November 9, 2007 at 9:48 am
Hello all,
I recently installed a named instance of sql2005 (standard edition) on a server that already has a default sql2000 instance.
I could connect to the database engine of the named instance.
Today I installed SP2 for SQL2005, and since that moment I get the following message when trying to connect to the named instance using Management Studio:
"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 SQL Network Interfaces, error 26 - Error Locating Server/Instance Specified ) (Microsoft SQL Server)"
I have checked SQL browser, this is running.
I have TCP/IP, Shared Memory, and Named Pipes active.
I am trying to connect using Management Studio on my local computer, and I am logged in on our domain, which is the same domain as the sql server host computer is on.
I can connect to the named instance using sqlcmd.
It is just that Management Studio does not "see" the named instance in the list of available servers anymore, while before updating to SP2, this named instance was visible.
Any help is greatly appreciated.
Hans
November 9, 2007 at 11:40 am
Hi H,
In these cases I create the Client Alias where I explicitly specify the protocol, port, the server name etc. To create the new alias use SQL Server Configuration Manager.
If you say you can connect using sqlcmd then I guess your SQL Server is running OK, sometimes it does not start by itself after SP install.
Unrelated to your server: SQL Browser requires port 1434 to be open and your Infrastructure may close it.
Regards,Yelena Varsha
November 10, 2007 at 8:50 pm
Can you connect to the instance on the server itself? Have you tried connecting to the instance from a different system other than your own?
K. Brian Kelley
@kbriankelley
November 12, 2007 at 1:04 am
I have tried to connect from another client, this also results in the same error.
I have not installed Management Studio on the server itself (our company has the policy not to install client applications on server machines), so I do not know, but it is a good idea, so I will install MS temporarily to see what it brings.
Thanks for replying.
Hans
November 12, 2007 at 6:55 pm
You can get the same result by trying to create an ODBC data source on the server referencing the instance. All you're trying to do is validate connectivity. However, if you're having problems from other clients as well, that would say it's not your particular workstation.
Obtain the IP address for the named instance. Using SSMS, try and connect to the named instance by using *server name*,*tcp port*. For instance, if your SQL Server is named OrionsBelt and the tcp port specified in SQL Server Configuration Manager is 7745, you would attempt to connect to OrionsBelt,7745.
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply