PRB: Executing .Fetch of the VB5 MSMAPI32.OCX Can Hang VB5

 Last reviewed: November 7, 1997
Article ID: Q176338
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

An application using the MSMAPI32.OCX MAPIMessages Control (version 5.00.3721) may hang when the .Fetch method of the control is called.

CAUSE

The messaging subsystem of your Operating System may be too outdated to use this control successfully.

The most common occurrence of this problem is where the customer has installed the Exchange 4 client from the original release media of Windows 95.

RESOLUTION

To resolve the problem, you can install the Windows Messaging System (WMS).

If the problem is on Windows 95, WMS can be installed from ftp://ftp.microsoft.com/Softlib/MSLFILES. The target file is called EXUPDUSA.EXE. This will update the messaging subsystem (MAPI DLL files) on the problematic system.

If the problem is on another platform, you can obtain the appropriate WMS from ftp://ftp.microsoft.com/developr/MAPI/WMS_RDST. The README.TXT file in that directory provides information on what file to download for operating system as well as installation instructions.

STATUS

This behavior is by design.

MORE INFORMATION

This article is not applicable if the problematic system has (or previously had) any version of Outlook or the Exchange client version 5 or higher installed. 

Keywords          : vb5all
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbprb

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

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