Event ID 568 and Event ID 567 seen in the Event Logs after upgrading to Compliance Accelerator 14

Event ID 568 and Event ID 567 seen in the Event Logs after upgrading to Compliance Accelerator 14

Article: 100048966
Last Published: 2020-11-30
Ratings: 0 0
Product(s): Enterprise Vault

Problem

After upgrading Enterprise Vault (EV) Compliance Accelerator (CA) to version 14, the errors below are seen in the Event Logs. There does not appear to be any loss of CA functionality. Restarting the Enterprise Vault Accelerator Manager Service and/or rebooting the CA server does not have any effect on the errors. Additionally, the errors below may also be seen when performing any CA functions that require CA to interact with EV, such as running Searches, Reviewing items or running Exports.

 

Error Message

Log Name: Veritas Enterprise Vault
Source: Accelerator Manager
Event ID: 568
Level: Error
Description:
APP AT - Customer ID: X - Failed to initialize Enterprise Vault FIPS libraries. Reverting to .NET libraries
Reason: Could not load file or assembly 'EVManagedSecurityWrapper.dll' or one of its dependencies. The system cannot find the path specified.
Stack:    at System.Reflection.AssemblyName.nGetFileInformation(String s)
   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
   at KVS.Accelerator.Common.SecurityAlgorithms.InitializeFIPSAlgorithms(String FIPSDLLPath)

V-437-568


Log Name: Veritas Enterprise Vault
Source: Accelerator Manager
Event ID: 567
Level: Error
Description:
APP AT - Customer ID: X - Failed to perform security operations
Reason: Value cannot be null.
Stack:    at System.Threading.Monitor.Enter(Object obj)
   at KVS.Accelerator.Common.SecurityAlgorithms.ComputeHash(Object hashAlgorithm, Byte[] bytesToHash)
   at KVS.Accelerator.Server.CommonStarterBase.StartApplicationThreads(CustomerType custType)

V-437-567

 

Cause

These errors are caused by a new code check introduced in CA 14. The code determines the location of certain EV .dll files required for CA communications with EV. If the code does not find the files in the specified location, it reverts to using the .NET libraries instead of the specified files and logs the errors. The files location is specified in the Registry on the CA server. At the time of this writing, the Registry contains the location of the files in the 32-bit section of the Registry. However, as the EV files are 64-bit and the 64-bit section of the Registry does not contain the location of the file, the errors are logged. The steps listed below will add the necessary 64-bit Registry information to alleviate the errors.

Note - These errors are only seen when using the full EV binaries on the CA server. If the EV API is installed on the CA server, these errors are not seen. It is not recommended to uninstall the EV binaries and then install the EV API to correct this issue. Uninstalling the EV binaries could also uninstall other Registry components required by CA and will require CA to also be uninstalled and reinstalled after uninstalling the EV binaries and installing the EV API.

 

Solution

To alleviate these errors, add the EV files location to the 64-bit section of the Registry:

1. Log on to the CA server with an account having local administrative rights.

2. Determine the installation folder of the EV binaries. The default location is C:\Program Files (x86)\Enterprise Vault. There are 2 methods to do this:

2.1. From File Explorer:
2.1.1. Right-click the Start button and select File Explorer.

2.1.2. Browse the drives and folders to find the Enterprise Vault installation folder location.

2.2. From the Registry:
2.2.1. Right-click the Start button and select Run.

2.2.2. Enter regedit in the Open: box and select OK.

2.2.3. Expand HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\KVS\Enterprise Vault\Install.

2.2.4. Find the Enterprise Vault installation folder location under the Data column of the InstallPath string.

3. Once the EV binaries installation folder has been determined, there are 2 options to add the required Registry value:

3.1. Use the Registry Editor:
3.1.1. Right-click the Start button and select Run.

3.1.2. Enter regedit in the Open: box and select OK.

3.1.3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE.

3.1.4. Under HKEY_LOCAL_MACHINE, right-click the SOFTWARE Key and select New > Key.

3.1.5. Enter the Key name: KVS

3.1.6. Right-click the KVS Key and select New > Key.

3.1.7. Enter the Key name: Enterprise Vault

3.1.8. Right-click the Enterprise Vault Key and select New > Key.

3.1.9. Enter the Key name: Install

3.1.10. The path should now look like this: HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Install. If correct, then right-click the Install Key and select New > String Value.

3.1.11. Enter the String Value name: InstallPath

3.1.12. Either double-click the InstallPath string or right-click the InstallPath string and select Modify.

3.1.13. Enter the Enterprise Vault installation folder location in the Value data field with a trailing backslash. For example, if the Enterprise Vault installation folder location is C:\Program Files (x86)\Enterprise Vault, enter the Enterprise Vault installation folder location as (note the trailing back slash): C:\Program Files (x86)\Enterprise Vault\

3.1.14. Close the Registry Editor window.

3.1.15. Either restart the Enterprise Vault Accelerator Manager Service from the Services control panel (right-click the Start button | Run | services.msc | OK) or restart the CA server.

3.2. Use a .reg file:
3.2.1. Right-click the Start button and select Run.

3.2.2. Enter notepad in the Open: box and select OK.

3.2.3. Add the following lines to the new Notepad file.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Install]
"InstallPath"="C:\\Program Files (x86)\\Enterprise Vault\\"

3.2.4. Edit the InstallPath location to point to the Enterprise Vault installation folder location. Note the use of the quotes and the double back slashes, including the trailing double back slashes - this is the correct syntax. For example, if the Enterprise Vault installation folder location is C:\Program Files (x86)\Enterprise Vault, enter the Enterprise Vault installation folder location within the double quotes as (note the trailing back slashes): C:\\Program Files (x86)\\Enterprise Vault\\

3.2.5. Once the InstallPath location has been correctly edited to point to the Enterprise Vault installation folder location, click on File, then select Save As.

3.2.6. Select a Folder location to store the file.

3.2.7. Change the Save as type to All Files (*.*).

3.2.8. Give the file a name and add the .reg extension. The .reg extension will not be automatically added and must be included in the file name.

3.2.9. Click Save and exit Notepad.

3.2.10. Navigate to the location of the file and double-click the file.

3.2.11. Read and acknowledge the Registry Editor warning, then acknowledge the Registry Editor information advising successful addition of the keys and values.

3.2.12. Either restart the Enterprise Vault Accelerator Manager Service from the Services control panel (Right-click the Start button | Run | services.msc | OK) or restart the CA server.

 

Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.

This issue is currently under investigation by Veritas. Pending the outcome of the investigation, this issue may be resolved by way of a cumulative hotfix, release update or service pack in the current or future versions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see https://www.veritas.com .

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

 

References

JIRA : CSC-7649

Was this content helpful?