FIX: SEM Generates Handled Exception Reading the Errorlog

 Last reviewed: May 2, 1997
Article ID: Q141975

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11402 (6.00)

SYMPTOMS

SQL Enterprise Manager (SEM) can generate the following handled exception upon reading the errorlog: 

   Error : 0, Severity: 19, State: 0
   Stored function 'xp_readerrorlog' in the library 'xpstar.dll' generated
   access violation; SQL Server is terminating process <process id>
This can cause SQL Enterprise Manager to hang to the point that the process must be killed.

CAUSE

SQL Enterprise Manager uses the extended stored procedure xp_readerrorlog to read the current errorlog. If the errorlog contains two or more contiguous line-feed characters, xp_readerrorlog will generate the access violation when it attempts to read it.

WORKAROUND

This situation is rare, but if you run into this scenario do not use SQL Enterprise Manager or xp_readerrorlog to read the errorlog in question. Try using another utility such as Write or Notepad.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: sql6 AV
Keywords : kbbug6.00 kbfix6.00.sp3 kbtool SSrvEntMan SSrvErr_Log
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.