ODBC Connection to a Instance | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

ODBC Connection to a Instance

I’m running two instance (Microsoft SQL Server 2000 – 8.00.81<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> and one default, I can connect to any of the three via of EM Or Query Analyzer. My Client lib is using Name Pipe & TCP/IP and the default is using port 1433 where as the two instance port are using "0". I would like to know why when I test my ODBC connection to one of the instance it fails (thats when using TCP/IP) but when using Name Pipe its ok. I have also assign a port number to the two instance as well as set it dynamically but yet the ODBC connection still fail, and ideals (help).
What is the error message indicating failure to connect? Security? Server Location? Timeout? Nathan H.Omukwenyi

Ensure TCP/IP is enabled on both the instance by taking server network utility help. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Connection failed:
SQLState: ‘01000’
SQL Server Error: 10061
[Microsoft] ODBC SQL Server Driver][TCP/IP Sockets] Connection Open(Connect())
Connection failed:
SQLState: ‘9001’
SQL Server Error 17
Microsoft ODBC SQL Server Driver [TCP/IP Sockets] SQL Server does not exists or access denied.
Nothing to do with client-side libraries, ODBC drivers or OLEDB if Enterprise Manager and Query Analyzer are working fine. Just chek your ODBC connection settings 1. The server instance name
2. The security type [Windows or Mixed Authentication] vis a vis the currently logged on user.
3. Username/Password combination.
Nathan H.Omukwenyi

Check this KBAhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 and findout the root cause to the error. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>