Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Access to the path "<install dir>\DotNetNuke.config" is deniedAccess to the path "\DotNetNuke.config" is denied
Previous
 
Next
New Post
6/11/2007 9:09 AM
 

I get the following error when accessing my DNN site:

 

Server Error in '/' Application.

Access to the path 'E:\DotNetNuke\DotNetNuke.config' is denied.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UnauthorizedAccessException: Access to the path 'E:\DotNetNuke\DotNetNuke.config' is denied.

ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[UnauthorizedAccessException: Access to the path 'E:\DotNetNuke\DotNetNuke.config' is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +2014595
System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) +488
DotNetNuke.HttpModules.Compression.RequestFilter.RequestFilterSettings.GetSettings() +237
DotNetNuke.HttpModules.Compression.RequestFilter.HttpModule.FilterRequest(Object sender, EventArgs e) +259
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

 

I don't have a DotNetNuke.config file in the root of my DNN directory, but I do have one in a subdirectory called config.  I don't think that I should have to copy that file to the install directory and I can't find where that file is being referenced from any other file.  Has anyone else had this issue?

 

Thanks...

 
New Post
6/11/2007 1:19 PM
 

Yes, I have had the same problem on some of my installations. I did just copy the file from the config directory to the root ditectory which then solved the problem. I'm not exactly sure why this is happening and I haven't looked into it because my sites are running fine.


Kist Enterprises
www.kistenterprises.com
 
New Post
4/12/2008 7:18 PM
 

I've seen this error once before.

Tonight I'm setting up a client's web site on a server that I can only admin via thier control panel, and I got this error.

When I copied the dotnetnuke.config file from the /config folder to the root folder I progressed to this error:

Could not find a part of the path 'C:\Inetpub\vhosts\lumentech.co.za\httpdocs\Config\Backup_200841319\web_.config'.Access to the path 'C:\Inetpub\vhosts\lumentech.co.za\httpdocs\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.
 

I think it's because of the file permissions of the virtual root which causes that error and by copying the dotnetnuke.config file it's just getting around it to give the real problem's error.

 
New Post
4/13/2008 6:46 AM
 

Hi guys, you should not use copy function to fix this error. Instead you should upload your files that has to placed at root level, to a directory has read, web, write permission first. Then you should move the file from that directory to root directory.

I have been using this method since years and it works :)

One more thing:

If you copy a file from A directory to B Directory, file will have permissions of B directory.

If you move a file from A directory to B directory, then file will have permissions of A directory. This is the main security difference between copy and move actions.

Move action inherit permissions from old directory, and copy action gets new security permissions of target directory.

More info can be viewed on my blogs.

Regards.

 

 


Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey
 
New Post
4/20/2008 6:45 PM
 

I had the exact same problem.  But, from my experience it really is a directory permission problem.  I added NETWORK SERVICE and gave it read, write, execute permission and bada bing it worked. 

Hope this helps. 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Access to the path "<install dir>\DotNetNuke.config" is deniedAccess to the path "\DotNetNuke.config" is denied


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:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out