ODBC ERROR

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hello,

One of the client system in my office is not connecting to the server when i want to creat the Data Scource from ODBC it gives the error below

' Connection Failed

SQLState:'08001'

Sql Server Error:1265

(Microsoft)(SQL Server Native Client10.0)Named Pipe Provider:Could not open connection to SQL Server(1265)

Connetion Failed:

SQL state:HYT00

SQL Server Error:0

(Microsoft)(SQL Server Native Client10.0)Login Timeout Expired'

Note: The password i used is correct am very sure. Also the server i selected is also correct but idont know why i am still having the error.

I will be glad if you can help me out.

Thank you

*This post is locked for comments

All responses (8)

Answers (0)

TD2012 935 on at

Like (0)

Report

RE: ODBC ERROR

Yes, I checked that, thank you for responding.
KirkLivermont 5,985 on at

Like (0)

Report

RE: ODBC ERROR

It is worth double checking that you are using the 32bit ODBC connection.

Kirk
TD2012 935 on at

Like (0)

Report

RE: ODBC ERROR

I'm having this same issue. The employee was able to log in then suddenly cannot. Their IT people assure me nothing has changed and that she has all the same rights as everyone else. The ODBC works when logged in as another user. I know this is several years old but I wonder what you did to correct it?
Community Member Microsoft Employee on at

Like (0)

Report

Re: ODBC ERROR

@Jeganeedhi and Richard Thanks so much i was able to resolve it.

God bless you
Richard Whaley 25,195 on at

Like (0)

Report

Re: ODBC ERROR

Simple question but thre MOST COMMON issue in this situation....is the user properly logged in to the network with rights to the desired server?

Try logging on to the workstation with someone elses network logon.
Jeganeedhi Krishnan 2,500 on at

Like (0)

Report

Re: ODBC ERROR

Hi,

Cause 1:

The client is attempting to connect using named pipes, and the server is not configured to allow remote connections using named pipes.

Resolution

Connect using TCP/IP, or use the SQL Server Configuration Manager to enable remote connections using named pipes.

Cause 2:

The client protocol order is attempting to connect with the named pipes protocol before trying the TCP protocol, and named pipes are not enabled on the server.

Resolution

Using SQL Server Configuration Manager on the client computer, move TCP before named pipes in the protocol order list.

Thanks
Community Member Microsoft Employee on at

Like (0)

Report

Re: ODBC ERROR

Hello,

Thanks for your reply.

The SQL browser is not off and the TCP/IP is enabled. i also put off the firewall but still the same thing. Now the error am getting is

'Connection Failed

SQLState:'08501'

Sql Server Error:233

(Microsoft)(SQL

Server Native Client10.0)Named Pipe Provider:no process is on the other end of the pipe

communication link failed'

i will be greatful for your quick responce.

Thank you
Jeganeedhi Krishnan 2,500 on at

Like (0)

Report

Re: ODBC ERROR

hi,

Can you able to connect the server using SQL client?

If it is not connecting then problem with SQL .

1.SQL Browser may be off

2.TCP/IP is not enabled

3.Check with Firewall settings

Thanks

Jeganeedhi