I'm trying to move a DNN database from our dev environment SQL Server [2005] to our production environment SQL Server [2008]. I've done this fo several other DNN instances on our network without a hitch, so I'm at a loss for why this time is a problem.
The DNN instance I'm moving the database for is a DNN 4.9.1 site running on IIS6/Windows Server 2003.
Original Configuration - works fine
192.168.200.12 is the dev environment db server [SQL Server 2005]
web.config - both the connectionStrings and appSetttings connection strings point to
connectionString="Server=192.168.200.12;Database=dnndb;uid=user;pwd=pass"
Database Move
- detach db from dev db server
- copy to production db server
- attach to production db server [SQL Server 2008]
- add a new user for the db server in [server]/Security
- add a new database user associated with the new server user
- verify that the newly created user/password has access to the server and database with SSMS
- Modify web.config connection strings in the DNN installation
connectionString="Server=192.168.100.20;Database=dnndb;uid=user2;pwd=pass2"
- Stop/Restart web Site
- Browse to DNN Site - looks fine
Next, I detach db from original dev db server and refresh DNN site default page in browser and I get the following error: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
I refresh the page again and from then on, I get: Cannot open database "dnndb" requested by the login. The login failed. Login failed for user 'user'.
If I then shut down the dev environment db server and refresh the DNN site default page, I get the following error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have also tried stopping and restarting the specific web site as well as stopping and restarting the entire IIS web service and the problem persists after the restarts.
About the only thing different about this website from the other DNN sites that we have in production is that this site is using the AliCommerce 2.1.5 DNN module.
Any ideas on troubleshooting or fixing this would be appreciated.