Solved

ODBC 3151 Errors

Posted on 1997-07-30
5
809 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
0
Comment
Question by:Briff
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 2

Expert Comment

by:armands
ID: 1088836
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.

0
 

Expert Comment

by:kcatten
ID: 1088837
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.
0
 

Expert Comment

by:kcatten
ID: 1088838
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.
0
 

Author Comment

by:Briff
ID: 1088839
Edited text of question
0
 

Accepted Solution

by:
sorokar earned 50 total points
ID: 1088840
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.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question