July 23, 2007 at 6:05 am
Hi,
I hope someone can help me out here? I have a fresh install of SQL Server 2000 (standard edition - sp4), on a server running Windows 2003 SE (v 5.2.3790). I am trying to create a system dsn on my client pc (running Windows 2000) to a newly created database in SQL server called BLISS.
I am getting the following error message:
Connection failed:
SQL State :'01000'
SQL Server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (Connect()).
Connection Failed:
SQL State :'08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
From support.micrsoft.com I have tried changing the TCPPort value to 0, but this has not helped. Does anyone have any further ideas please?
Jackie
July 23, 2007 at 6:11 am
Is the TCP protocol correctly set. Try using named pipes to create the DSN instead of TCP.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 23, 2007 at 6:14 am
July 23, 2007 at 6:22 am
July 23, 2007 at 6:25 am
Hi,
Yes, that is exactly the same error message. Could you please explain how you got around it? Which machine do I run the client config thing on? Control Panel on my office pc is locked down apart from creating dsns, and I can't get to a command prompt either! Obviously we have technical people here to help, but i need to be able to show them your solution in full before I give them a ring, as they are really busy today.
Hope you can help?
July 24, 2007 at 4:33 am
July 24, 2007 at 5:44 am
You need to check the client configuration properties of sql server. This can be done using typing cliconfg in run command. Then do the necessary property cahnge.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 24, 2007 at 11:03 am
Hi,
I got into cliconfg.exe on my pc. I added TCP/IP and named pipes for the general tab, but these were already there for the server running SQL Server 2000. Port numbers match with those on the server. Is there something that I am missing? Maybe a server setting?
Thanks for you advice so far. I am learning a lot.
July 24, 2007 at 11:58 pm
Try using query analyzer to see if the connections succeeds. Also from the server check if remote connections are set to on also try my previous advice of creating the DSN using named pipes instead of TCP.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 26, 2007 at 10:18 am
Have you tried connecting with Bliss's IP (XXX.XXX.XXX.XXX) instead of the name? Or tried the fully qualified domain name e.g. bliss.med.com? If you could get to a command prompt I would recommend you pinging the server by ip and by name to see if you can even get a response from it. Also what about firewalls (either software or hardware) between the servers?
Good luck!
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy