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 ...Problem installing 6.1.0Problem installing 6.1.0
Previous
 
Next
New Post
11/2/2011 7:50 AM
 
Hi

Tried to install v6.1.0 on a Helm based server. Got the error during the install wizard after being prompted for a windows ui and password. I've installed 6.01 and 6.0.2 on the same server previously without problem.

Can anyone shed any light on this?

THanks in advance

Phil







Server Error in '/' Application.

Access to the path 'D:\Domains\lower-wensleydale.com\wwwroot\App_Data\ClientDependency' 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 'D:\Domains\lower-wensleydale.com\wwwroot\App_Data\ClientDependency' 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 and IIS 7, and the configured application pool identity on IIS 7.5) that is used if the application is not impersonating. If the application is impersonating via , 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 'D:\Domains\lower-wensleydale.com\wwwroot\App_Data\ClientDependency' is denied.] System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +9718606 System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj) +9489546 System.IO.DirectoryInfo.Create() +15 ClientDependency.Core.CompositeFiles.Providers.XmlFileMapper.EnsureXmlFile() +115 ClientDependency.Core.CompositeFiles.Providers.XmlFileMapper.Initialize(HttpContextBase http) +142 ClientDependency.Core.Config.ClientDependencySettings.LoadDefaultFileMapConfig(ClientDependencySection section, HttpContextBase http) +130 ClientDependency.Core.Config.ClientDependencySettings.LoadProviders(ClientDependencySection section, HttpContextBase http) +495 ClientDependency.Core.Config.ClientDependencySettings..ctor() +135 ClientDependency.Core.Config.ClientDependencySettings.get_Instance() +78 ClientDependency.Core.Module.ClientDependencyModule.LoadFilterTypes() +37 ClientDependency.Core.Module.ClientDependencyModule.System.Web.IHttpModule.Init(HttpApplication app) +79 System.Web.HttpApplication.InitModulesCommon() +172 System.Web.HttpApplication.InitModules() +43 System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +828 System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +304 System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107 System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +327


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
 
New Post
11/2/2011 8:57 AM
 
Hi Phil,
Are you using the beta version or the version that was released late last night? I know we had this problem in the Beta release, but I'm fairly certain it was corrected for the final release.
Here is a link to final release packages:
http://dotnetnuke.codeplex.com/releases/view/75718

Thanks,
Will

Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
11/2/2011 9:05 AM
 
HI WIll, thanks for the quick reply. It was last nights release that I tried to install....I never use a beta release on a live server.

Is there a simple fix or does the package need to be updated?

Cheers

Phil

 
New Post
11/2/2011 9:10 AM
 
Phil,
What you will need to do is set the permissions properly on that folder (D:\Domains\lower-wensleydale.com\wwwroot\App_Data\ClientDependency) as indicated in the error message.

"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 and IIS 7, and the configured application pool identity on IIS 7.5) that is used if the application is not impersonating. If the application is impersonating via , the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user."

I'm not very familiar with Helm, but I would think you would be able to do this through the Helm console.

Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
11/2/2011 9:18 AM
 
Thanks WIll - to clarify, you're saying that the ASPNET user has to have permissions on that directory as well as NETWORKSERVICE?

Is this a change to the DNN installation requirements in general or just a workaround for this particular problem?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem installing 6.1.0Problem installing 6.1.0


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