For some reason agents started to log errors and when using MFCMAPI it also fails with errors.
It is possible that the MAPI CDO got “corrupted”, often this happens when MAPI CDO was not installed “correctly”.
Re-install the MAPI CDO
To install or re-install the MAPI CDO download ExchangeMapiCdo.EXE from elsewhere in the KB as the download is not available from Microsoft anymore.
Uninstall the Microsoft Exchange System Manager or the Messaging API and Collaboration Data Objects 1.2.1 using the Control Panel (Add or Remove Programs)
Note: If the uninstall didn’t work as expected then it is a good idea to use the Program Install and Uninstall troubleshooter offered by Microsoft.
This program replaces the old Windows Installer Cleanup utility (MSICUU2.exe) and can be downloaded from here:
http://support.microsoft.com/kb/2438651
When done locate the following files and if they are present rename them by adding the extension .old.
When searching for them make sure that “Search system folders” and “Search hidden files and folders” is selected under “More advanced options”:
EMSMDB32.DLL, EMSABP32.DLL, CDO.DLL
After this has been done reboot the host.
When logging in use the service account used by the agent and ensure this account has local admin rights granted explicitly, not via group membership.
Find the downloaded ExchangeMapiCdo.EXE file, double-click the file to extract the ExchangeMapiCdo.MSI file.
Then double-click the ExchangeMapiCdo.MSI file and install the Microsoft Exchange Server MAPI Client and CDO version 1.2.1.
Important! If UAC (User Account Control) is enabled on the agent host machine then the installation of the MAPI CDO should be run as an administrator.
This option might be not available if you right-click ExchangeMapiCdo.MSI., as workaround use the following steps:
Start - All Programs- Accessories, right click on Command prompt and select Run as administrator.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
Provide the path to the location with ExchangeMapiCdo.MSI, type ExchangeMapiCdo.MSI (or drag and drop the ExchangeMapiCdo.MSI to the cmd windows) and press Enter.
Follow the installation wizard and install the MAPI CDO.
After this has been done it is safe to start the Quest agents using the QMm Exch GUI. Do not attempt to start the services, they will be started by the tool, when the agent is started using the GUI.
In some cases the MAPI Stub library can be broken by Group Policy or applications that change the Stub registry settings.
Eg. one customer had a customized group policy that changed the default mail client to Lotus Notes:
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail
When you install the Exchange MAPICDO the value is "ExchangeMAPI".
When this policy was applied the value is "Lotus Notes".
This change prevented QMM agents and MCFMAPI from logging on to Exchange.
http://blogs.msdn.com/b/stephen_griffinwaarchive/2008/06/04/how-to-break-the-mapi-stub-library.aspx states "...there's no way to tell the stub that there are two MAPI implementations your application can work with and just use whichever one is available."
In the example above it would be an either/or that was flipped by the Group Policy and CDO reinstalls.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center