[i:30nv73ko]By Mitchel Sellers[/i:30nv73ko]

Source:
[size=85:30nv73ko][URL=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/119/Installing-DotNetNuke-455-Locally.aspx]http://www.mitchelsellers.com/Blogs/tabid/54/articleType/
ArticleView/articleId/119/Installing-DotNetNuke-455-Locally.aspx[/URL][/size:30nv73ko]

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 have tried to note as many differences as possible. Windows Vista installation is similar but requires a few different steps relating to IIS. This article is a re-visit to my first article of this type geared towards DotNetNuke 4.4.1..

Prior to following this instruction guide please ensure that you have downloaded the "install" version of DotNetNuke 4.5.5 from [url=http://www.dotnetnuke.com/:30nv73ko]http://www.dotnetnuke.com[/url:30nv73ko]. 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 to your machine 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.

[size=130:30nv73ko]Creating SQL Server Database[/size:30nv73ko]

[list:30nv73ko]
[*:30nv73ko]Start SQL Server Management Studio Express (SSMSE), (if you don’t have this please install it from [url=http://go.microsoft.com/fwlink/?LinkId=64064:30nv73ko]here.[/url:30nv73ko])[/*:m:30nv73ko]
[*:30nv73ko]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) [/*:m:30nv73ko]
[*:30nv73ko]Once you have connected and opened the utility you will want to expand the node for your server name as located in step 2[/*:m:30nv73ko]
[*:30nv73ko]Right Click on the "Databases" node and select "Create New Database"[/*:m:30nv73ko]
[*:30nv73ko]Specify a name for your database, I will use DotNetNuke455 for this example, then click create [/*:m:30nv73ko]
[*:30nv73ko]Now expand the "Security" node, then right click on "Logins" and select add[/*:m:30nv73ko]
[*:30nv73ko]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 [url=http://www.hostmysite.com/support/vps/windows/mixedmode/:30nv73ko]this[/url:30nv73ko] to enable mixed mode on your server) [/*:m:30nv73ko]
[*:30nv73ko]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. [/*:m:30nv73ko]
[*:30nv73ko]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[/*:m:30nv73ko][/list:u:30nv73ko] 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.
[list=1:30nv73ko]
[*:30nv73ko]Using windows explorer navigate to c:\inetpub\wwwroot, then right click and select "New" -> "Folder" and create a folder called "DotNetNuke455". This folder will become the install directory for DotNetNuke[/*:m:30nv73ko]
[*:30nv73ko]Right click on your newly created file and select "Sharing and Security"[/*:m:30nv73ko]
[*:30nv73ko]Switch to the security tab, if you do not see the "Security" tab, you will need to disable the "Use Simple File Sharing" option in your Folder View Options.[/*:m:30nv73ko]
[*:30nv73ko]Click "Add.."[/*:m:30nv73ko]
[*:30nv73ko]In the textbox type ASPNET if on Windows 2000/XP or NETWORKSERVICE if on Windows 2K3/Vista, then press ok[/*:m:30nv73ko]
[*:30nv73ko]Under permissions for this account check the box for full control, then press "Ok" to save the changes[/*:m:30nv73ko]
[*:30nv73ko]Open the DotNetNuke 4.5.5 Install Zip package[/*:m:30nv73ko]
[*:30nv73ko]Select "Extract All Files/Folders" [/*:m:30nv73ko]
[*:30nv73ko]For the extraction location select the folder you created in step 1[/*:m:30nv73ko]
[*:30nv73ko]Once all files have been extracted you need to edit the "Web.config" file located in the root of the DotNetNuke folder[/*:m:30nv73ko]
[*:30nv73ko]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 [url=http://www.connectionstrings.com/:30nv73ko]http://www.connectionstrings.com[/url:30nv73ko] for assistance with other formats
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/web_config_Settings.jpg[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]Also inside the web.config look for a setting called <add name="AutoUpgrade" value="True" />, change the value on this to "False"[/*:m:30nv73ko]
[*:30nv73ko]Lastly inside the web.config look for a setting called <add name="UseWizard" value="True" />, change the value on this to "False"[/*:m:30nv73ko]
[*:30nv73ko]Save the modified document[/*:m:30nv73ko][/list:o:30nv73ko]
The above finishes the actual configuration of the DotNetNuke file system first we created the needed directory, then we assigned the proper file permissions, then we configured the web.config file to not only connect to the database but to also do some preventative settings changes to secure the site.

[size=130:30nv73ko]Setup Virtual Directory and Start DotNetNuke[/size:30nv73ko]

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.
[list=1:30nv73ko]
[*:30nv73ko]Open the IIS Snap-In tool, this can be found via "Start" -> "Settings" -> "Control Panel" -> "Administrative Tools" -> "Internet Information Services"[/*:m:30nv73ko]
[*:30nv73ko]Expand the root notes until you can expand the "Default Web Site" node
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Tree.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]You should see your application folder listed under the "Default Web Site", right click on the folder and select "Properties"[/*:m:30nv73ko]
[*:30nv73ko]On the first tab, click the "Create" button next to the application name, you should then see DotNetNuke455 listed
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Directory_Properties.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]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.
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Document_Properties.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]Now, switch to the "Dierectory Security" tab[/*:m:30nv73ko]
[*:30nv73ko]Click "Edit" in the "Anonymous access and authentication control"[/*:m:30nv73ko]
[*:30nv73ko]Ensure that a checkmark is included in the "Anonymous Access" box at the top of the screen then click "Ok" to exit[/*:m:30nv73ko]
[*:30nv73ko]Now switch to the "ASP.NET" tab and ensure that "2.0.50727" is selected for the ASP.NET version[/*:m:30nv73ko]
[*:30nv73ko]Click "Ok" to save your changes and complete the IIS setup[/*:m:30nv73ko]
[*:30nv73ko]Now open Internet Explorer and navigate to "http://localhost/DotNetNuke455/Install/install.aspx[/*:m:30nv73ko]
[*:30nv73ko]You should see some test indicating the DNN installation progress then a link that says "Click here to access your portal"[/*:m:30nv73ko][/list:o:30nv73ko]
This walks you through the entire setup process to get a local copy of DotNetNuke working with SQL Server 2005 Express. This installation guide can help you get up and going on a hosting provider as well, simply noting that the first portion of the setup is typically completed by your web hosting provider.

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 1: Download and Extract DotNetNuke 4.5.1 Source Package into your local drive[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5]Log in (or register) to DotNetNuke.com and get the latest source package available from Downloads page. Note that; you should download 4.x versions for ASP.NET 2.0 and 3.x versions for ASP.NET 1.1.[/size:2a0r3ix5][size=100:2a0r3ix5]After downloading source package extract it to a folder on your Desktop (for example Godaddy Practice folder).[/size:2a0r3ix5][size=100:2a0r3ix5]Now review the directory structure on extracted folder. You need to check Website folder under extracted folder. We are going to create many virtual directories to make it run at root level. Now, lets continue with next step.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 2: Godaddy Account Management[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]1) Click [/size:2a0r3ix5][url=http://www.godaddy.com/:2a0r3ix5][size=100:2a0r3ix5]here[/size:2a0r3ix5][/url:2a0r3ix5][size=100:2a0r3ix5] to open [b:2a0r3ix5]Godaddy.com[/b:2a0r3ix5]. Login to your account.[/size:2a0r3ix5]

[size=100:2a0r3ix5]2) Choose [b:2a0r3ix5]Hosting Servers > My Hosting Account[/b:2a0r3ix5] from main navigation menu.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]3) [b:2a0r3ix5]Manage Hosting[/b:2a0r3ix5] page will open. From there you will be able to pickup your hosting packages for listed domains. In this example I’ll be using my domain name, [url=http://www.mikroproje.net/:2a0r3ix5]mikroproje.net[/url:2a0r3ix5] as an example.[/size:2a0r3ix5]

[size=100:2a0r3ix5]4) Click [b:2a0r3ix5]check box[/b:2a0r3ix5] button and click on your domain name. Page will refresh with [b:2a0r3ix5]Hosting Account Details[/b:2a0r3ix5] like following picture.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]5) Click [b:2a0r3ix5]Open[/b:2a0r3ix5] button near your domain to open up [b:2a0r3ix5]Control Panel[/b:2a0r3ix5] for your hosting account. [b:2a0r3ix5]Hosting Manager [/b:2a0r3ix5]window will be open in a new window.[/size:2a0r3ix5]

[size=100:2a0r3ix5]6) In this window review important sections like [b:2a0r3ix5]Account Summary[/b:2a0r3ix5], [b:2a0r3ix5]Settings > ASP.NET Runtime[/b:2a0r3ix5] and make necessary changes if you need any.
[b:2a0r3ix5]It’s important that using ASP.NET 2.0 for DotNetNuke 4.x.[/b:2a0r3ix5]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]7) Ensure that [b:2a0r3ix5]FrontPage Extensions[/b:2a0r3ix5] (under Settings tab) is not installed. (I have forgotten to mention about this requirement at first revision of this tutorial)

If installed, [b:2a0r3ix5]FrontPage Extensions[/b:2a0r3ix5] may prevent you from managing [b:2a0r3ix5]directory permissions[/b:2a0r3ix5].[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step [/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]3: Virtual Directory Management
[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]In [b:2a0r3ix5]Hosting Manager[/b:2a0r3ix5] click on [b:2a0r3ix5]Content > Directory Management[/b:2a0r3ix5] button. [b:2a0r3ix5]Home > Content > Directory Management[/b:2a0r3ix5] page will open. Also open up [b:2a0r3ix5]Website[/b:2a0r3ix5] folder from extracted source package.[/size:2a0r3ix5] [size=100:2a0r3ix5]We are going to create [b:2a0r3ix5]Virtual Directories[/b:2a0r3ix5] and assign [b:2a0r3ix5]permissions[/b:2a0r3ix5] to these directories.[/size:2a0r3ix5] [size=100:2a0r3ix5]Click on [b:2a0r3ix5]Create Directory[/b:2a0r3ix5] button at bottom pane. (If you can’t see Create Directory button ensure that FrontPage extensions are not installed. If installed, simply uninstall them from Settings tab of Hosting Manager)[/size:2a0r3ix5] [b:2a0r3ix5][size=100:2a0r3ix5]Create a Custom Directory[/size:2a0r3ix5][/b:2a0r3ix5][size=100:2a0r3ix5] wizard page will open. Complete the form with following information:
[/size:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Step 1: Enter a name:[/color:2a0r3ix5][/b:2a0r3ix5] [b:2a0r3ix5]_sgbak[/b:2a0r3ix5]
[b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Step 2: Select permisions:[/color:2a0r3ix5][/b:2a0r3ix5] [b:2a0r3ix5]Read, Write[/b:2a0r3ix5]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]Click on [b:2a0r3ix5]Continue[/b:2a0r3ix5] and click on [b:2a0r3ix5]Add[/b:2a0r3ix5] buttons in order.[/size:2a0r3ix5] [size=100:2a0r3ix5]This is an example directory. [b:2a0r3ix5]_sgbak[/b:2a0r3ix5] contains [b:2a0r3ix5]visual studio template[/b:2a0r3ix5] file for DotNetNuke (DotNetNuke.vstemplate.2007-01-23.15-05-04.2416) (The numbers may differ)

Let’s make virtual directory creation process easier for further reading:[/size:2a0r3ix5][size=100:2a0r3ix5]Create [b:2a0r3ix5]App_Code[/b:2a0r3ix5], [b:2a0r3ix5]App_Data[/b:2a0r3ix5], [b:2a0r3ix5]App_Browser[/b:2a0r3ix5], [b:2a0r3ix5]bin[/b:2a0r3ix5], and [b:2a0r3ix5]Config[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read & Write[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]App_GlobalResources[/b:2a0r3ix5], [b:2a0r3ix5]Components[/b:2a0r3ix5], [b:2a0r3ix5]controls[/b:2a0r3ix5], [b:2a0r3ix5]DesktopModules[/b:2a0r3ix5], [b:2a0r3ix5]images[/b:2a0r3ix5], [b:2a0r3ix5]Install[/b:2a0r3ix5], [b:2a0r3ix5]js[/b:2a0r3ix5], [b:2a0r3ix5]Portals[/b:2a0r3ix5] and [b:2a0r3ix5]Providers[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read, Web [/b:2a0r3ix5]and[b:2a0r3ix5] Write [/b:2a0r3ix5]permissions.[/size:2a0r3ix5][b:2a0r3ix5][size=100:2a0r3ix5]Update:[/size:2a0r3ix5][/b:2a0r3ix5][size=100:2a0r3ix5] You also need sub virtual directories for [b:2a0r3ix5]DesktopModules[/b:2a0r3ix5] and [b:2a0r3ix5]App_Code[/b:2a0r3ix5] directories.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]DesktopModules\HTML[/b:2a0r3ix5] and [b:2a0r3ix5]DesktopModules\Links[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read[/b:2a0r3ix5], [b:2a0r3ix5]Web[/b:2a0r3ix5] and [b:2a0r3ix5]Write permissions[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]App_Code\HTML[/b:2a0r3ix5] and [b:2a0r3ix5]App_Code\Links[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read[/b:2a0r3ix5] and [b:2a0r3ix5]Write[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]godaddyroot[/b:2a0r3ix5] directory with [b:2a0r3ix5]Read[/b:2a0r3ix5], [b:2a0r3ix5]Web[/b:2a0r3ix5], [b:2a0r3ix5]Write[/b:2a0r3ix5], [b:2a0r3ix5]Set Root[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Check your settings again and click [b:2a0r3ix5]Add[/b:2a0r3ix5] button.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 4: Creating a MSSQL Server Database[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]In [b:2a0r3ix5]Hosting Manager[/b:2a0r3ix5] page, click on [b:2a0r3ix5]Databases[/b:2a0r3ix5] > [b:2a0r3ix5]SQL Server[/b:2a0r3ix5] button.

[/size:2a0r3ix5][size=100:2a0r3ix5]At [b:2a0r3ix5]MS SQL Server Databases[/b:2a0r3ix5], click on [b:2a0r3ix5]Create New Database[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]In [b:2a0r3ix5]Create SQL Server Database Wizard Instructions[/b:2a0r3ix5] page; write a simple description about your database at [b:2a0r3ix5]SQL Server Database Information[/b:2a0r3ix5] > [b:2a0r3ix5]Description[/b:2a0r3ix5] field. Check that [b:2a0r3ix5]Create DSN [/b:2a0r3ix5]option check box is signed. Provide your username and password at [b:2a0r3ix5]SQL Server Database Connection Information[/b:2a0r3ix5]. Make sure that [b:2a0r3ix5]Select Installation Option[/b:2a0r3ix5] > [b:2a0r3ix5]Install Schema Features[/b:2a0r3ix5] checkbox is signed. Click on [b:2a0r3ix5]Continue[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]In [b:2a0r3ix5]Verify SQL Server Database Changes Wizard Instructions[/b:2a0r3ix5] page, review your configuration and click on [b:2a0r3ix5]Create Database[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]System will process your request.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]After submitting your request you will see a message like following:
[b:2a0r3ix5]Successfully Submitted Information for Creation of SQL Server Database![/b:2a0r3ix5]
Notice that your newly created database’s status is currently [b:2a0r3ix5]Pending Setup[/b:2a0r3ix5].

[/size:2a0r3ix5][size=100:2a0r3ix5]This states that your request is being processed by Godaddy. Please wait approximately 15 minutes before continue.

After a break, lets continue with Database section. Your session may become ended. So may need to re-login to [b:2a0r3ix5]Control Panel[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]Now check that your database status changed to [b:2a0r3ix5]Setup[/b:2a0r3ix5] mode.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]This means your database is ready for usage.[/size:2a0r3ix5] [size=100:2a0r3ix5]You will see three icons at [b:2a0r3ix5]Actions[/b:2a0r3ix5] tab. Click on [b:2a0r3ix5]View Connection Strings icon[/b:2a0r3ix5] at Actions tab.[/size:2a0r3ix5] [size=100:2a0r3ix5]A [b:2a0r3ix5]pop-up[/b:2a0r3ix5] window will display your database connection strings. These strings are important and we need to implement connection strings to [b:2a0r3ix5]web.config[/b:2a0r3ix5] file. Copy the [b:2a0r3ix5]SqlConnection (.NET)[/b:2a0r3ix5] connection string and paste it into a [b:2a0r3ix5]notepad[/b:2a0r3ix5] file.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 5: Creating web.config File and Configuring Connection Strings and Other Settings (for SQL Server 2000/2005)[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5]Locate the extracted [b:2a0r3ix5]Source[/b:2a0r3ix5] package and navigate to [b:2a0r3ix5]Website[/b:2a0r3ix5] folder. Find [b:2a0r3ix5]release.config [/b:2a0r3ix5]file and rename it to [b:2a0r3ix5]web.config[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]You need to change [b:2a0r3ix5]Connection Settings and Application Settings[/b:2a0r3ix5] strings to enable the [b:2a0r3ix5]communication[/b:2a0r3ix5] between DotNetNuke and [b:2a0r3ix5]SQL Server[/b:2a0r3ix5]. Open up notepad file that contains [b:2a0r3ix5]SqlConnection (.NET)[/b:2a0r3ix5] connection string and implement it to your [b:2a0r3ix5]web.config[/b:2a0r3ix5] file like following example:
[/size:2a0r3ix5][b:2a0r3ix5]
[B][size=100:2a0r3ix5]Default Connection and Application Strings:[/size:2a0r3ix5][/b:2a0r3ix5][/B]
[code:2a0r3ix5]
<connectionStrings>
<!– Connection String for SQL Server 2005 Express –>
<add
name="SiteSqlServer"

connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />
<!– Connection String for SQL Server 2000/2005
<add
name="SiteSqlServer"
connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
providerName="System.Data.SqlClient" />
–>
</connectionStrings>
<appSettings>
<!– Connection String for SQL Server 2005 Express – kept for backwards compatability – legacy modules –>
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;
User Instance=True;AttachDBFilename=
|DataDirectory|Database.mdf;"/>
<!– Connection String for SQL Server 2000/2005 – kept for backwards compatability – legacy modules
<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
–> [/code:2a0r3ix5]

[size=100:2a0r3ix5][b:2a0r3ix5]Custom Connection and Application Strings for SQL Server 2000/2005[/b:2a0r3ix5] [/size:2a0r3ix5]
[size=100:2a0r3ix5](Works at Godaddy Hosting Packages – You need to modify Connection Strings with servername, database, username and password values – change this entries from notepad file that contains account specific information)[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<connectionStrings>
<!– Connection String for SQL Server 2005 Express
<add
name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" /> –>
<!– Connection String for SQL Server 2000/2005 –>
<add name="SiteSqlServer" connectionString="Server=godaddydatabaseservername;
Database=databaseid;uid=databaseloginusername;pwd=databaseloginpassword;"
providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!– Connection String for SQL Server 2005 Express kept for backwards compatability – legacy modules
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;
User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
–>
<!– Connection String for SQL Server 2000/2005 – kept for backwards compatability – legacy modules –>
<add key="SiteSqlServer" value="Server=godaddydatabaseservername;Database=databaseid;
uid=databaseloginusername;pwd=databaseloginpassword;" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[color=#000000:2a0r3ix5][size=100:2a0r3ix5]If you have trouble viewing code you can download sample web.config file from following link:[/size:2a0r3ix5]
[/color:2a0r3ix5][url=http://www.mynetnuke.com/Portals/3/docs/godaddy.zip:2a0r3ix5][color=#000000:2a0r3ix5][size=100:2a0r3ix5]Godaddy Sample Web Config File[/size:2a0r3ix5][/color:2a0r3ix5][/url:2a0r3ix5][color=#000000:2a0r3ix5][COLOR=#c0504d][size=100:2a0r3ix5][I DID THIS][/size:2a0r3ix5][/color:2a0r3ix5] [/COLOR]

[size=100:2a0r3ix5]You also need to disable [b:2a0r3ix5]Compression[/b:2a0r3ix5] feature from [b:2a0r3ix5]httpModules[/b:2a0r3ix5] section.[/size:2a0r3ix5] [size=100:2a0r3ix5]Find following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule,
DotNetNuke.HttpModules.Compression"/> [/code:2a0r3ix5] [size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5][code:2a0r3ix5]
<!– <add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule, DotNetNuke.HttpModules.Compression"/> –> [/code:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Update – Important Step:[/b:2a0r3ix5] You must also change [b:2a0r3ix5]UseInstallWizard[/b:2a0r3ix5] value to [b:2a0r3ix5]False[/b:2a0r3ix5] from [b:2a0r3ix5]appSettings[/b:2a0r3ix5] section. (Default value is true)[/size:2a0r3ix5]

[size=100:2a0r3ix5]Find the following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<add key="UseInstallWizard" value="true"/> [/code:2a0r3ix5] [size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5][code:2a0r3ix5]
<add key="UseInstallWizard" value="false"/> [/code:2a0r3ix5]

[size=100:2a0r3ix5]If you won’t disable the [b:2a0r3ix5]UseInstallWizard[/b:2a0r3ix5] feature, you will get [b:2a0r3ix5]permission[/b:2a0r3ix5] errors, and [b:2a0r3ix5]installation wizard[/b:2a0r3ix5] will warn you that it can’t continue.[/size:2a0r3ix5]
[size=100:2a0r3ix5]
By disabling Install Wizard you are going to make an [b:2a0r3ix5]advanced DotNetNuke install[/b:2a0r3ix5].

[b:2a0r3ix5]Optional:[/b:2a0r3ix5] You may need to [b:2a0r3ix5]register your app_code subfolders to generate granular assemblies during compilation[/b:2a0r3ix5] (following example contains information about how to apply subfolders for [b:2a0r3ix5]HTML[/b:2a0r3ix5], [b:2a0r3ix5]XML[/b:2a0r3ix5] and [b:2a0r3ix5]Survey[/b:2a0r3ix5] modules.

[b:2a0r3ix5]Note:[/b:2a0r3ix5] If you want to install these modules you must include their subdirectories under [b:2a0r3ix5]web.config[/b:2a0r3ix5] like following example. Some modules are problematic under [b:2a0r3ix5]medium trust[/b:2a0r3ix5] environments, but the workaround is simple. (However this solution does not always work with third party modules – eg: Bi4ce GoMap)

Find following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<!– register your app_code subfolders to generate granular assemblies during compilation
<codeSubDirectories>
<add directoryName="sub-directory name"/>
</codeSubDirectories> –> [/code:2a0r3ix5]

[size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– register your app_code subfolders to generate granular assemblies during compilation –>
<codeSubDirectories>
<add directoryName="HTML" />
<add directoryName="Survey" />
<add directoryName="XML" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[size=100:2a0r3ix5][b:2a0r3ix5]Optional:[/b:2a0r3ix5] If you want to [b:2a0r3ix5]upload large files[/b:2a0r3ix5] with [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5], you must configure web.config to allow large file uploads.

Default section is allows you upload a maximum of 8192 kb (8 MB)[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– allow large file uploads –>
<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192"/>
<httpCookies httpOnlyCookies="true" requireSSL="false" domain="" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[size=100:2a0r3ix5]I’m using a custom string configured for allowing large file uploads – a maximum of 262144 kb (256 MB):[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– allow large file uploads –>
<httpRuntime executionTimeout="400000" useFullyQualifiedRedirectUrl="true" maxRequestLength="262144" requestLengthDiskThreshold="262144" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 6: Sending Website Folder to FTP[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=120:2a0r3ix5][b:2a0r3ix5]Update:[/b:2a0r3ix5] [b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Prevent Other Users to Access Host and Admin Accounts After Upload[/color:2a0r3ix5][/b:2a0r3ix5] [/size:2a0r3ix5]
[size=100:2a0r3ix5]Now navigate to local [b:2a0r3ix5]Website[/b:2a0r3ix5]\[b:2a0r3ix5]Install[/b:2a0r3ix5] folder from Windows Explorer
For example: [b:2a0r3ix5]C:\Documents and Settings\Administrator\Desktop\DotNetNuke_4.5.1_Source\Website\Install[/b:2a0r3ix5]
And open up DotNetNuke.install.config file with a text editor (like notepad) and change host and admin user account passwords. (default host password is: dnnhost and default admin password is: dnnadmin)
Save the file and close the application.

After finishing previous steps you need to upload your files to the web server via FTP. You may want to use a free client like[url=http://filezilla.sourceforge.net/:2a0r3ix5]Filezilla[/url:2a0r3ix5] for uploading your files to web server.
[/size:2a0r3ix5][b:2a0r3ix5]
[size=100:2a0r3ix5]Lets explain how to use Filezilla for your hosting account.[/size:2a0r3ix5][/b:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Download[/b:2a0r3ix5] and [b:2a0r3ix5]install[/b:2a0r3ix5] latest version of [b:2a0r3ix5]Filezilla client[/b:2a0r3ix5] and run it. Use [b:2a0r3ix5]CTRL+S[/b:2a0r3ix5] combination to open up [b:2a0r3ix5]Site Manager[/b:2a0r3ix5] window. Create [b:2a0r3ix5]new website profile[/b:2a0r3ix5] for your website (you may skip this step if website profile already exists).[/size:2a0r3ix5]

[size=100:2a0r3ix5]In [b:2a0r3ix5]Site Details[/b:2a0r3ix5] section enter your domain at [b:2a0r3ix5]Host[/b:2a0r3ix5] field. [b:2a0r3ix5]Default port[/b:2a0r3ix5] value is [b:2a0r3ix5]21[/b:2a0r3ix5]. Do not change this value unless told otherwise. Default value for [b:2a0r3ix5]Server type[/b:2a0r3ix5] field is [b:2a0r3ix5]FTP[/b:2a0r3ix5]. Do not change this field too. Choose [b:2a0r3ix5]Normal[/b:2a0r3ix5] as [b:2a0r3ix5]Logon Type[/b:2a0r3ix5]. Provide your [b:2a0r3ix5]username[/b:2a0r3ix5] and [b:2a0r3ix5]password[/b:2a0r3ix5] at [b:2a0r3ix5]User[/b:2a0r3ix5] section. Click on [b:2a0r3ix5]Save and Exit[/b:2a0r3ix5] button to record changes.

Use [b:2a0r3ix5]CTRL+S[/b:2a0r3ix5] again to open up and connect to newly created Website. Choose your website and click on [b:2a0r3ix5]Connect[/b:2a0r3ix5] button.[/size:2a0r3ix5]

[size=100:2a0r3ix5]After connecting you will see storage area at right pane. [b:2a0r3ix5]Remote site[/b:2a0r3ix5] field should include your website account username (for example: /username). Also you should see the virtual directories created at [b:2a0r3ix5]Step 3[/b:2a0r3ix5].

Now navigate to local [b:2a0r3ix5]Website[/b:2a0r3ix5] folder (extracted from source package at [b:2a0r3ix5]Step 1[/b:2a0r3ix5]) from [b:2a0r3ix5]Local Site[/b:2a0r3ix5] field at left pane.[/size:2a0r3ix5]

[size=100:2a0r3ix5]For example: [b:2a0r3ix5]C:/Documents and Settings/Administrator/Desktop/DotNetNuke_4.5.1_Source/Website[/b:2a0r3ix5].

[b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Important note:[/color:2a0r3ix5][B]Upload all folders[/b:2a0r3ix5] (!) in the [b:2a0r3ix5]/DotNetNuke_4.5.1_Source\Website[/b:2a0r3ix5] directory to [b:2a0r3ix5]/username/[/b:2a0r3ix5] directory at FTP server. But do not upload [b:2a0r3ix5]files[/b:2a0r3ix5] yet.
[/B]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]Upload all remaining files (!) to /username/godaddyroot/ directory at FTP server.[/size:2a0r3ix5]

[size=100:2a0r3ix5]Since we cannot change root permissions of our username directory, we need an alternative way. It comes at next paragraph.

After finishing uploading files, read following section carefully!!!
Navigate to /username/godaddyroot/ directory from FTP client. Select all files with pressing CTRL+A keys. Move (you can use drag and drop feature) all of the files to parent directory (/username/ directory).

Navigate to /username/Config/ directory from FTP client. Simply select Compression.config, SiteUrls.config and SolutionExplorer.oml.config files and drag and drop them to parent directory (/username/ directory).[b:2a0r3ix5]

[B][color=#a0a0a0:2a0r3ix5]Knowledge Base: The difference between Copy and Move actions.[/color:2a0r3ix5][/b:2a0r3ix5]
[/B]Copying files between directories do not keep file permissions. The files inherit new permissions of directory. But moving files keeps file permissions. So in this example we practiced how to fight with Godaddy.

Lets say we have two directories called Directory A, Directory B.
Directory A is a parent directory and has only read permission.
Directory B is a sub directory and has read, web, write and root permissions.

If we copy files at Directory B and paste them under Directory A, effective permissions of the files will be only read. Because files will inherit permissions of Directory A.
But if we move files from Directory B to Directory A file permissions will remain.

You can practice this example with your operating system (Windows XP, Windows 2000, Windows Server 2003 and Windows Vista) (With NTFS permissions) [/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 7: Installing DotNetNuke[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Lets continue with last step to install DotNetNuke over Godaddy root directory[/b:2a0r3ix5].
After moving files from [b:2a0r3ix5]/username/godaddyroot/[/b:2a0r3ix5] to [b:2a0r3ix5]/username/[/b:2a0r3ix5] you should be able to install [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5] without any errors.

[b:2a0r3ix5]Browse[/b:2a0r3ix5] http://www.yourwebsiteaddress.com/Insta … de=Install and [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5] installation will start. Ensure that installation completes without any errors. Once installation completed you should immediately change your [b:2a0r3ix5]Host[/b:2a0r3ix5] and [b:2a0r3ix5]Admin[/b:2a0r3ix5] accounts’ passwords.

If you have any errors while installing DNN, please read this [b:2a0r3ix5]documentation[/b:2a0r3ix5] again. If you believe this installation documentation misses some important step, contact me privately at (labfxdx at gmail dot com). Also you may want to discuss other issues about Hosting companies like Godaddy at our tech support forum (beta).

[b:2a0r3ix5]About this article:[/b:2a0r3ix5] This article is based on Official DotNetNuke Installation Guide (comes with Documentation Guide) and Unofficial [url=http://www.mikroproje.com/DotNetNukeArticles/tabid/283/articleType/ArticleView/articleId/79/Default.aspx:2a0r3ix5]How to Install DotNetNuke to Godaddy Root Folder[/url:2a0r3ix5] article (written by [url=http://www.mikroproje.com/:2a0r3ix5]Ismet Dumlupinar[/url:2a0r3ix5]) and contains important steps about installing DotNetNuke 4.5.0 and DotNetNuke 4.5.1 to Godaddy Root Folder.

[b:2a0r3ix5]My next article will contain following information.[/b:2a0r3ix5][/size:2a0r3ix5]
[size=100:2a0r3ix5]How to upgrade Godaddy Hosted DotNetNuke 4.4.1 to DotNetNuke 4.5.1.

This article will be based on Mitchell Seller’s articles.
[url=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/55/DotNetNuke-Upgrade-Tips-Lessons-Learned.aspx:2a0r3ix5]DotNetNuke Upgrade Tips[/url:2a0r3ix5]
[url=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/22/Default.aspx:2a0r3ix5]Upgrading DotNetNuke from Previous Versions[/url:2a0r3ix5]
[/size:2a0r3ix5]

If you want to
remove
the ‘
Search
Web’ and ‘
Search
Site’ radio buttons from your DotNetNuke instance, you will have to open up the ascx for whatever skin you are using, and change the markup for the skin object like so:

[code:2qscbsur]
<dnn:SEARCH runat="server" id="dnnSEARCH" showWeb="False" showSite="False" />[/code:2qscbsur]

I have a shared hosting plan with multiple domain names. One domain is the main one for the root, but I have other domain names which I want to both point to the root (since I run DotNetNuke from the root), as well as to subfolders so that I can run multiple web sites with my limited hosting plan.
Since my host won’t let me point additional domains to subfolders (the additional domain names are all aliased to the same root location), I need a way to redirect them to a subfolder based on the domain name,

Here’s how to do it

Create a file named [b:m19iu2un]default.asp[/b:m19iu2un] and place it in the root folder. This will be checked whenever any of my domains are requested, and it will redirect as needed. Note that this code also handles both [b:m19iu2un]www [/b:m19iu2un]and [b:m19iu2un]non-www [/b:m19iu2un]URL references.

The specifics

The domains maindomain.com and maindomain2.com should point to the file named default.aspx in the root (and DotNetNuke takes care of redirecting them to the correct portal).

The domain otherdomain.com should point to a subfolder of the root named subfolder.

<%response.buffer=true%>
<%
where=Request.ServerVariables("SERVER_NAME")
Select Case where
case "www.maindomain.com"
response.redirect "default.aspx"
case "maindomain.com"
response.redirect "default.aspx"
case "www.maindomain2.com"
response.redirect "default.aspx"
case "maindomain2.com"
response.redirect "default.aspx"
case "www.otherdomain.com"
response.redirect "/subfolder"
case "otherdomain.com"
response.redirect "/subfolder"
End Select
%>

This step is the first part of the process as you must know how to access to the database to complete the DotNetNuke Restore.

[size=130:ri0nnxr4]Restoring To SQL Server 2000[/size:ri0nnxr4]

If you are using SQL Server 2000 you will want to use the below steps, please see the SQL Server 2005 steps for restoring to SQL Server 2005 using SQL Server Management Studio Express.
[list=1:ri0nnxr4]
[*:ri0nnxr4]The first step is to create a new blank database with the same name as your existing database. To do this simply right click on your server and select “Create Database” providing the database name[/*:m:ri0nnxr4]
[*:ri0nnxr4]Right-click on your new SQL Server database[/*:m:ri0nnxr4]
[*:ri0nnxr4]Select “All Tasks” -> “Restore Database”[/*:m:ri0nnxr4]
[*:ri0nnxr4]Select “From Device” as the “Restore:” option[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click “Select Devices” then “Add”[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click the “…” button to browse for your .bak file, then press “Ok” to add it to the list[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click “Ok” to get back to the “Restore Database” window, then switch to the “Options” tab[/*:m:ri0nnxr4]
[*:ri0nnxr4]Ensure that the “Force Restore over Existing Database” checkbox is selected[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click the “Ok” button to begin the restore process[/*:m:ri0nnxr4]
[*:ri0nnxr4]Once completed you should receive a message stating restore successful![/*:m:ri0nnxr4][/list:o:ri0nnxr4]
If you have restored this to a different database server, or to a different database name be sure to follow the optional Web.Config change instructions below, otherwise you will not be able to access your database

[size=130:ri0nnxr4]Restoring to SQL Server 2005[/size:ri0nnxr4]

If you are using SQL Server 2005 you may use the below steps to restore your database backup to the server.
[list:ri0nnxr4]
[*:ri0nnxr4]The first step to successfully restoring a database is to create a new database on your server. This is accomplished by right clicking on the “Databases” item in SQL Server Management Studio Express (SSMSE) and selecting “New Database”[/*:m:ri0nnxr4]
[*:ri0nnxr4]If possible the database name that you create should be the same as the one you are restoring, but it is not required[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now that you have a database right-click on it and select “Tasks” -> “Restore” -> “Database”[/*:m:ri0nnxr4]
[*:ri0nnxr4]Select “From Device” as the source[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click the “…” button, then click “Add” in the window that appears[/*:m:ri0nnxr4]
[*:ri0nnxr4]Find your .bak file then press “Ok” twice to return to the restore database window[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now you will see a list of backup sets to restore, select the MOST recent backup by placing a check box in the “restore” column.[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now switch to the “options” page (upper left of the window)[/*:m:ri0nnxr4]
[*:ri0nnxr4]Ensure that the “Overwrite the Existing Database” is checked[/*:m:ri0nnxr4]
[*:ri0nnxr4]Ensure that the “Restore As” column indicates the proper .mdf and .ldf locations for your specific server. If needed you may change these using the “…” buttons. (Typically needed for restores provided by a hosting company to a non-hosting company location).[/*:m:ri0nnxr4]
[*:ri0nnxr4]Press “Ok” to restore your backup[/*:m:ri0nnxr4][/list:u:ri0nnxr4]
This should now have your database up and running on the new server. REMEMBER: if you changed your database server name, or your database name from your previous configuration you will need to follow the optional web.config changes listed below.

[size=130:ri0nnxr4]Restoring the DotNetNuke Installation[/size:ri0nnxr4]

Follow the below steps to restore your DotNetNuke Installation, these instructions are assuming restoring to a new server that has NOT been configured to host your DotNetNuke site.
[list=1:ri0nnxr4]
[*:ri0nnxr4]Using windows explorer navigate to c:\inetpub\wwwroot, then right click and select “New” -> “Folder” and create a folder with the same name as your existing DNN installation. (If you installed to a different location you may simply navigate to that path and substitute it for any further path references)[/*:m:ri0nnxr4]
[*:ri0nnxr4]Open your DotNetNuke backup zip file[/*:m:ri0nnxr4]
[*:ri0nnxr4]Select “Extract All Files/Folders”[/*:m:ri0nnxr4]
[*:ri0nnxr4]For the extraction location select the new folder created in step 1[/*:m:ri0nnxr4]
[*:ri0nnxr4](OPTIONAL) If in the database restore process above you changed your server or database name, you will need to modify your web.config file to note the changes. (See [url=http://www.mitchelsellers.com/Default.aspx?tabid=54&EntryID=30:ri0nnxr4]this[/url:ri0nnxr4] tutorial for assistance)[/*:m:ri0nnxr4][/list:o:ri0nnxr4]

[size=130:ri0nnxr4]Creating New Virtual Directory (If Needed)[/size:ri0nnxr4]

If you are restoring your application to the same folder on your working production server, you should now have a fully restored copy of your site. If you are moving to a different server or have restored to a path on the same server that does not have a virtual directory configured you will need to follow the below steps.
[list=1:ri0nnxr4]
[*:ri0nnxr4]Open the IIS Snap-In tool, this can be found via “Start” -> “Settings” -> “Control Panel” -> “Administrative Tools” -> “Internet Information Services”[/*:m:ri0nnxr4]
[*:ri0nnxr4]Expand the root nodes until you can expand the “Default Web Site” node[/*:m:ri0nnxr4]
[*:ri0nnxr4]You should see your newly created folder listed with a standard folder icon[/*:m:ri0nnxr4]
[*:ri0nnxr4]Right-click on the folder and choose “Properties”[/*:m:ri0nnxr4]
[*:ri0nnxr4]On the first tab click “Create” next to the application name. The application name displayed should be the same as your previous installation. IF NOT you will need to modify the “Portal Alias” table to update to the new application name[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now, switch to the “Documents” tab. Remove all current default documents and add in default.aspx[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now, switch to the “Directory Security” tab[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click “Edit” in the “Anonymous Access and Authentication Control” area[/*:m:ri0nnxr4]
[*:ri0nnxr4]Ensure that a checkmark is placed in the “Anonymous Access” option at the top of the window and press “Ok” to exit[/*:m:ri0nnxr4]
[*:ri0nnxr4]Now switch to the “ASP.NET” tab and ensure that “2.0.50727” is selected for the ASP.NET version[/*:m:ri0nnxr4]
[*:ri0nnxr4]Click “Ok” to save your changes and complete IIS Setup[/*:m:ri0nnxr4][/list:o:ri0nnxr4]
If you did not change your application name you should now be able to view your application. If you have specified a different application name, you will need to modify any entries in the PortalAlias table that reference your old application name. This should provide you a quick guide to restoring or moving a DNN installation to a new server. Please let me know if you have any questions/comments/concerns. My forum is also available for anyone that would like assistance with any errors that might come up.