Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Connection Failed: SQL STATE: '01000' Server Error: '10060' [ODBC SQL Server Driver][TCP/IP Sockets] Expand / Collapse
Author
Message
Posted Thursday, June 20, 2013 12:46 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, June 21, 2013 1:40 PM
Points: 1, Visits: 6
Hi,

My Server has installed with SQL 2000 and iam trying to connect to SQL Server through ODBC and iam getting the following error

Connection Failed:
SQL STATE: '01000'
Server Error: '10060'
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectOpen
(Connect())
Connection failed:
SQLState: '08001'
SQL Server Error: 17

From the same network iam able to connect from another system. Both the systems are Windows 7 64 bit

Can some one help me to sort this out. Awaiting for some solution. Thanks in advance.
Post #1465900
Posted Sunday, September 1, 2013 2:51 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 6:32 AM
Points: 971, Visits: 301
Hello,

A first remark : SQL Server 2000 is no longer supported ( even in extended support ).The same thing is occurring shortly for SQL Server 2005 ( all SP ). It would be useful to upgrade your SQL Server towards SQL Server 2008 R2 ( the direct jump to SQL Server 2012 is impossible ).
Usually , when I have a problem of connection to a SQL Server , I am searching the answer in the SQL Server Protocols Blog
http://blogs.msdn.com/b/sql_protocols/ where I find quickly a solution to my problem.
But you are using SQL Server 2000 and I have noticed a little sentence which could make more difficult to find the solution
"One of the more visible changes we made in connectivity space for SQL Server 2005 was enhancing error messages reported to the user in case of connection failures"
- SQL Browser is not existing before SQL Server 2005 which makes less easy the remote connections
see http://blogs.msdn.com/b/sql_protocols/archive/2005/09/22/473111.aspx and
http://blogs.msdn.com/b/sql_protocols/archive/2005/09/22/473111.aspx
http://blogs.msdn.com/b/sql_protocols/archive/2005/09/28/474698.aspx
Some useful links :
http://blogs.msdn.com/b/sql_protocols/archive/2006/09/30/sql-server-2005-remote-connectivity-issue-troubleshooting.aspx
http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx
Even if these articles were written for SQL Server 2005 and over , some ideas they provided could be useful for you

A last thing : which is the last service pack installed on your SQL Server ? Which is the edition also ?
Have a nice day
Post #1490481
Posted Sunday, September 1, 2013 3:08 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 6:32 AM
Points: 971, Visits: 301
Hello ,

Have you read this thread ?
http://www.sqlservercentral.com/Forums/Topic780491-9-1.aspx

Have a nice day
Post #1490482
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse