Hello everyone!
I'm in a bit of a pickle because of my lack of knowledge of SQL. So, I'm begging for some mercy here on getting me on the right track.
My company hosts it's internal website on a Windows Server 2003, IIS 6.0 with DNN 5.0 connecting to a MS SQL Express 2005 Database.
Due to a few constraints and other server upgrades, I'm hoping to host the SQL portion of the website on our ultra-awesome SQL server machine. (64 bit, MS SQL 2005 Standard, Windows 2003 Server in a domain)
Here lies the problem and what I have tried so far.
I have installed SQL 2005, backed up the database on the SQL Express machine, Restored the backup on the new Awesome Server, ensured that there were appropriate permissions on the new Database, and made these changes in the web.config file
Red is what used to be used
Green is what is now.
<!-- 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=cenanfp01;Database=DotNetNuke;uid=sa;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=cenanfp01;Database=DotNetNuke;uid=sa;pwd=*******;"/>
I am able to get connected to the server, but I only get a
This site is currently Unavailable
Please check back later
Any thoughts or ideas? I'll date an ugly sister of yours for the answer. 
Gord