Solved

SQL Error: Unable to read login packet (s)

Posted on 1998-03-31
11
542 Views
Last Modified: 2010-05-18
Our NT 3.51 server is reporting very frequently the following SQL error:

Error:17832, Severity:18, State:0. Unable to read login packet (s).  

I checked what the "Handling Error Messages" manual advices1 and everything is OK, but unfortunately the Event Viewer continues receiving too many of this errors every day. Do you  know any other reasons that  could cause this error on the server?  What else do you advice me to do?

My SQL Version is 4.21



1. Advice in "Handling Error Messages": Verify that all clients connecting to the affected SQL Server are using the latest version of the SQL Server clients components, including the Net-Libraries, DB-Library, and/or ODBC drivers.      
0
Comment
Question by:gpolanco
  • 6
  • 4
11 Comments
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090940
Hi,
We have the same problem... I'm VERY interested in where this thread ends up. We get around 1,500-2,000 (roughly) of these a day and I've tried everything short of getting rid of every protocol except TCP/IP (the network guys wont let me), but I've read/heard that this might fix the problem (as long as you are running the latest library versions).
Do you use IPX,TCP and NetBieu (we do)?

(Know this didn't help, but hey... just wanted to let you know you're not alone...)
Jim

0
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090941
Hi again,
Another thing that 'might' cause this is if packets are broken up by your routers (we fixed this but still got the messages).
Jim
0
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090942
We're using NT 3.51 & NT 4.0 with SQL 6.5 (latest SPs for all) ... so versions aren't the problem...
Jim

0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:gpolanco
ID: 1090943
Hi Jim_SQL,
Thanks for your comments, I really appreciate them. It is very rewarding to know that I'm not alone.

About your question we only use NetBieu. As you, we are using NT 3.51 & NT 4.0 with SQL 6.0, but we ONLY have this error in the server (just one) where we have NT 3.51 with SQL 4.21. Do your network's clients hangs frecuently while trying to connect to the SQL-server wich is reporting the error? My clients do.

Please let me know any news about this error.


Glenys.


0
 

Author Comment

by:gpolanco
ID: 1090944
Adjusted points to 150
0
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090945
Hi,
We, the only machines that receive this error for us are 2 NT 4.0 machines running SQL 6.5. The error seems to only happen when we use Win3.11 machines accessing the SQL servers through TCP/IP. It doesn't appear that other machines have a problem. As far as the 'hanging' goes... if we use rdo they do sometimes. I think there is nothing we can do regarding that though since with the 5(?) layers for TCP/IP if the bottom layers get confused it will hang your computer (Win95 and Enterprise manager hang on big queries too). We're in the process of converting everything to use the VB SQL dll, since it seems to offer the fastest connections and the least amount of hanging, but it still does hang, just less often.
Jim

0
 

Accepted Solution

by:
ZakB earned 150 total points
ID: 1090946
If you are receiving MANY of the these errors, it is probably due to a problem on the client side.  Slow networks and routers that cannot send large packets can also cause this problem.
Some things to look at:

1 - Using a 32 bit ODBC driver for a 16 bit application under Windows 95.  The errors will continue until the application terminates.

2 - The client machine may not have suffient resources to make the connection.

3 - Some anti-virus software programs may cause this problem if they are configured to scan ALL files.

2 -
0
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090947
Hi,
Strange... we both have this problem on different versions of NT AND different versions of SQL on those NTs, and yet we can specifically say that the problem only occurs on specific NTs at our sites? (Definitely sounds like a network thing... ie network cards, routers, cables, NT settings... but I'm still not sure what it is).
Jim
0
 
LVL 2

Expert Comment

by:Jim_SQL
ID: 1090948
Hi,
If someone can come up with an answer that fixes both gpalonco's and my problem (both) I'll post a question worth an additional 300 points (and only accept your answer so you get the points).
Jim

0
 

Author Comment

by:gpolanco
ID: 1090949
Hi ZakB,

I’m evaluating your suggestions and seems like if one of them is working. Anyway I want to be sure. As soon as I have conclusions I will let you know and I will grade your answer.

Bye, Glenys.

0
 

Author Comment

by:gpolanco
ID: 1090950
Hi ZakB and Jim_SQL, my problem was solved by removing our  antivirus application (Cheyenne) from the clients with WIN.311. I had updated this application just around the days that the server started to reporte the SQL-error. Thanks (both of you) for all your help; I really appreciate it.


Bye, GLenys.

0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

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

Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

803 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