ODBC 3151 Errors

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
BriffAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

armandsCommented:
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
kcattenCommented:
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
kcattenCommented:
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
BriffAuthor Commented:
Edited text of question
0
sorokarCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.