Hi - It appears that you have only view permissions and that your installation isn't complete. The fact that you can get as far as you have would seem to rule out any network communications from or between servers, i.e. SQL Server to your IIS web server running on a different machine.  Your configuration is a common one and is good for various reasons.

What I would recommend is starting over (sorry...) and making sure that your aspnet account is added to the web folder.  You'll want to do this using Windows Explorer right click on the folder and select Properties > Security and clicking the Add button.  In the textbox add aspnet and click OK.  Select the ASP.NET machine account just added and click "Full Control". Click OK and if prompted "Yes" to apply to all sub-directories.

Since some of the data has been loaded to your database, I would open SSMS or Enterprise Manager, locate your database,  delete it, create it and see that your user id/user account is properly added.  It should not matter but you can open IIS 6 and delete the virtual directory and re-create it.  If you already have websites running on your IIS 6/Win2k3 server then you should be set for DNN.  If not realize that IIS 6 is really locked down so you will need to enable scripts, and any other settings that are turned off - it would be worth it to check into this and review the built-in help on setting up your IIS 6 server.  This is a one time deal but until you are configured for running asp.net websites you'll have issues with any asp old, asp.net, etc. sites.

Let me know how it goes and if you need additional help and I will see what I can do.

Good luck!

John

Hi Roncansan - I believe you are very close.  If you check the c:\inetpub\wwwroot\DotNetNuke\Install\Module folder it should be empty at this point, i.e. won't have all the *.zip module files.

What I am interested in is step (3) above.  Are you using Windows Explorer to do this?  I don't have Win2K3 installed so what I see in WinXP may be different than what you see, but only slightly.  All that is necessary is the aspnet account, but give it full control.  If you have an "Advanced" button under the Security tab for the DotNetNuke folder, click it and check the check box with "Replace permission entries...".  Click OK twice to exit.

Also, for your website do you have an icon that looks like an open box with a COM+ (black & green) component thing inside, or does it look like a flat folder with a blue globe in the lower right?  If it is the later select your site and click on properties.  Click on the "Create" command button and then click ok.

Since your site may still not come up right, i.e. the install didn't complete, you may want to delete the files and sub-directories under your DotNetNuke folder AFTER you've saved your web.config off to the side, since it sounds like your web.config setting for your database are correct and you can use this again.  Delete your database and create this again.  The sql account sounds fine although all you need is public and dbo_owner checked for your sql account.  If you are still having trouble send me an email at itfriend@dls.net and I can send you my MSN Messenger account so we can IM and get you running.

Again, I think that you are very close even though it may appear that nothing is working.  Good luck and contact me if I can help any further!

John
*Forgot to ask if you are able to run other asp, asp.net sites on your IIS 6 install since by default it is very locked down.