FIX: ODBC Clients Show as Sleeping but Command Is EXECUTE

Last reviewed: June 27, 1997
Article ID: Q164442

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 16453 (6.5)

SYMPTOMS

When an ODBC client runs a stored procedure, and after the execution is complete, the Current Activity in SQL Enterprise Manager or the results of a sp_who query may show that the process' (spid) status is sleeping, but the command is EXECUTE instead of AWAITING COMMAND.

WORKAROUND

If the process is not blocked by another process, the query has been completed, and you can ignore the EXECUTE command.

STATUS

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

MORE INFORMATION

This problem may also occur with DB-Library clients that use the stored procedure API calls (those with RPC in the function name).

Additional query words: sqlrpc dbrpc
Keywords : kbbug6.50 kbprg kbusage SSrvDB_Lib SSrvEntMan SSrvProg SSrvStProc kbfixlist
Technology : ODBC
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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