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 Access to the path '...LogFailures.xml.resources' is denied
Previous
 
Next
New Post
2/26/2011 1:38 PM
 
Hi,
Are You sure that LogFailures.xml.resources exists on the file system?
 
New Post
2/26/2011 1:47 PM
 
Darin,

Maybe this post helps: http://www.40fingers.net/WeblogsNews/...



Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
3/1/2011 10:57 AM
 
Seems like there are issues with using the ApplicationPoolIdentity account for the AppPool Identity advanced setting (in conjunction with granting the DefaultAppPool user full access to the physical path).  Just so others who have this trouble understand all of what I stated in this post I'll go into detail.  I have the luxury of having access to a hypervisor (a physical box which servers virtual machines) whereby I can create virtual servers at will.  So to diagnose this problem I decided to create a fresh copy of Windows Server 2008 R2 inside a Virtual Machine for testing purposes.  The steps I took were: 1) install Windows Server 2008 R2 with required IIS/Application roles 2) run all MS updates 3) create physical folder for DNN instance under c:\inetpub in my case I created c:\inetpub\centreDnn 4) grant the DefaultAppPool user Full Control to c:\inetpub\centreDnn 5) create apCentreDnn application pool within IIS setting the Identity value to AppPool Identity 6) created the site within IIS directing the site to use the apCentreDnn app pool.  So from step 1 to step 6 were talking a server that's about 1 hour old - not too much can be wrong with it at this point.  7) visit website and got the same stinkin error.  Not sure Cathal understood exactly what I meant as I didn't clone anything this was an entirely new and clean install - however his suggestion to use the Network Service account did prove successful on this new install which leads me to believe that either some setting isn't documented when using the ApplicationPool Identity model or else the technology isn't where it needs to be and isn't stable enough to run the same from install to install.

At any rate I'm proceeding with my new DNN instance using the Network Service account instead of ApplicationPool Identity.
 
New Post
3/1/2011 11:30 AM
 
Thanks Erik, I wish I had that doc prior to starting the VM install.  Perhaps I'll try these exact steps with another VM when time permits.  One thing in your article that I didn't do was Auto Create the appPool I manually created mine and it appears that by allowing the site to auto create the pool there is a virtual user with the same name that gets created as well much like the DefaultAppPool user described in another post in this thread.  Perhaps the missing link is to allow the site to autocreate the pool and then use the virtual user created by that process in the ACL to the physical location.
 
New Post
11/12/2011 1:16 PM
 
To whom it may concern. On Win XP 64bit, I have given both ASPNET and NETWORK SERVICE Full control. This got rid of LogFailures.xml.resources' while trying to install
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Access to the path Access to the path '...LogFailures.xml.resources' 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