We are currently in the middle of an Outlook 2007 to Outlook 2013 POC & to date we have had some challenges in regards to the functionality of the Virtual Vault after the installation of Outlook 2013. Outlook 2013 installs without error. We then launch Outlook all looks well with the Virtual Vault in the navigation pane, however when you click on the Virtual Vault to expand the folder set you get the error message "Cannot expand the folder. The set of folders cannot be opened. An unexpected error has occured. MAPI was unable to load the information service EVMSP.DLL. Be sure the service is correctly installed and configured".
To set the scene we have the current configuration on our POC test case machine
- Outlook 2007 SP3 installed side by side with Outlook 2013 15.0.4649.1001 :
- Enterprise Vault Outlook Addin 10.0.4.1293
- Outlook 2007 SP3 user with Virtual Vault working as expected
- Outlook 2013 15.0.4649.1001 with Virtual Vault, however cannot expand folder set because of the MAPI error above.
In order to re-enable the Vault we have had to do one of two tasks below:
1. As part of the Outlook 2013 installation script we perform a repair of the Enterprise Vault add-in, which results in most cases of a working Virtual Vault upon completion of the installation of Outlook.
2. By running the following command rundll32 EVMSP32.dll,MergeEVMSPWithMAPISVC
To my understanding the reason for this MAPI error is a result of the new installation of Outlook 2013 creating a new MAPISVC.INF where the Enterprise Vault services have not been registered. This then results in the Virtual Vault not functioning as expected. In performing one of the two tasks below this registers the service with MAPI, which results in a working Virtual Vault.
What i would like to understand is if anyone in the forum has come across an issue like this & what approach you have taken to resolve it. Any insight, suggestions or comments would be greatly appreciated.
Solved! Go to Solution.
Sorry just to clarify ... are you infering a feature the addin should have by this comment?
"this issue would be solved straight away if the client made the check on startup"