Skip Ribbon Commands
Skip to main content

MAPI error troubleshooting

Last Update: 7/21/2017 11:27 AM
This article has been moved to our new Help Center. Please update your bookmarks.

Notice: This Knowledge Base article pertains specifically to the DeploymentPro (legacy) product, and not to the DeploymentPro product that is part of MSPComplete or DeploymentPro for UserActivation.​

​When configuring Outlook for Office 365 using DeploymentPro, and Outlook fails to configure, you can view the logs at the following location.


Open the most recent subfolder and othe Outlookconfigurator.log file.

In this log file there may contain one of the following errors.  

  1. [CRITICAL] Failure: Cannot create an empty profile. - Reason: MAPI_E_NO_ACCESS (ffffffff80070005)


This error occurs when the user has successfully configured the Office 365 profile through DeploymentPro and then rerun OutlookConfigurator. The OST file was locked by Outlook and the error was MAPI_E_NOACCESS, since Outlook was not able to write over the locked user data file with the same name.


  1. Download MFCMAPI from

  2. Launch the mfcmapi.exe

  3. Click on Profiles and select Show Profiles.


  1. Delete the newly created profile "useractivation..." (leave other profiles intact).
  2. Delete the "useractivation..." OST data file and autodiscover data file corresponding to the new profile under this directory:
    1. For Windows XP : C:\Documents and Settings\user\Local Settings\Application Data\Microsoft\Outlook
    2. For Windows 7+: C:\Users\<Username>\AppData\Local\Microsoft\Outlook
  3. Make sure Outlook is closed.
  4. Rerun bootstrap.exe from the end user email or right-click the Guardian icon in the system tray and click on Launch OutlookConfigurator.


 2.  [CRITICAL] Failure: Cannot configure the profile. - Reason: MAPI_E_NETWORK_ERROR (ffffffff80040115)


This error indicates a network error, and will keep Outlook from connecting to Office 365 even when trying to configure a profile manually.


There is no single solution to this error. Users should use OWA for Office 365 while the admin is troubleshooting.

Some things to check and try:

1. Run Windows Update to make sure all users' machines have the latest security updates and certificates installed.

2. Check to make sure that the following certificate is installed: Baltimore CyberTrust root certificate.

3. Reboot the computer.

4. Rerun bootstrap.exe from the end user email, or right-click the Guardian icon in the system tray and click on Launch OutlookConfigurator.