The ordinal 23 could not be located in the dynamic link library MAPI32.dll

Posted: 9/4/2009, Updated: 7/11/2010

Overview

When Identity Finder is launched or a search is initiated, an attempt is made to load specific Windows components (e.g., MAPI32.dll) that allow the searching of e-mail messages and attachments.  If these Windows components become outdated, corrupted, or are replaced by another application, an error may be displayed and Identity Finder will be unable to continue.

Detail

The file MAPI32.dll is a Windows operating system file and is included on every Windows system.  This file is used by e-mail applications and is required for Identity Finder to function as it contains the Windows messaging interface that allows Identity Finder to search, for example, Outlook and Outlook Express messages and attachments.

Any change to this file or its configuration can cause any of the following errors to be displayed by Identity Finder.

• The ordinal 30 could not be located in the dynamic link library MAPI32.dll
• The ordinal 23 could not be located in the dynamic link library MAPI32.dll
• Unable To Find MAPI32.dll

Resolution

To resolve this issue, please perform steps 1-3, in order, and stop when the error is no longer displayed.  If Eudora is installed on the system (even if it is not in use), it may be possible to directly skip to step 4; however, it is recommend that all of the steps are followed in order.

1. Microsoft is aware that this file can become corrupted and provides a utility with every copy of Windows named, "fixmapi".  To run fixmapi, click Start->Run and type "fixmapi" (without the quotes) and click OK.  There is no visual indication that it ran or that it did anything and it has no user interaction.  After clicking OK, wait 30 seconds and then reboot the computer.  After restart, launch Identity Finder to confirm that the issue has been resolved.  If the issue persists, continue to step 2.
2. Ensure that all of the latest operating system updates and patches are installed on the system, especially the latest Windows Service Pack.  Use Windows Update to install all of the updates (this may take some time and require several reboots).  Once all of the outstanding updates have been successfully installed, reboot the system again.  After restart, launch Identity Finder to confirm that the issue has been resolved.  If the issue persists, continue to step 3.
3. Even if the applications are not being used, launch Outlook Express or Windows Mail (also included with each copy of Windows) to attempt to initialize the MAPI interface by clicking Start->Run and typing "msimn" without the quotes.  If the Windows e-mail application does not run, this is indicative of  another problem with the operating system that must be resolved before Identity Finder will function.  If the application opens successfully, launch Identity Finder to confirm that the issue has been resolved.  Launch Identity Finder with the e-mail application open and with it closed.  If the issue persists, it is recommended that the original operating system installation CD be used to repair Windows.  Because the issue exists outside of Identity Finder, no further assistance is available from our support team.
4. If Eudora is installed on the system, even if it is not in use, it may have replaced the Windows version of MAPI32.dll with a version incompatible with Identity Finder.  Open Eudora and determine if it is set to use its MAPI server, "Always".  If so, switch the value to "Only When Eudora Is Running" and then reboot the computer.  After restart, launch Identity Finder to confirm that the issue has been resolved.  If the issue persists, follow steps 1-3 above.