Home » DotNetNuke - Module Development » DotNetNuke SecurityException AspnetHostingPermission

DotNetNuke SecurityException AspnetHostingPermission

tp_vol4_003

Yesterday I was setting up DotNetNuke for a designer on a computer at a corporate location so that he could start working on CSS for some of our custom modules.  He had an earlier version of DNN installed, so you’d think that it would “just work” but there seems to be a new module or something going on that caused the AspnetHostingPermission exception to get thrown so that we couldn’t even run the web site.

I hate setting up development computers at corporate locations.  Everything that works fine for me always seems to take just as long if not longer to set up there (wherever “there” is.)

There is a simple fix to this error.  Go into the IIS manager and select the AppPool that your web app is using.  Click the “Advanced Settings” link that you’ll find on the right-hand panel.

In the new dialog that shows up, you’ll see “Process Model” > “Identity”.  Change that identity to “NetworkService” and OK out.

Everything SHOULD work now.  At least it did for me.

 

Other post in DotNetNuke - Module Development

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
  • DotNetNuke Modules – Install DNN into VS 2008DotNetNuke Modules – Install DNN into VS 2008 Today, we will install DotNetNuke into Visual Studio so that we can create our first module. So fire up Visual Studio, and let's get going.I'll be using Visual Studio 2008 to walk […]
  • DotNetNuke Modules – Making Content PortableDotNetNuke Modules – Making Content Portable The last main feature of module development that we need to discuss is the implementation of IPortable.If you've ever worked with other content management systems in a corporate […]
  • DotNetNuke Modules – Foundational ConceptsDotNetNuke Modules – Foundational Concepts There are two design patterns that DotNetNuke relies on heavily, not just in the core code, but in any module you might develop.The first is a three tiered architecture, or more […]
  • DotNetNuke Modules – Benefits of ArchitectureDotNetNuke Modules – Benefits of Architecture Now that we have something running, it's time to take a look at the various parts of the DotNetNuke framework.  But before we do, we need the all-important question, "Why do we […]

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer. His commitment to quality through test driven development, vast knowledge of C#, HTML, CSS and JavaScript as well as his ability to mentor younger programmers and his passion for Agile/Scrum as defined by the Agile Manifesto and the Scrum Alliance will certainly be an asset to your organization.

  • http://www.scottallender.com Scott Allender

    I have ran into this issue a LOT with windows 7 and windows 2008. My fixes for it are basically to ensure that the App Pool user account belongs to IIS_IUSRS group and and to grant the IIS_IUSRS group RWX privileges on the site directory. For DNN, I grant Full privileges.

    • Dave

      While it “works”, I wouldn’t do that on a production server. Sounds like a security risk to me.