A Windows 2000 Client May Display "RPC_S_INVALID_TAG" When Connecting to UNIX Systems (316406)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q316406 SYMPTOMS
RPC-based programs that run on a Windows 2000-based client may not work when the client connects to UNIX servers (such as SUN or Hewlett-Packard).
CAUSE
When you use structures as parameters in RPC calls on Windows 2000, the call may not work and may generate "RPC_S_INVALID_TAG (1733)" or "RPC_X_BAD_STUB_DATA (1783)" errors.
The problem occurs on a Windows 2000-based client that is attempting to communicate with a server platform that uses a different byte ordering. SUN and Hewlett-Packard use big-endian, DEC (like Windows) uses little-endian.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
------------------------------------------------------
05-Feb-2002 17:32 5.0.2195.4735 940,816 Ole32.dll
05-Feb-2002 17:32 5.0.2195.4909 428,304 Rpcrt4.dll
05-Feb-2002 17:32 5.0.2195.4840 186,128 Rpcss.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB316406 |
---|
|