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.
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:
(http://support.microsoft.com/kb/152734/EN-US/ )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:
Article ID: 192127 - Last Review: October 10, 2013 - Revision: 4.0