August 18, 2009 at 12:09 pm
This is the message:
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)
My dedicated admin connection port is 51780
My default port is 49161
The this I did:
1. I installed SQL Service Pack 3, but it's important to say that my SQL Server has never worked.
2. I enabled TCP/IP connections in the Surface Area Configuration.
3. In the Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\SuperSocketNetLib\Tcp\IPX I changed the TcpPort to my default port (49161)
4. The same as step 3 a changed to my default port the port number in the Configuration Manager of my instance.
5. I switched off my firewall (hehe).
6. I created an alias and it doesn't work.
Other details are:
Can not connect using localhost, I just can connect using ServerName\InstanceName and the alias I created.
In the network databases I don't see all of them and the ones I see I can't connect to them.
Don't know if it's a security issue and/or compability issue?
I'm really desperate, please help guys.
August 18, 2009 at 1:09 pm
The error message states that NAMED PIPES did not work so enabling TCP won't work. Maybe this article will help, http://msdn.microsoft.com/en-us/library/ms188247.aspx
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
August 18, 2009 at 2:09 pm
Thanks. I tried all of the axamples showed in the link and all of them were OK.
Also I tried to use telnet with my ports and run OK.
I checked the LogFile and I looked there was the following message:
"SQL Server is not ready to accept new client conecctions..."
Then I googled the message and I found http://support.microsoft.com/kb/929376 that it´s the hotfix and I installed it. Finally I restarted the machine and remains the issue 🙁
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply