RPC Encoding API "MesInqProcEncodingId" Not Work for a Decoding Handle

This article was previously published under Q165664
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
The "MesInqProcEncodingId" application programming interface (API), that issupposed to return the interface ID and the procedural number used inprocedural encoding of a remote procedure call (RPC) interface method to auser specified buffer, always seems to return an interface ID of 00000000-0000- 0000-0000-000000000000} and procedural number of 0 when called with adecoding handle before decoding the buffer. This happens for both fixedstyle and procedural encoding/decoding.
CAUSE
The MesInqProcEncodingId API is not functioning properly.
RESOLUTION
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
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.
Properties

Article ID: 165664 - Last Review: 10/06/2013 23:21:36 - Revision: 2.2

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbapi kbbug kbfix kbnetwork kbqfe kbrpc KB165664
Feedback