Unable to read in login record.

Unable to read in login record.

Post by Tony Langd » Thu, 13 Oct 1994 17:43:44



Has anyone seen the following error in the errorlog:
server: Unable to read in login record.

This was an isolated error, i.e no other errors in the log at the same
time.

Does anyone know what causes it, and is it anything to be worried about?

BTW :
 SQL Server/4.9.2/EBF 2417/Sun4/OS 4.1.2/1/OPT/Tue Jan 11 07:06:49 PST 1994

---

 Goldman Sachs International Limited   | Phone : +44 71 774 5420
 Peterborough Court, 133 Fleet Street, |
 London. EC4B 2AA                      | ... and the Reds go marching on, on, on ...

 
 
 

1. unable to read login packet!

Did anyone find a fix to the above?  I just finished installing 6.0 on a
new server, under NT 3.51, and it kept accumulating the same message
over and over on the Event Log.  The SP3, did not seem to work, and will
try the SP5 of NT.  My network is Banyan.

Thanks a much!
Bud

2. Monitoring

3. Error: 17832 Unable to read login packet(s)

4. How relevant is the underlysing OS?

5. Error 17832 - Unable to read login packets(s).

6. trace profiler

7. ERROR 17832 Unable to read login packets

8. Drop & Recreate table problems

9. Error: 17832 Sev: 18 State: 0 Unable to read login packet(s)

10. Error: Unable to Read login Packet(s)

11. Error 17832 unable to read login packets

12. Unable To Read Login Packet(s)

13. Event Log shows Unable to read login packets