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

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

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

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.

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:For more information, contact your primary support provider.

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.