Error Message

Could not load file or assembly 'KVS.EnterpriseVault.NSFManager.DLL' or one of its dependencies. The specified module could not be found.
    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
    at System.Reflection.Assembly.Load(String assemblyString)
    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)

Opening a message via a Report follows the same process as viewing the original message in the Accelerator Review Set whereby the Accelerator makes a call to EV to obtain the item from storage. To do this, it must communicate with EV using certain .dll files. For Lotus Notes messages, one of the files used is the KVS.EnterpriseVault.NSFMananger.dll file located in the CA or DA installation folder. If this file is either missing or is at a different version than the same file located in the EV installation folder on the Accelerator server, the message retrieval process will fail with the error above. Other files used include EVManagedSecurityWrapper.dll and EVContentManagementAPI.dll.

Please follow these steps to confirm the KVS.EnterpriseVault.NSFManager.dll along with the other required .dll files are correctly installed:

1. On the Accelerator server while logged on as the Vault Service Account (VSA):

1.1. Copy the EVManagedSecurityWrapper.dll, EVContentManagementAPI.dll and KVS.EnterpriseVault.NSFManager.dll files from the Enterprise Vault installation folder (e.g.: C:\Program Files (x86)\Enterprise Vault).

1.2. Paste the files into the root of the Accelerator installation folder (e.g.: C:\Program Files (x86)\Enterprise Vault Business Accelerator). Rename any existing files as needed.

2. Edit the VSA's PATH Environment Variable to include the above folders:

2.1. Right-click on the Computer in Windows Explorer | Properties | Advanced System Settings | Environment Variables.

2.2. Edit the Path variable in the System Variables pane and add the path to the EV installation folder (e.g.: C:\Program Files (x86)\Enterprise Vault) and Accelerator installation folder (e.g.: C:\Program Files (x86)\Enterprise Vault Business Accelerator) at the beginning of the Path Variable Value in a semi-colon-separated list.
An example of a completed Path Variable Value entry could look like this:

C:\Program Files (x86)\Enterprise Vault;C:\Program Files (x86)\Enterprise Vault Business Accelerator;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

2.3. Save the changes and close the System application window.

3. Reboot the Accelerator server to make the changes effective. If the Accelerator server cannot be rebooted, an alternate method would be to stop the Enterprise Vault Accelerator Manager Service (EVAMS), restart the IIS Admin Service, then start the EVAMS, finally log off and log back on to the Accelerator server as the VSA. This method may not be effective, however, and a reboot may still be required.

NOTE:

After an upgrade the copied files may not get upgraded and this procedure will have to be performed again for the current version.