GYMM8
asked on
Microsoft SQL Server connection issue in debug
Hi Experts,
I have a strange anomoly that is occuring. My published site accesses my data no problem but when I try and run it in debug I get a connection failure which is:
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
Now like I said, if I publish the website it works fine so the above error is only occuring when I run this in development. Also any attempt to create an ODBC connecting using ODBC Administrator return the same error.
The database lives on a Windows 2008 virtual server and the only thing that recently changed here was that they increased my allocated memory and disk storage space
Any ideas?
I have a strange anomoly that is occuring. My published site accesses my data no problem but when I try and run it in debug I get a connection failure which is:
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
Now like I said, if I publish the website it works fine so the above error is only occuring when I run this in development. Also any attempt to create an ODBC connecting using ODBC Administrator return the same error.
The database lives on a Windows 2008 virtual server and the only thing that recently changed here was that they increased my allocated memory and disk storage space
Any ideas?
bbao
For the very first step, are you able to ping the SQL sever in the dev environment?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Always check the firewall. If something stops working that used to work and you've done nothing different on sql server or vs .net side then it's usually the middle man!
as i mentioned, always first ping, that would quickly tell you if firewall could be an issue. :-)