PRB: INVALID_HEADER or Other Error from COM on MSCS

 Last reviewed: January 23, 1998
Article ID: Q179474
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK)
  • Microsoft Windows NT Server Enterprise Edition version 4.0

SYMPTOMS

When you install a Component Object Model (COM) server for use within a Microsoft Cluster Server (MSCS) group, COM communication can fail. This problem occurs when both an application and the COM server are running on the same cluster node. In this situation, COM generates an error such as the following when the application attempts to call the COM server: 

   OLE received a packet with an invalid header. (80010111)

CAUSE

Currently, an application cannot connect to a COM server on the same machine using anything other than the network basic input/output system (NetBIOS) name of the local host.

RESOLUTION

You can work around this problem by placing both the COM server and the requesting application in the same MSCS group and writing the client to assume the COM server is on the local host.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 

Keywords          : kbcluster
Version           : win95; WINNT:4.0
Platform          : Win95 winnt
Issue type        : kbprb
Solution Type     : kbpending

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 23, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.