SQL Server 2000 - Connecting to a named SQL 200 instance

Question

SQL Server 2000 - Connecting to a named SQL 200 instance

Gary Cobden

Ten Centuries

Points: 1269
More actions
June 16, 2009 at 3:28 am

#95425

Morning
I have a Server running SQL Server 2000 SP4 which has both a default and named instance installed
From my PC using Enterprise Manager I can connect to the default instance without a problem, however I cannot connect to the named instance. The named instance does have 'Allow Remote Connections' set.
Can anybody assist with a solution please

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Chand00 SSCertifiable Points: 6466 More actions · Answer 1

Can you check whether port on which the named instance is running is open. And what is the error message that you get when trying to connect. Are you trying to connect from other machine. Check out the event viewer on the server for more info

Thanks

Chandra Mohan N

[font="Verdana"]Thanks
Chandra Mohan[/font]

Gary Cobden Ten Centuries Points: 1269 More actions · Answer 2

Sorry, how do I check if the Port is open - and if it is closed, how do I open it?

Error message is

SQL Server does not exist or access denied

Connection Open(Connect())

I am trying to connect to the instance on the Server from my PC via Client Tools - I can see the instance fine on the Server

Thanks

ankur_libra Hall of Fame Points: 3999 More actions · Answer 3

I hope that you must be specifying the name of the named instance while accessing it.

Moreover, check that specific SQL service for that instance should be running on the server.

If not, then start that service. Only then u will be able to connect to that instance.

Gary Cobden Ten Centuries Points: 1269 More actions · Answer 4

Affirmative to all 3 statements, nut still cannot access

george sibbald SSC Guru Points: 104210 More actions · Answer 5

if not already done so in EM properties\security set audit level to failed logins only. This will give you more info on the error in the errorlog and the application event log. If you don't get an error you know its not even reaching SQL.

---------------------------------------------------------------------