BUG: Problem Using Xp_readerrorlog When Reading Large Errorlog

 Last reviewed: January 21, 1998
Article ID: Q157804
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15167

SYMPTOMS

When you use the SQL Enterprise Manager (SEM) 'Server - Error log' or run xp_readerrorlog with a large errorlog, you may find that it takes a long time to run. If the user closes SEM or ISQL/w before xp_readerrorlog finishes returning results, you may find the following messages repeated in the SQL Server errorlog and application event log: 

   ods      Error : 17824, Severity: 10, State: 0
   ods      Unable to write to ListenOn connection '\\.\pipe\sql\query',
   loginname 'sa', hostname 'BP71092'.
   ods      OS Error : 232, The pipe is being closed.
The size of the errorlog may grow 20K or more every second, and the server will be very slow. The problem will stop after 15 to 20 minutes, and everything will return to normal. However, during this 15 to 20 minute window, the errorlog may grow to 30 MB, and any operation on the server will be extremely slow.

WORKAROUND

To work around this problem, use Notepad, Write, or another text editor to view the SQL Server errorlog.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug6.00 kbbug6.50 SSrvEntMan SSrvErr_Log kbusage
Version : 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 21, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.