| Event Id | 17832 |
| Source | ODS Error |
| Description | Unable to read login packets Error 17832, Severity 18. |
| Event Information | Under certain situations, Microsoft SQL Server may log the following error either in its
error log or in the Windows NT event log: 17832 Unable to read login packet(s). This error occurs if a client starts to connect but never successfully completes the attempt because of a client operating system, application, or network failure. However, the very occurrence of these errors in the errorlog or event log does not necessarily indicate any real problems with your SQL Server connectivity. Even in normal operations, this error may still occur at times, due to the unreliable nature of networks, especially wide area networks. In addition, improper use of applications (such as restarting the computer in the middle of a login process) can also cause this error to occur. To determine whether or not you are facing a real problem, you may want to check the following: Check with the end users to see whether they have experienced any difficulties in making connections to SQL Server. If nobody reports any connectivity problems, you can usually ignore these errors. Check the frequency of this error in the error log. If it occurs very frequently, it indicates some potential problems, even if no one is complaining about any connectivity problems. If you have determined that you have a real problem, you may want to apply the additional troubleshooting methods |
| Reference Links | INF: How to Troubleshoot SQL Server Communication Error 17832 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.