FIX: SELECTs from SYSPROCESSES Result in Access Violation

Last reviewed: April 8, 1997
Article ID: Q151985

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

SYMPTOMS

On busy symmetric multiprocessing (SMP) computers, queries against the virtual table sysprocesses may infrequently get a handled access violation, causing the client connection to be terminated. Other clients are unaffected. The call stack of the access violation will look similar to the following:

findwaitfor+0x2f ins_sysproc+0x7fc make_fake+0xe8 s_setuptables+0x2bc s_execute+0x7d8 sequencer+0x23f execproc+0xfb7 s_execute+0xb8c sequencer+0x23f language_exec+0x65e

STATUS

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

Additional query words: SQL6 SQL65 SP_WHO
Keywords : kbbug6.00 kbfix6.50.sp1 kbnetwork SSrvGen SSrvTrans
Version : 6.0 6.5
Platform : WINDOWS

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