Posts Tagged ‘dotnetnuke’

DotNetNuke 4.08.01 Installation Tips

March 4, 2008

I was having trouble installing DotNetNuke (DNN) on SQL server 2000. It was giving me the error message that user cannot be recognized etc. Although user and database was properly set up. What was wrong is that by default the database connection string which is active (uncommented) in web.config file is for SQL Server Express 2005. The connection string for SQL Server 2000 is actually commented out.

I could not notice it – although i was making changes to the SQL 2000 settings it was not making any sense. Finally i could catch the culprit comment in both “connectionStrings” and “appSettings” section of the web.config file.

The active SQL Server 2000 settings for my web.config file is as below. The SQL Express 2005 settings are commented out:

<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=dnn; pwd=dnn;"
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=dnn; pwd=dnn;"/>
</appSettings>