Virtual Vault fails to launch as the application cannot locate the MAPI provider information for the information store.

  • Article ID:100022450
  • Modified Date:
  • Product(s):


When the Virtual Vault client is installed on an operating system (OS) where the locale does not match only the user that installed the applications will be able to utilize Virtual Vault.

This occurs due to the manner in which Virtual Vault makes use of the underlying MAPI call 'FGetComponentsPath' to get the UILanguage entry. This entry exists under the SID of the user that installed Outlook. If this fails, Virtual Vault will try to get additional configuration information using locale paths to locate the Mapisvc.inf file that will contain information pertaining to the information store providers configured on the system.

For example, on an English installation the default path is: C:\Program Files\Common Files\System\MSMAPI\1033 where '1033' pertains to the English Locale. On non-English versions the numeric path will change to reflect the language accordingly, i.e. Dutch would be '1043'

Virtual Vault may attempt to repair the Mapisvc.inf entry under this path if the user logged in has the necessary permissions to update files in that folder. The installer will locate and update the Mapisvc.inf file in the %system% path when Virtual Vault is installed with an account that has Administrative permissions on the machine. If the user does not have permission to update files under the Locale location, a generic access denied error will be logged. This error occurs when Virtual Vault tries to repair the missing entry in the file as determined by the path obtained from the FGetComponentsPath function call.  


Error Message

The following errors may also be generated when attempting to configure Virtual Vault:

Enterprise Vault could not add or remove the following Virtual Vaults:


Try again later.

A client trace will record the following entry:

[1528] Could not create an instance of Virtual Vault. Verify that EVMSP is correctly configured in MAPISVC.INF: 0x8004010F
[1528] ~EVMSPConfig::AddEVMSPService: 0x8004010F


Option 1
The locale must be the same for Outlook, Virtual Vault and the Operating System.

Option 2
Add the user account that is accessing Virtual Vault 'Power User' rights to the locale folder path. (For example, a Dutch locale path would be c:\program files\Common Files\System\MSMAPI\1043)


This issue has been addressed in the following release:

Enterprise Vault 9.0.4 Cumulative Hotfix 2

Enterprise Vault 10.0.3 - Release Notes

Was this content helpful?

Get Support