Please Verify the following requirements are met:
1. On the MessageStats server ensure there is only one MAPI Provider installed
- For Exchange 2003 and earlier the latest version of MAPI CDO can be used as the MAPI Provider or ESM 2003
- For Exchange 2007 and later only MAPI CDO is supported as the MAPI Provider for MessageStats
Note: The latest version of MAPI+CDO can be downloaded from here: http://www.microsoft.com/download/en/details.aspx?id=1004
2. If gathering against an Exchange 2010 Organization ensure MessageStats is configured to connect to a 2010 CAS server for the Connection Server:
- In the MessageStats Console expand Exchange Organizations
- Right Click the Exchange Organization Name and select Properties
- Select the Connection Server tab
- Check the Connect to an Exchange 2010 Organization radio button
- Enter the Netbios name of an Exchange 2010 CAS server
- Enter the name of an Exchange 2010 logon mailbox to which the MessageStats service account has Full Access rights
If the MAPI Provider requirements have been met, please use the following steps to troubleshoot the issue:
1. Repair possible MAPI corruption:
- Uninstall the MAPI Provider
- Run a Search for MAPISVC.inf and rename it to MAPISVC.inf.old
- Run a search for fixmapi.exe and then Right click on it and Select Open ( Nothing should happen which is expected behavior)
- Download the latest MAPI CDO from Microsoft and install it
2. Use MFCMAPI to test MAPI on the MessageStats server:
Note: With respect to MessageStats, Outlook connectivity is not a good indication of MAPI communication. MessageStats uses the same MAPI calls that MFCMapi uses which is why MFCMapi is used to test MAPI
- Download the latest 32bit version of MFCMAPI to the MessageStats server: http://mfcmapi.codeplex.com/
- Ensure you are logged in as the MessageStats service account and run MFCMapi.exe
- Select Session | Logon only (Does not display stores)
- Click New to create a new Profile and step through the Wizard
- Select the newly created profile in the Choose Profile dialog box and click OK
- Select MDB | Get Mailbox Table
- Enter the name of a Mailbox server and click OK
If any errors are encountered while trying to test MAPI using MFCMAPI it is an indication that there is an environmental problem with MAPI on the server where MessageStats is installed or a problem with MAPI communication to the Exchange servers
3. If errors were encountered when running MFCMAPI on the MessageStats server, test with MFCMAPI from a different server:
- Select a server that does not already have a MAPI Provider installed (Outlook, ESM 2003, MAPI CDO) and download and install the latest version of MAPI CDO
- Copy MFCMapi.exe to the server
- Logon as the MessageStats service account and run MFCMapi.exe
- Select Session | Advanced Logon | Logon only (Does not display stores)
- Click New to create a new Profile and step through the Wizard
- Select the newly created profile in the Choose Profile dialog box and click OK
- Select MDB | Open other mailboxes | Get Mailbox Table
- Enter the name of a Mailbox server and click OK
If there were no errors encountered when running MFCMAPI from the server and a list of mailboxes was displayed in MFCMAPI then the issue is an environmental issue on the server where MessageStats is installed. If errors were encountered it could be an indication of MAPI communication problems.
4. Use Microsoft Network Monitor to capture and analyze the network traffic from the MessageStats (or server used in step 3) to the Exchange server:
- Download and install the latest version of Network Monitor to the server where you are running the MFCMapi tests from
- Start Network Monitor
- Run MFCMapi.exe as the MessageStats service account
- Select Session | Advanced Logon | Logon only (Does not display stores)
- Click New to create a new Profile and step through the Wizard
- Select the newly created profile in the Choose Profile dialog box and click OK
- Select MDB | Open other mailboxes | Get Mailbox Table
- Enter the name of a Mailbox server and click OK
- Stop Network Monitor
- Review and analyze the traffic captured to determine if there is an issue with communication to the Exchange server
For details on how to use Network Monitor or how to analyze the traffic captured please consult Microsoft documentation or contact Microsoft for further assistance