New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

Home All Forums

1
2
3
4
5

Home

Getting Started

Installing DNN ...

Installation 4.9.3 System.Security.SecurityException:

4/20/2009 10:18 PM

MSlade

Joined: 12/6/2008

Posts: 10

Installation 4.9.3 System.Security.SecurityException:

I am installing 4.9.3 on an Windows 2003 R2 server with IIS v6. I have set all the prerequisites up, permissions, database etc. The website is set up under the default web site in IIS using a virtual directory. When I run the install by typing http://localhost/BCSPortal I get the Server Error message below;

If I change my web.config where the trust is commented out and set it to the following;

<!--

set code access security trust level - this is generally set in the machine.config--><trust level="Medium" originUrl=".*" />

I get a DNN installation error message that tells me that my Network Service permissions are not set correctly, yet I have double checked and even have someone check for me that the Network Service account has every box ticked excpet full control.

I have been searching on the web about medium trust issues, but have not found a resolution for problems during installation. Thanks in advance for help.

DotNetNuke Error: - Version 04.09.03

DotNetNuke Configuration Error

Access to the path 'C:\Inetpub\DotNetNuke\web.config' is denied.

DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website.

Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Disable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.

If using Windows 2000 - IIS5
1. the [SERVER]\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website.
If using Windows 2003 - IIS6
1. the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and Change Control of the virtual root of your website.

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

            

            1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

            

              <%@ Page Language="C#" Debug="true" %>

            

            or:

            

            2) Add the following section to the configuration file of your application:

            

            <configuration>

               <system.web>

                   <compilation debug="true"/>

               </system.web>

            </configuration>

            

            Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

            

            Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


            [SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]
   System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) +0
   System.Security.CodeAccessPermission.Demand() +58
   System.AppDomainSetup.VerifyDir(String dir, Boolean normalize) +93
   System.AppDomain.get_BaseDirectory() +33
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +234
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +127
   DotNetNuke.Common.Global.Global_BeginRequest(Object sender, EventArgs e) +53
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

4/21/2009 3:54 AM

Sebastian Leupold

www.dnnwerk.de
Joined: 3/8/2004

Posts: 46212

Re: Installation 4.9.3 System.Security.SecurityException:

please make sure to grant "Network Service" full permission for DNN install directory and all files and subfolders inside.

Cheers from Germany,
Sebastian Leupold

Speed up your DNN Websites with TurboDNN

4/21/2009 1:40 PM

MSlade

Joined: 12/6/2008

Posts: 10

Re: Installation 4.9.3 System.Security.SecurityException:

I had tried changing the Network Service account to have Full control permissions at the root directory (all child directories and files had same permissions) and this had no effect. I still received the same DNN error message when trying to access install wizard.

Page 1 of 1

Home

Getting Started

Installing DNN ...

Installation 4.9.3 System.Security.SecurityException:

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DotNetNuke Error: - Version 04.09.03

DotNetNuke Configuration Error

DNN Corp. (DotNetNuke)