Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kpm
Starting Member
2 Posts |
 Posted - 2002-12-06 : 11:35:02
|
| The actual full error log message is:-2002/12/02 07:47:15.78 ods Error:17832,Severity:18, State:0 Unable to read login packet(s).Is there anyone who has come across this before and I mean the Error message been logged every minute for the past 6 days. This isn't only creating large error logs but, I think it could be contributing to performance issues.If anyone can help |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-12-06 : 12:59:08
|
| Well I typed up a response to this, but I guess it didn't get posted.Are you seeing this on SQL Server 6.5 or 7.0? I have mostly seen this on 6.5. I have never seen this on 2000.It is my understanding that this error means that a user has disconnected abruptly meaning the user didn't disconnect on purpose. It is also my understanding that this is a network problem. I strongly believe that this is not causing ANY performance problems. If you believe that this error is causing problems, you should have your network administrator put a network sniffer on the subnet where the database server resides. The sniffer should be able to tell you what the problem is. If it doesn't, you will have to move the sniffer to the subnet where a particular user, that is affected by this problem, resides. |
 |
|
|
kpm
Starting Member
2 Posts |
Posted - 2002-12-09 : 06:28:06
|
| Thanks for the reply.This is on SQL Server 6.5, we are hoping to upgrade to 2000 next year.I thought that a network sniffer could be an option from the articles that I have read on the Microsoft site. Thanks for confirming this.Cheerskpm |
|
|
|
|
|
|
Error 17832 Unable to read login packets