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 ...Install Fails on Windows 2003 DCInstall Fails on Windows 2003 DC
Previous
 
Next
New Post
6/19/2008 11:38 AM
 

We are trying to install DNN 4.8.4 on a Windows 2003 DC. We have extracted the Install.zip into the D:\INetPub\DotNetNuke folder.

SQL 2005 Blank Database is built with a non-sa account having DBO rights. We can log into the database using the account credentials.

Permissions to the Site Folder are Full Control for both IUSR and NETWORK SERVICES account.

Here is the error we are getting:

DotNetNuke Error: - Version 04.08.04


 

DotNetNuke Configuration Error

Could not find a part of the path 'D:\INetPub\DotNetNuke\Config\Backup_20086191039\web_.config'.Access to the path 'D:\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.

The NT AUTHORITY/NETWORK SERVICE User Account HAS FULL ACCESS!

Does anyone know a work around for this bogus error?

 

 
New Post
6/20/2008 7:49 PM
 

domain controllers have additional security applied to them, and really shouldn't be used for web hosting if possible. http://msdn.microsoft.com/en-us/library/aa579070.aspx details the measures you'll have to take to create a valid user to get asp.net running correctly.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/24/2008 12:55 AM
 

It doesn't make any difference...I can even grant the Network account administrative rights to the box, and it still says it cannot write to the folder.

 
New Post
6/24/2008 8:34 AM
 

please read the link I posted earlier, as it states:

 On a domain controller, all user accounts are domain accounts and not local machine accounts, so Aspnet_wp.exe fails because it cannot find a local account named "localmachinename\ASPNET".

You will need to explicitly create a local machine account, grant it permissions and update the machine.config, to get asp.net working.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/24/2008 9:20 AM
 

In addition to what Cathal has said as far as security, there is one other thing to consider. A website on a DC will likely suffer from performance issues, you really should avoid hosting a site on a DC.

 



 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install Fails on Windows 2003 DCInstall Fails on Windows 2003 DC


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