FIX: DBCC SQLPERF(THREADS) Fails w/ AV on 6.0 SP 1

 Last reviewed: May 1, 1997
Article ID: Q138013

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

SYMPTOMS

The command DBCC SQLPERF(THREADS) on SQL Server version 6.0 Service Pack 1 fails with the error: 

   DBCC function 'threads' in the library 'sqlper60' generated access
   violation; SQL Server is terminating process <n>
The client connection that executed this command is terminated, but other client connections are unaffected. The client may see the access violation error listed above, or encounter DB-Library errors 10037, "Unexpected EOF from SQL Server," or 10008, "Bad Token from SQL Server: Datastream processing out of synchronization."

This problem does not exist in SQL Server 6.0 without Service Pack 1 applied.

WORKAROUND

Most of the information from SQLPERF(THREADS) can be found using a combination of other resources such as SQL Enterprise Manager (Current Activity), sp_who, examining the sysprocesses table, and Windows NT Performance Monitor.

For additional information about SQL Server Windows NT threads, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q117559
   TITLE     : INF: How to Correlate Spid, Kpid, and Thread Instance

STATUS

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

Additional query words: sql6 windows nt SP1 sqlper60.dll
Keywords : kbbug6.00.sp1 kbfix6.00.sp2 kbprg SSrvProg SSrvTran_SQL
Version : 6.0.sp1
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 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.