FIX: Problem Using Xp_readerrorlog When Reading Large Errorlog

ID: Q157804

The information in this article applies to:
BUG #: 15167 (SQLBUG_65)

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 version 6.0.

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.


MORE INFORMATION

Additional query words: 


Keywords          : kbusage SSrvEntMan SSrvErr_Log kbbug6.50 kbfix6.50.SP5 kbbug6.00 
Version           : winnt:6.0,6.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: April 21, 1999