How to use MFCMapi to test Microsoft Exchange Server Messaging API (MAPI) functionality and administrator access.

Article:TECH53597  |  Created: 2007-01-12  |  Updated: 2013-10-21  |  Article URL http://www.symantec.com/docs/TECH53597
Article Type
Technical Solution

Product(s)

Issue



How to use MFCMapi to test Microsoft Exchange Server Messaging API (MAPI) functionality and administrator access.


Solution




MFCMapi is a utility to test if MAPI is functioning correctly. It should be installed and run on the Exchange server, not the backup server and will only allow you to determine if there is a problem with the MAPI profile on the Exchange server.

Information:

 Download mfcmapi_bin.exe from MFCMapi.codeplex.com site select the following link:

 For additional information see Microsoft Knowledge Base article 291794:

Instructions:
  1. Double click on the file to start the extraction.
  2. Click 'Yes' on the license agreement screen.
     
  3. On the self extractor screen, choose a location to extract the files then click 'Unzip'.
     
  4. On the confirmation screen, click 'OK'.
     
  5. Click on 'Close' on the self extractor screen.
     
  6. Navigate to the location the files were unzipped to.
     
  7. Double click 'MFCMapi.exe'.

  8. On the 'About' screen, click 'OK'.

  9. Click on 'Session | Logon and Display Stores'.
     
  10. On the 'Choose Profile' screen, click on 'New'.

  11. Accept the default and click on 'Next'.
     
  12. Enter 'Test Profile' and click on 'Next'.
     
  13. Enter the name of the Exchange server and click 'Next > Next > Finish'.

  14. The 'Test Profile' should now show in the 'Choose Profile' screen.
     
  15. Click 'OK'.

  16. The upper window pane should now show 2 lines of information, one for mailboxes and one for public folders.
     
  17. Click on 'MDB | Open Other User's MailboxSelect the mailbox the error was received on and click 'OK'.

  18. Click on the plus next to 'Root Container | Top of Information Store | Inbox'

Note: If performing this test on a Windows Server 2008 or Vista operating system, and a network connection error occurs, you may need to disable IPv6.
This will need to be disabled via the network adaptor properties, as well as in the Windows registry. A reboot is required after making this registry change.

Warning: Incorrect use of the Windows Registry Editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes
 
 
To disable IPv6 on a Windows Server 2008-based computer via the Windows registry, please perform the following changes:
  1. Open the Windows Registry Editor.
     
  2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Services | Tcpip6 | Parameters
     
  3. In the details pane, click New, and then click DWORD (32-bit) Value.
     
  4. Type DisabledComponents, and then press ENTER.
     
  5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.*
    Note: The 0xffffffff value or the 4294967295 value disables all IPv6 components except for the IPv6 loopback interface.
 
 
Additional Values:
  • Note The value "0" is the default setting.
  • Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows Vista to use Internet Protocol version 4 (IPv4) instead of IPv6 in prefix policies.
  • Type 0x20 to use IPv4 instead of IPv6 in prefix policies.
  • Type 0x10 to disable native IPv6 interfaces.
  • Type 0x01 to disable all tunnel IPv6 interfaces.
  • Type 0x11 to disable all IPv6 interfaces except for the IPv6 loopback interface.



Legacy ID



291357


Article URL http://www.symantec.com/docs/TECH53597


Terms of use for this information are found in Legal Notices