Client Extensions installed on a machine running Outlook 2007/2010 and Exchange System Manager (ESM) will not load

  • Modified Date:
  • Article ID:000081324


Enterprise Vault Client Extensions that are installed on a machine with Outlook 2007/2010 and Exchange System Management installed will not load.

As per Microsoft Knowledge base, Microsoft does not support installing Microsoft Outlook and Microsoft Exchange Server 2003 (including Exchange System Manager), Microsoft Exchange 2000 Server (including Exchange System Manager), or Microsoft Exchange Server 5.5 on the same computer.

For more details about this limitation, please visit the following link:

Error Message

The Add-in "Enterprise Vault" (C:\Program Files\Enterprise Vault\EVClient\Valkyrie.dll) cannot be loaded and has been disabled by Outlook. Please contact the Add-in manufacturer for an update. If no update is available, please uninstall the Add-in.


Several common scenarios for the error to be displayed include the following:

Scenario 1
Exchange System Manager 2003 and Outlook 2007/2010 are installed on the same machine.

1. Re-Install Exchange System Manager and reboot the system
2. Un-Install Exchange System Manager and reboot the system.

3. Un-Install the Enterprise Vault Client Extensions and Outlook, then reboot the system.
4. Re-Install Outlook and then Install the Enterprise Vault Client Extensions.
5. Run FIXMAPI from a command prompt, which does not require a reboot.  Fixmapi.exe is located under \(Windows Drive)\Windows\System32

NOTE:  Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.  

Scenario 2
Outlook 2007/2010 is installed but the MAPI Profile in the Registry has become inconsistent

1. Open Outlook and navigate to Help -> Office Diagnostics (in Outlook 2003 this was "Detect & Repair").

2. When Office Diagnostics completes open a command prompt

3. Type "fixmapi" and press "Enter". The "fixmapi" command generates no output and runs silently.

NOTE:  Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.  

4. Restart the machine.

Scenario 3
The Enterprise Vault Client has not been registered correctly Or Enterprise Vault Client will run a self re-install every time Outlook is restarted and also an operation calling an Archived object is called for the first time after restarting.

1. Open a command prompt and navigate to "C:\Program Files\Enterprise Vault\EVClient"

2. If Enterprise Vault 7 Client or later has been installed, type "ResetEVClient" and press "enter" (one of the steps taken is to re-register "Valkyrie.dll").

3. If Enterprise Vault 6 Client or earlier has been installed, type "regsvr32 Valkyrie.dll" and press "enter".

Note: What to do if file permissions do not allow ResetEVClient to delete the .dat files
1. Close Outlook.
2. Search for and manually delete the following files in the affected user's profile: extend.dat, outcmd.dat, frmcache.dat.
3. Run ResetEVClient to register valkyrie.dll.
4. Restart Outlook and test. Can perform this procedure on all user's profiles if required.

If the error still occurs or the "Valkyrie.dll" cannot be registered, reinstall the Enterprise Vault client from the installation media.

Scenario 4
Windows Desktop Search, Exchange System Manager and Outlook 2007/2010 have been installed on the same machine

After installing Windows Desktop Search (Instant Search in Outlook 2007/2010) the "Valkyrie.dll" fails to load due to inconsistencies with the Messaging Application Programming Interface (MAPI) profile in the Windows registry.

This can occur when uninstalling Windows Desktop Search 2.6 and installing Windows Desktop Search 3.0.1 without performing the required reboot.

1. Uninstall the Enterprise Vault client.

2. Uninstall Outlook and restart the machine.

3. Reinstall Outlook and restart the machine once more.

4. Install the Enterprise Vault Client

5. From a command prompt type "fixmapi" and press "Enter".

NOTE:  Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.  

6. Restart Outlook and full functionality should be restored.

Note: In some environments running the Fixmapi utility will resolve the issue. (For more information on the Fixmapi utility refer to Microsoft article )


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)