Microsoft KB Archive/157804

= FIX: Problem Using Xp_readerrorlog When Reading Large Error Log =

Article ID: 157804

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition
 * Microsoft SQL Server 6.0 Standard Edition

-



This article was previously published under Q157804



BUG #: 15167 (SQLBUG_65)



SYMPTOMS
When you use the SQL Enterprise Manager (SEM) 'Server - Error log' or run xp_readerrorlog with a large error log, 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 error log 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 error log 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 error log 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 error log.



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 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.



MORE INFORMATION
Keywords: kbbug kbfix kbusage KB157804

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.