I'm stumped.
I've got an instance of SQL 2000 (staging\staging2000) running on a box side-by-side just fine with an instance of SQL 2005. When I'm working in Visual Studio on the staging box, it works just fine. I connect and get into the 2000 instance of the database with no problems.
As soon as I move over to my laptop (same configuration), I get ...
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
My connection string is calling the SQL 2000 instance properly (as far as I know).
server=staging\staging2000;initial catalog=xxxxx;uid=xxxxx;password=xxxxx;
The .net connector is apparently trying to connect to the 2005 instance. I'm stumped. Anyone have any suggestions?
Print | posted on Monday, April 24, 2006 7:17 AM