FIX: RPC Returns Error 7222 When Re-executed After Canceled RPC

• Microsoft SQL Server version 6.5

SYMPTOMS

After canceling a remote procedure call (RPC), re-execution of the same RPC from the same connection returns the following message:

Error 7222 "Received bad token 0x%x from site '%.*s'"

CAUSE

Canceling an RPC on a primary site does not cancel the connection on the remote site.

WORKAROUND

To work around this problem, do either of the following:

• Do not cancel the RPC.
  
  -or-



• After the RPC cancellation, issue subsequent calls to the same RPC from another spid. Note that this workaround may not work if the original RPC is holding blocking locks.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

MORE INFORMATION

After canceling the RPC, sp_who on the remote site shows an associated unkillable spid. Clearing the connection on the primary site will also clear the spid on the remote site.

Configuration values 'remote conn timeout' and 'remote query timeout' have no effect.

Additional query words: sp sp5cancelled cancelling connect time out

Keywords          : SSrvGen kbbug6.50 kbfix6.50.SP5 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: April 4, 1999