Aaron,

I suggest you review your information before posting misguiding remarks. From page 36 of the DNN 4 Installation Guide:

In addition to the connection String setting under <appSettings> required in 3.x, 4.x also requires the same connection String to be set under the

<connectionStrings> section.

Although I do not take it personally and don't think of myself a DNN guru by any means, I have to recommend you to be more careful with your posts. The forums are community supported, people that have more experience with DNN are encouraged to participate helping others. I honestly think that disqualifying other posters is a not a good approach.

Finally, if you have found a dozen things missing from the instruction please post them in this forum and ask a moderator to pin it so others don't miss them too and they can update the guides as well.

I did not mean to be negative in my post. The platform is very easy to use and install but it does not mean that the user shouldn't have a minimum knowledge. Yes, there are several posts that repeatedly say the same and almost 100% of the time it is simply not following the instructions. You might understand that after answering the same thing over and over and having a document that describes in detail the Installation process the fastest answer is help me help you.

I am sure many other members would have stepped in as well, yet I will do it once more. Please note I am not providing details, which are already in the mentioned documentation. Also I make no assumptions about your knowledge, except that you are the administrator of your machine and know your way around windows, IIS and SQL.

DNN 3 in Windows XP and SQL 2000

1. Download install version
2. Unzip the file to <DNNFolder>
3. Set permissions for that directory as described in the Installation Guide.
4. Open IIS and create a <Virtual Directory>. Point it to the <DNN Folder>
5. Open your <SQL instance> Create a <DNNDatabase>
6. Add a <DNNUSER> with a <PASSWORD> to SQL
7. In SQL give dbowner permissions to <DNNUser> for <DNNDatabase>
8. Open release.config and set connection strings to your <SQL instance>, <DNNDatabase>, <DNNUSER> and  <PASSWORD>
9. Rename release.config as web.config.
10. Call http://localhost/>Virtual Directory>
11. Done

Add me to your MSN as hooligannes (at) hotmail.com I will guide you step by step and then please come back and say it could take 5 minutes and not three months. This will simply calma down my ego, and is pretty selfish but c'mon humor me!

At this point, I am going to add my 2 cents worth of comments.  As you can see in my other posts, I've had a great deal of trouble trying to get DNN 4.0.2 to install.  In my opinion, any change to IIS, SQL, XP, 2003, etc, that has to be made/included to get DNN to install IS A DNN INSTALL ISSUE,  not IIS, not SQl, etc.

As such, these associated changes should be described and documented in the DNN documentation.  Given the total effort and man hours spent by everyone on this forum asking, re-asking, re-re-asking and those replying, re-replying, etc, it would surely be less expensive (and better for DNN's reutation) to break out the install doc by release and update the doc to include all of the associated changes that are requied to get DNN up and running.