Installing DotNetNuke 4.4.1 - Clean Install Windows 2000/XP 

Installing DotNetNuke can be somewhat difficult at times, therefore I am writing this article to give you a full step by step guide to installing DotNetNuke on a Windows XP Pro system. The instructions are similar for Windows 2000 and XP Home but might vary slightly. I will be creating a secondary installation guide in the future for installation with Windows Vista.

Prior to following this instruction guide please ensure that you have downloaded the "install" version of DotNetNuke 4.4.1 from http://www.dotnetnuke.com.  You can save the zip file to your desktop for the time being.  You will also need to have SQL Server Express 2005 installed, (Other versions work, but these instructions might not match 100% on other versions).  Lastly you must be logged in with administrative permissions.

The setup will be broken into the following 3 sections; creating the needed SQL Serveer database and user account, unzipping DNN and configuring the web.config file, and finally setup of the virtual directory and starting DotNetNuke.

Creating SQL Server Database

  • Start SQL Server Management Studio Express (SSMSE), (if you don't have this please install it from here.)
  • Once SSMSE has opened, please note the "Server Name" of the server that you are connecting to, this is the full text of the information in that field. (Circled in below picture) 
  • Once you have connected and opened the utility you will want to expand the node for your server name as located in step 2
  • Right Click on the "Databases" node and select "Create New Database"
  • Specify a name for your database, I will use dnn441 for this example, then click create 
  • Now expand the "Security" node, then right click on "Logins" and select add
  • Provide the information for the dnn account, be sure to select "SQL Server Authentication" and remember the password. (If SQL Server Authentication is not available see this to enabled mixed mode on your server) 
  • Now select "User Mappings" and check the box next to your newly created database at the top, then select the "dbowner" role from the listing at the bottom, this maps the account to have full access to your database. 
  • Click "Create" to have your user account created. Once this is completed you are now done with the databse setup. Please remember the database server name from step two and the username and password used to create the SQL Server account as we will be using this in the next section

Unzipping and Configuring DotNetNuke

All files from the DotNetNuke install zip must be extracted to a common folder, typically this folder is created as a sub directory of C:\inetpub\wwwroot. The instructions below will be based on installation to this location, if you desire to install DotNetNuke at a different location simply substitute your folder path anytime it is referenced in the below instructions.

  1. Using windows explorer navigate to c:\inetpub\wwwroot, then right click and select "New" -> "Folder" and create a folder called "DotNetNuke441". This folder will become the install directory for DotNetNuke
  2. Open the DotNetNuke 4.4.1 Install Zip package
  3. Select "Extract All Files/Folders" 
  4. For the extraction location select the folder you created in step 1
  5. Once all files have been extracted you need to edit the "Web.config" file located in the root of the DotNetNuke folder
  6. Modify the circled sections of the web config, you will need to set this up to connect to your database, so substitute your values for "Server", "Database", "uid", and "pwd".  This format of connection string will work for both SQL 2000 and SQL Express.  You may use other valid connection string settings, you may visit http://www.connectionstrings.com for assistance with other formats
    Connection String Values to Change
  7. Save the modified document
  8. Navigate back to the folder where you placed DotNetNuke and right click on the foldername, then select "Sharing and Security".  From there you will want to grant FULL permissions to either the ASPNET Account, or NETWORKSERVICE account (Vista and 2K3 Server).  No other permissions should need to be changed.

Setup Virtual Directory and Start DotNetNuke

Now that we have the database and file system setup we will proceed to the final step of setup, configuring IIS to host your website.

  1. Open the IIS Snap-In tool, this can be found via "Start" -> "Settings" -> "Control Panel" -> "Administrative Tools" -> "Internet Information Services"
  2. Expand the root notes until you can expand the "Default Web Site" node
    IIS Default Web Site View
  3. You should see your application folder listed under the "Default Web Site", right click on the folder and select "Properties"
  4. On the first tab, click the "Create" button next to the application name, you should then see DotNetNuke441 listed
    IIS Directory Settings
  5. Now, switch to the "Documents" tab. Remove all current entries and add "Default.aspx" to the listing. Your window should look like the following when complete.
    IIS Documents Settings
  6. Now, switch to the "Dierectory Security" tab
  7. Click "Edit" in the "Anonymous access and authentication control"
  8. Ensure that a checkmark is included in the "Anonymous Access" box at the top of the screen then click "Ok" to exit
  9. Now switch to the "ASP.NET" tab and ensure that "2.0.50727" is selected for the ASP.NET version
  10. Click "Ok" to save your changes and complete the IIS setup
  11. Now open Internet Explorer and navigate to "http://localhost/DotNetNuke441/
  12. You should see some test indicating the DNN installation progress then a link that says "Click here to access your portal"

This walks you through the entire setup process to get a local copy of DotNetNuke working with SQL Server 2005 Express. If you have any comments please leave them below, if you have any trouble and need assistance please utilize my forum to request assistance!

Posted by Mitchel on Tuesday, February 27, 2007
 

Comments

This looks like a very good tutorial, thank you for your great efforts!!

Please consider writing similar tutorials about *upgrading* a DNN install, and about *moving* a DNN site from development to production.

Thank you, Tom

By Tom on Tuesday, February 27, 2007 at 5:08 PM

Tom,

Thank you for the positive feedback. If you look back a few days in my blog postings I have an upgrade post for going from 4.3.5 -> 4.4.1. I will consider preparing a "moving" tutorial, I actually had not thought of that one.

By mitchel.sellers@gmail.com on Wednesday, February 28, 2007 at 1:22 AM

Well done Mitchel, now I finally got a place to point all those pesky newbies to ... just kidding everyone :)-

By Tom Kraak on Sunday, March 04, 2007 at 10:54 AM

A tutorial for Server 2003 and SQLExpress 2005 would be nice. I thought this was for 2005 but just now realised it doesn't say that.
Thanks.

By Ernie on Friday, March 09, 2007 at 2:25 PM

Ernie,

The SQL Server portion of this does assume you are using SQL Server 2005 express.

You SHOULD be able to use these same instructions for Windows 2003 server....I do not believe there are any major differences, I just don't have access to a copy of it to get detailed screen captures or to double check.

By mitchel.sellers@gmail.com on Friday, March 09, 2007 at 2:26 PM

With reference to your IIS tree.jpg:

I'm not sure I understand the difference between dnn441 and DotNetNuke441.

You mention in the code that database=dnn441, but also specify earlier that the database is given the name of DotNetNuke441.

2.
isn't there something missing in your instructions? Such as:

"configure the physical directory ~ give read/write permissions to the physical directory for either the ASPNET user account if you have IIS 5 (Windows XP) or the NETWORK SERVICE user account if you have IIS 6 (Windows 2003). the permission that you must give is "modify". then give read (but not write) permissions to the IUSR_machinename account.
"

By Mark on Wednesday, August 15, 2007 at 7:11 AM

Mark,

I apologize, there was an inconsistency in my wording, I have modified this.

As for permissions, you are mostly correct. I have added a note about that as well. But basically just give full permissions to ASPNET or NETWORKSERVICE and you will be set to go!

Also you might have a look at my newer install documents as they are a bit more detailed.

By mitchel.sellers@gmail.com on Wednesday, August 15, 2007 at 7:40 AM

Finally got it working.

I found out that in IIS the ASP.NET 2.x was not there (Web Service Extensions). I had to enable ASP with this command: "%systemroot%\Microsoft.NET\Framework\version\aspnet_regiis.exe" -i.

I also followed this guide to get SQLExpress connected on my Windows 2003 box: http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1202/Default.aspx

Succes,
Patrick

By Patrick on Thursday, October 25, 2007 at 6:38 AM

Its work for me ....

thanks

your so cool ....

keep up the gud work

By Elmer Extreme on Thursday, August 28, 2008 at 10:01 PM
Click here to post a comment

Donate

Show your appreciation for the content/modules made available by MitchelSellers.com by making a donation. Donations are used to assist with dedicating time to creating free content.