DotNetNuke Configuration Error ( Install DotNetNuke on Windows server 2008 R2 or Windows server 2008 with IIS 7)
Today I am followed the DNN forums instructions and a video to install DotNetNuke(version 4.9.02) on Windows server 2008 R2, I got the following error message.(See it at the end of the article).I double checked that I do give full permission to NETWORK SERVICE User Account.
After I have done a little bit research ,it turns out that in my application pool settings within IIS, the “identity” of the account has been set to ApplicationPoolIdentity rather than NetworkService.The “identity” of the account is the one that needs to be granted full permissions. As long as that name matches, you are fine. NETWORK SERVICE is simply the default,but it is not the default for my machine.See the screen shot below.
The following is the error message from DotNetNuke.
Access to the path ‘C:\DNN\DotNetNuke_Community_04.09.02_Source\Website\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.
Thanks for this post. I was trying to figure out this problem forever. It seems in the DNN documentation they would say to check the App Pool identity.
Thanks!!
I was having File Upload issues as I moved a DNN site to new server running Win 2008 R2. Changing the Pool Identity back to Network Service solved the issue.
Thank you!