My life turned into a nightmare on Sunday when I got a 500 Error on my website.  I did what the host knowledgebase said and reset IIS, and since then my remote connection to a SQL 2005 DB is not working at all.  I had them do a full upgrade, which I needed done anyway, but still no luck.  The module I use - Indoogrid, which is fantastic - appears to be working fine and there are no issues with the SQL 2005 DB.  I can connect to it just fine, but not through DNN.

The admins who host my SQL 2005 DB said it is a web config issue, that somehow the connection string got changed back to the old "Data Source=mssql503.myhost.com" setting.  It needs to be Data Source=mssql505.myhost.com. 

But my DNN host (who shall go nameless as I am not happy with them right about now) said "The only web.config file we have access to is that of your main DNN site, which needs to have it's database settings pointed at the SQL Server running on our side. If this is changed to point somewhere else the rest of the DNN installation will fail to load."

I guess the question is, who do I safely add the correct remote DB connection string to the web.config file without crashing my whole site?  Any ideas?  Thanks. 

The site is up, but the database module won't load due to the connection string issue. My concern is how to add the sql server 2005 express connection string to the web.config file without breaking my site?

Thanks.

I don't get it, how can your site be up if its not connecting to the db?

---

Philip Beadle - Employee