FIX: Incorrect Display of Error Log in Enterprise Manager (308834)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q308834
BUG #: 354811 (SHILOH_BUGS)
BUG #: 101900 (SQLBUG_70)
SYMPTOMS
SQL Enterprise Manager (SEM) incorrectly parses and displays SQL Server error logs that contain short stack dumps. SQL Server sorts the error log by date and SEM incorrectly interprets the date field for short stack dump lines; therefore, SEM sorts the error log incorrectly.
CAUSE
Short stack dump lines do not contain information that SQL Server can identify as date or source. However, SQL Enterprise Manager parses short stack dump lines as if they have the columns Date and Source, which results in the display of an error log that is very confusing to read and incorrectly sorted.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
To work around this problem, use a text editor to view the error log files that contain short stack dumps.
STATUSMicrosoft has confirmed that this is a problem in Microsoft SQL Server 7.0.
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.MORE INFORMATION
To correct this problem SQL Server 2000 Service Pack 2 formalizes the format for the short stack dump lines in the SQL Server error log files, by preceding the lines in a short stack dump with an asterisk character (*). The SQL Server 2000 Enterprise Manager ignores lines that start with an asterisk and thus, it does not parse or sort lines from a short stack dump.
Modification Type: | Major | Last Reviewed: | 10/28/2003 |
---|
Keywords: | kbbug kbfix KB308834 |
---|
|