Article ID: 165664 - View products that this article applies to.
This article was previously published under Q165664
This article has been archived. It is offered "as is" and will no longer be updated.
The "MesInqProcEncodingId" application programming interface (API), that is supposed to return the interface ID and the procedural number used in procedural encoding of a remote procedure call (RPC) interface method to a user specified buffer, always seems to return an interface ID of 00000000- 0000- 0000-0000-000000000000} and procedural number of 0 when called with a decoding handle before decoding the buffer. This happens for both fixed style and procedural encoding/decoding.
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.
Article ID: 165664 - Last Review: October 6, 2013 - Revision: 2.2
Contact us for more help
Connect with Answer Desk for expert help.