April 23, 2010 at 10:59 am
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) (Microsoft SQL Server, Error: 2).
What I’ve done: All SQL Services are started. SQL Server Surface Area Configuration Remote Connection is set to Named Pipes or TCP/IP.
What else should I do?
KR,
RonKin
April 26, 2010 at 8:39 am
It tries to place in management studio the local name or localhost when it will be to logar.
April 26, 2010 at 8:43 am
I'm sorry I don't understand, what you mean by logar.
Thanks,
RonKin
April 26, 2010 at 11:18 am
You would need to verify that the network name of the SQL instance is accessible. If you can access it by entering the IP address then there is probably a DNS issue.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 29, 2010 at 6:29 am
I had a similar problem and it turned out to be because the SQL Server Browser service was not running on the SQL server I was trying to connect to. This service provides SQL Server connection information to client computers, so as well as configuring named pipes/tcp ip etc, this needs to run I think
April 29, 2010 at 6:37 am
Also make sure there isn't a firewall that is blocking the TCP port SQL is running on. (1433 by default)
The Redneck DBA
May 3, 2010 at 12:58 pm
Firewall is not on for server.
May 3, 2010 at 1:00 pm
SQL Server Browser Service is started.
May 4, 2010 at 3:10 am
I know it's a bit obvious but it might be worth checking the SQL logs on the server you're trying to connect to. If there is a problem with remote connections it might give you a hint. Sometimes it's quite specific and therefore useful!
May 4, 2010 at 7:13 am
Finally got connected. Thank you all for your help.
RonKin
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply