We help IT Professionals succeed at work.

ODBC 3151 Errors

Briff
Briff asked
on
Medium Priority
838 Views
Last Modified: 2011-10-03
My clients are getting ODBC 3151 Errors and fail to connect to my SQL 6.5 database on a large network how can I improve the connectivity so that it connects first time round?

I have also have noticed that I get a couple of error mesages on the server whos' time stamps apear to co-incide
with the 3151 message they are :-

ods error 17832 severity 18 state 0
ods error unable to read login packets
Comment
Watch Question

Commented:
Is there an error message text returned by ODBC driver? Sorry, but I can't find error code 3151.
Anyway check that your client is using the network protocol you are supporting on the server (Named Pipes, Multi-protocol, IPX/SPX, TCP/IP). Which conection are you using - trusted, standard security or mixed. Your client must use one supported by your server. It is configurable with ODBC driver.

Commented:
3151 is not an ODBC error message/number I believe you are using MS Visual Basic for your client application.  If you are, that number is a connectivity issue with the datasource you are connecting to.  If the datasource is an Access DB then make sure the users have rights to the area where the MDB is connected to.

Commented:
3151 is not an ODBC error message/number I believe you are using MS Visual Basic for your client application.  If you are, that number is a connectivity issue with the datasource you are connecting to.  If the datasource is an Access DB then make sure the users have rights to the area where the MDB is connected to.

Author

Commented:
Edited text of question
Commented:
I have experienced the '17832' error many times while using Named Pipes. SQL Server has only one default pipe that it listens on for client requests. Requests get queued and often times the connection times out, resulting in the '17832' error. I have increased the number of pipes available to SQL, thus balancing the load and reducing the chance for timeout errors. Also, you might try connecting via TCP and/or increasing the Application logon timeout value. See MS Knowledge Base Article # Q165189 for details.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.