RPC Encoding API "MesInqProcEncodingId" Not Work for a Decoding Handle (165664)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q165664 SYMPTOMS
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.
CAUSE
The MesInqProcEncodingId API is not functioning properly.
RESOLUTIONTo 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
STATUSMicrosoft 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.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbAPI kbbug kbfix kbnetwork kbQFE kbRPC KB165664 |
|---|
|