FIX: RpcTestCancel() Always Returns Error Code 5

Article translations Article translations
Article ID: 192127 - View products that this article applies to.
This article was previously published under Q192127
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


Your RPC server manager routine makes a RpcTestCancel() call to test if the current RPC call has been cancelled by the remote RPC client. However, this call always returns error code 5.


To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack


Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.


Under Windows NT version 4.0 Service Pack 3 and previous Service Packs, when an RPC client issues a cancel then the client is unblocked. However, the server never notices the cancel. If the client is using an infinite timeout, the client does not unblock unless the server finishes or fails the call.

On Windows NT version 4.0, you need to do the following to cancel an RPC remote call:

  1. Use connection-oriented protocols, such as ncacn_ip_tcp, for communication between your RPC client and server.
  2. In the client-side main thread start another call thread to make the actual RPC call. For example: CallThread = (void *) _beginthreadex(...);
  3. The call thread issues RpcMgmtSetCancelTimeout(0), where 0 indicates that you do not want to wait for the RPC server to acknowledge the cancel (the call is immediately abandoned upon a cancel). Next, your call thread makes the actual RPC call.
  4. In the main thread, you can either call Sleep() to sleep for sometime or wait until the timeout expired and issue RpcCancelThread() to cancel the call if it timeouts. For example: rc = WaitForSingleObject(CallThread, 5000); if (WAIT_TIMEOUT == rc) { status = RpcCancelThread(CallThread); . . .
  5. In your RPC server-side manager routine, you need to test if the current RPC call has been cancelled by calling RpcTestCancel(). However, RpcTestCancel() always returns error code 5, even if the cancel packet has been received by the RPC server runtime.


Article ID: 192127 - Last Review: October 10, 2013 - Revision: 4.0
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
kbnosurvey kbarchive kbbug kbfix kbrpc kbnetwork KB192127

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from