Configuring MAPI

Additional configuration steps are required for MAPI before you can define the parameters for incoming and outgoing mail within System Admin.

MAPI is no longer supported from ASM version EOS (10.5).

You must:

  1. Download MAPI onto the web server

  2. Create the MAPI profile on the web server

  3. Configure ASM Core to use the MAPI connection

  4. Configure the ASM Core services to use appropriate access account

If you have difficulties, see the Troubleshooting section for suggestions.

Downloading the MAPI Client

You must have MAPI and Outlook downloaded and configured on the web server where ASM Core is installed.

If you have the 64bit version of Outlook, Exchange Server, or Exchange Admin installed on the web server, MAPI is already provided.

Creating the MAPI Profile

A MAPI profile needs to be created on the web server.

If you are using Exchange as a mail server, you will not need to create a MAPI profile for the incoming email account.

If you have Outlook installed on the web server, you can add MAPI profiles using the Mail Settings in the Control Panel.

  1. Open the Mail Setup dialog box by selecting Control Panel > Mail.

  2. Select the Show Profiles button.

  3. Add the MAPI profile.

If you do not have Outlook installed, use the following link to find instructions, as provided by Microsoft.

Or use the steps below:

  1. Download the MAPI Profile Manager from the Microsoft website onto the web server.

  2. Open Profman2.exe from the extracted directory.

  3. Click Create New Profile and enter a name for the profile.

  4. Select the newly created profile and click Add service to selected profile.

  5. Select Microsoft Exchange Server, and click OK.

  6. Enter the name of the Microsoft Exchange server and Mailbox to be used with ASM Core.

  7. Click Check Name in this window. The Exchange Server and Mailbox should be underlined, indicating that they are reachable. If not, or you see an error, check the details and try again.

  8. If additional settings, such as Advanced, Dial-Up Networking or Remote Mail are required for your MAPI connection, consult your Exchange Server documentation.

  9. Click OK. Your MAPI profile is now configured.

If the MAPI account has more than one mailbox, ASM Core uses the default folder to retrieve email.

Configuring ASM Core to use the MAPI connection

Before you start

If you have details for another server displayed, you must close these before adding a new server.

You must have System Set Up selected in the Admin tab of your General Access security role.

  1. From System Administration, expand the System section and open Email Settings.

  2. Select the Incoming or Outgoing server that you want to add, and click Add.

  3. Enter the Exchange Server and mailbox details.

  4. Enter the login ID and password of the appropriate account. Or select the Use NT Auth checkbox.

  5. Enter details for options such as Logging Analyst and Auto Reply, as described in Email Settings.

  6. Click Save. MAPI is now configured for use with ASM Core.

You cannot test the connection on MAPI accounts within the Email Server Details as you do with SMTP or IMAP.

Configuring ASM Core Services

To use MAPI for incoming emails, the ASM Messaging Service must run as an account that has full access to the mail server and MAPI mailbox.

If using a normal Windows account it must have full access to the mail server and MAPI mailbox, and have appropriate privileges to run as local service.

If using MAPI mailbox account, it must also be a services account with the appropriate privileges to run as local service. Use this account to log onto the web server so that a Windows profile is created on that server.

The account must also have full access to the database if DB NT Auth is selected in Server Console > System Properties > Database tab.

All ASM Core Services must run under the same account.

  1. Click Start > Run, type services.msc, and click OK. The Services window opens.

  2. Right-click each of the ASM Core services and select Properties.

  3. Click the Log On tab and change the Log On to the appropriate account. Be sure to include the domain in the Login ID (DOMAIN/username).

  4. Change all of the services to run as the same account.

  5. Restart all of the ASM Core Services by restarting the Administrative Service.


If you receive errors after completing the steps above, use these troubleshooting steps.




Often indicates that the account you are using does not have permission or cannot reach the Exchange server.

  • Ensure that you have installed the Microsoft Exchange Server MAPI Client from the link above, and that you have configured a profile for the account.

  • Ensure you have configured the services to run as the email account, and that the email account has been granted Log On as Service rights on the server.

  • Deselect the NT Authentication checkbox in ASM Core and restart the Messaging Service.


Often indicates a permission issue, where the email account configured for the services does not have full rights to the mailbox.

If you are using Microsoft Exchange, open a web browser and log into Outlook Web Access as the email account you have configured for the services. Ensure that this account can successfully log into the account.


A catch-all error, but often indicates that there is a configuration problem with one or more folders on the mail server.

If you are using Microsoft Exchange, ensure that Public Folders have been configured on the Exchange server and are accessible by the email account you are using.

If the error persists after configuring the Public Folders, you can add a string to the registry to tell Collaboration Data Objects to ignore the Public Folders:

Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393 ( .

  1. On the ASM Core server, click Start > Run, type regedit, and press Enter. The Registry Editor window opens.

  2. Navigate to: HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/Windows Messaging Subsystem/CDO

  3. If no CDO key exists, create one.

  4. Add a 32-bit DWORD with the name Ignore No PF, and set the value to 1.

  5. Restart the messaging service for the change to take effect.