PRB: Load Library Failed Error Registering Active Messaging

Last reviewed: November 21, 1997
Article ID: Q173852
The information in this article applies to:
  • Collaboration Data Objects (CDO), version 1.1

SYMPTOMS

You may receive the following error when trying to run REGSVR32 against Olemsg32.dll:

   Load Library Failed.  Get Last Error = 0x0000001F

CAUSE

Your MAPI DLLs may be too outdated to allow the Active Messaging Library to be registered. It includes the MAPI DLLs that shipped with the initial release of Microsoft Exchange 4.0.

RESOLUTION

Update your MAPI DLLs to the versions released with Microsoft Exchange 4.0 (or later). This can be done by one of the following methods:

  • Install the DLLs from the Exchange 4.0 Server release rather than the original Exchange 4.0 client released with Windows 95.
  • Install any version of Exchange greater than 4.0.
  • Download Exupdusa.exe from: ftp://ftp.microsoft.com/Softlib/MSLFILES/. NOTE: This is effectively an Exchange 4.0 Service Pack. First make a complete backup, then run the update.

STATUS

This behavior is by design.

MORE INFORMATION

If this was the cause of the error, once the underlying MAPI DLLs are updated, REGSVR32 should be able to successfully register Olemsg32.dll.

REFERENCES

For additional information about Collaboration Data Objects versus Active Messaging, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q176916
   TITLE     : INFO: Active Messaging and Collaboration Data Objects (CDO)

Keywords          : kberrmsg ActMsg
Version           : WINDOWS:1.1
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 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.