Problem
When starting the Enterprise Vault Accelerator Manager Service (EVAMS), the service appears to start, but access to the Enterprise Vault (EV) Discovery Accelerator (DA) customer home page is not successful. Checking the Enterprise Vault Event Log shows the error
Error Message
Event Type: Error
Event Source: Enterprise Vault
Event Category: None
Event ID: 40966
Description: A program fault has raised an exception.
Exception: Could not load file or assembly 'KVS.EnterpriseVault.Interop.DirectoryConnection, Version=7.5.3.2130,
Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c' or one of its dependencies. The located assembly's manifest definition does not match
the assembly reference. (Exception from HRESULT: 0x80131040) Diagnostic:
Type: System.IO.FileLoadException
Reference:
Command Line: "C:\Program Files\Enterprise Vault Business Accelerator\AcceleratorManager.exe"
Application Domain: AcceleratorManager.exe
Process Id: 3324
Thread Id: 5432
Stack Trace: at
KVS.EnterpriseVault.Management.ProcessManager.SpawnProcess(Boolean restart)
at KVS.EnterpriseVault.Management.ProcessManager.KVS.EnterpriseVault.Management.IAdminControl.Start()
V-437-40966
Cause
This error is reporting a version mismatch with the listed file:
KVS.EnterpriseVault.Interop.DirectoryConnection.dll
In this instance, the listed version of 7.5.3.2130 does not exist as it should be 7.5.3.2138.
Solution
1) Log onto the DA server as the Vault Service Account
2) Stop the Enterprise Vault Accelerator Manager Service (EVAMS)
3) Create a folder off of the root of the C:\-Drive called DATemp (i.e., C:\DATemp)
4) Copy the following files from the DA installation folder (default is C:\Program Files\Enterprise Vault Business Accelerator) to the C:\DATemp folder for safe keeping
--- AcceleratorManager.exe.config
--- AcceleratorManagerConsole.exe.config
--- AcceleratorService.exe.config
--- ADSynchroniser.exe.config
5) Copy the license files from the DA installation folder's Installed Licenses folder (default is C:\Program Files\Enterprise Vault Business Accelerator\Installed Licenses) to the C:\DATemp folder for safe keeping
6) Use the Add or Remove Programs application from Control Panel to uninstall Veritas Enterprise Vault Discovery Accelerator
7) Use the Add or Remove Programs application to also uninstall Veritas Enterprise Vault
8) Restart the DA server after the uninstall operations have completed
9) Log onto the DA server as the Vault Service Account after it completes the restart
10) Delete the DA installation folder (default is C:\Program Files\Enterprise Vault Business Accelerator)
11) Delete the Enterprise Vault installation folder (default is C:\Program Files\Enterprise Vault)
12) Open regedit and delete the HKEY_LOCAL_MACHINE\SOFTWARE\KVS key
13) Open IIS Manager and delete the virtual directories for the DA customer and the EVBAAdmin sites if they still exist
14) Install, but do not configure, Enterprise Vault using the same version as running on the other EV servers in the site
15) Install Discovery Accelerator using the same DA installation software as was used in the prior installation and referencing the license files in the C:\DATemp folder when prompted
16) When the installation is completed, check to see if the EVAMS is running and start if not
17) Check the Enterprise Vault Event Log for any new instances of the Event ID 40966 error
18) If there are no new instances, then access the EVBAAdmin site on the DA server
19) The prompt will appear to create the DA configuration database
20) Enter the name of the SQL Server that contains the DA configuration database where requested (note that this information can be obtained from the AcceleratorManager.exe.config file in the C:\DATemp folder if needed)
21) Enter the name of the existing DA configuration database where requested (note that this information can also be obtained from the AcceleratorManager.exe.config file in the C:\DATemp folder if needed)
22) Select the option to use the existing database
23) Click the OK button to see the system connect to and use the existing configuration database
24) A prompt will appear to restart the Enterprise Vault Accelerator Manager Service (EVAMS) then click the OK button, so restart the EVAMS, THEN click the OK button
25) The EVBAAdmin page should appear and display all DA servers that are recorded in the DA configuration database
26) Expand the DA server on which the error occurred
27) Right click on the customer under the server
28) Select the option to check the virtual directory (this option will create that virtual directory on the DA server if it does not already exist)
29) Check the EV Event Log again for any new Event ID 40966 errors
30) If no new instances of the error, access the DA customer home page should be successful.
