This is my fourth post trying to find a way to install DNN.

I started with a base XP SP2 system with IIS, NET Framework 2.0 and SQL Server 2005 installed with DotNetNuke as a named instance.

Based on many hours of reading posts on this site....(more later) I did the following (at a summary level, though can upload any entry on any item you should want...just did not wish to make this initial entry horribly long):

I downloaded the source.zip to a directory named DotNetNuke. 

I created a virtual server pointing to the DotNetNuke sub-directory "Website".  I added Default.aspx.

I created an emtpy DotNetNuke database.  I assigned ASPNET and Network Service full access to everything.

I renamed web to web.config.   I fixed the entries to point to SQL Server rather than Express.  I added/corrected the AutoUpgrade, UseDnnConfig and InstallMemberRole to value="true".

I set ASPNET to read permission at the C: root directory with modify children.  Then I corrected the entries for DotNetNuke and Windows directories to modify and full respectively.

I still get an ASPNET connection failure.

I just want a set of instructions on how to successfully install DNN 4.02 on XP SP2, Server 2005 Standard with a named instance.

I don't want to hear "Read the Instructions", as multiple respondants have mapped it's serious deficiencies.

I don't want to hear that SQL, IIS, ASPNET issues are not relevent.  Any change to any of those that is required to get DNN installed is relevent.

I don't want to hear "Read the other entries and blogs", as my employer is not paying me to do that.  (Even though I have spent 25-30 hours doing it)

I don't want to hear "Look at my hosted install dialog", as hosted and native have major differences.

I can upload any part of my install if anyone wishes to view it.

Just an update.  I have spent the last few ( 4+) hours trying everything that has been posted.  I am now back to the stupid "aspnet_wp.exe fails" from the "Unable to Connect".

 

Ok. If you follow these directions to the letter, you WILL have a DotNetNuke installation running on your Windows XP Professional box. If you want to then open and compile the solution in Visual Studio, that is the subject of another post, but let's first get you installed...

1. Unzip the DotNetNuke 4.02 Install zip into an empty directory where it will reside on your machine. In my case that is D:\Development\WebProjects\DnnDev.

2. Right click on the DnnDev directory and select "Sharing and Security" and click the Security tab.

3. Click the "Add" button and in the "Enter the Object Names to Select" area, type "ASPNET" without the quotes.

4. Click the [Check Names] button and the ASPNET username will be verified and fully qualified. Click OK.

5. Select the new ASPNET user and give him "Modify" permission. He doesn't need "Full Control". Click OK.

6. Back in the WebRoot directory, Make a copy of the release.config file and rename it "web.config". Also copy the \config\SiteUrls.config file to WebRoot.

7. Open the web.config file in a text editor (Textpad is the best), comment out the two SQL Express SiteSqlServer keys, and uncomment the SQL Server 2000 / 2005 ones.

8. Fix the value of them both as follows...

"Server=(local);Database=DnnDev;trusted_connection=yes;"

Make both SiteSqlServer keys have the same connection string. Save and close the text editor. Don't modify anything else in the web.config file.

-----
SQL Server:

 This is slightly different in SQL Server 2005 and SQLServer 2000, but the concepts are the same. If you have problems finding any of this stuff in there, reply and let me know exactly which version you are using.

Before you create the database...

9. Start up SQL Server Enterprise Manager and expand the "Security" section. Make sure "ASPNET" has been added to the list of "Logins" and given default access to "master".

10. Collapse the security node, right click on the "Databases" node and select "New Database". Name the database DnnDev. Accept all defaults and let the Enterprise Manager create the database.

11. Expand the new DnnDev database node and select "Users". Right click in the users area and select "New Database User". From the drop down list, select the "ASPNET" account you just created. Give him dbowner access. Click OK.

Close the SQL Server Enterprise Manager.

-----
IIS Administrator:

12. Open IIS Adminstrator applet and add a new virtual directory to the default website. Name it "DnnDev", point it to the D:\Development\WebProjects\DnnDev directory. Make sure "Read" and "Run Scripts" are checked and accept all other defaults.

13. Right Click the new website entry in IIS and click "Properties". Select the "ASP.NET" tab and make sure you are running the 2.0.50215.0 version of ASP.NET.

Setup is now complete. If there is not a problem with the system, opening up IE or Firefox and navigating to http://localhost/dnndev will instantiate the DotNetNuke installer. After the installer has completed, there will be a link at the bottom of the page that will take you to the new portal site. Installation will only run once. After which point, navigating to http://localhost/dnndev will just display the site.

I did not "demand" anything, I simply asked for an answer.  If my tone was wrong, it was probably due to the pain that this project is causing me.

hooligannes:

I am forced to work on this project between 22:00-05:00 since I clearly can't bill my client for these conversations and attempts.  While I appreciate your offer to assist, off the top of my head, I don't have a clue as to what time zone you are in (-4GMT). 

I have dedicated more than 30 years of my life to volunteer IT groups (SHARE, Guide, ANSI, ISO) and I fully expect to "pay my dues" to DNN.  What was your hidden meaning behind "I will have one request and I hope you honor it"?  I have, in several posts, offered my time and abilities with no response except one that indicated that since I didn't have "significant DNN experience" my assistance would be of little use (my interpretation of the comment).

Getting to the subject at hand (using DotNetNuke Installation Guide V1.0.03 and the fact that I am developing this on XP with a hopeful transistion to a production Server 2003 environment using SQL Server 2003 in both cases).:

I added <localmachine>\ASPNET to  SQL with permissions db_owner, db_datareader, db_datawriter, db_ddladmin, and db_securityadmin per page 15.  This is over and above your statement.

I followed MS KB 317012 as best I could concerning permissions for ASPNET.  The NETWORK SERVICE entries are in anticipation of moving this portal to a production platform

Per the install instructions (pg13-14) additional changes to web.config are required by my reading over and above your statement.

So, being stupid,  most times hardheaded, and forced by my nature to follow directions implicitly, do I head your comments to follow the "INSTALL GUIDE" or your comments in this post?

In any event DNN still doesn't install.

pblanton:

I appreciate you comments and suggestions, unfortunatly my customer is forbidden by his outside auditor to use SQL security.  It has to be Windows Authorization.

And, when I tried your suggested path using Windows Authorization (as best I could interpret it), I got the same old "Unable to Connect"