FIX: ODBC Clients Show as Sleeping but Command Is EXECUTE (164442)
The information in this article applies to:
This article was previously published under Q164442
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).
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbBug kbfix kbProgramming kbusage KB164442 |
|---|
|