XCLN: Using OLE Messaging to View Non-Replicated PF Fails

 Last reviewed: April 15, 1997
Article ID: Q157018
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, version 4.0
  • Microsoft Exchange Windows NT client, version 4.0
  • Microsoft Exchange Windows 95 client, version 4.0

SYMPTOMS

When you use OLE messaging to view a non-replicated Public Folder in the Public Folder hierarchy the following error might appear on Win32: 

   Run-time error -2147417851 (80010105) OLE Automation Error The server
   threw an exception.
This error can be trapped and avoided.

On Win16, you might see: 

   MDSIP - An error has occurred in your application. If you choose Ignore,
   you should save your work in a new file. If you choose Close, your
   application will terminate.
If you click Ignore, you will see the following: 

   Application error. MDISP caused a GPF in module MDISP.EXE at 0002:093F.
If you click Close, you will see: 

   Run time error '-2147418105 (80010007' OLE Automation error.
You can click OK and the application will terminate.

If you click Close after the initial error, the following error will be displayed: 

   Application error. MDISP cause a GPF in module MDISP.EXE at 0002:08E6.
and then the application will terminate. This cannot be trapped.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: OleMsg
Keywords : kbbug4.00 kbfix4.00.sp3 kbusage XCLN
Version : 4.0
Platform : WINDOWS

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: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.