Error Message

Launching the VEA locally on the server would give the errors below:

Error V-39-53247-2

Error while connecting to localhost

Could not connect to server. Capabilities mismatch.

VEA uses the VxVMCERT.pem file located at C:\Program Files\Veritas\VERITAS Object Bus\bin\ for SSL connections.

The issue can occur if the below registry entries are missing:

HKEY_LOCAL_MACHINE\Software\Veritas\VxSVC\CurrentVersion\Network\Params\Security\SSLCERTPATH

AND

HKEY_LOCAL_MACHINE\Software\Veritas\VxSVC\CurrentVersion\Network\Params\Security\SSLKEYPATH

1) Verify if the VxVMCERT.pem file exists at C:\Program Files\Veritas\VERITAS Object Bus\bin\

NOTE: If it does not exist, then copy the file from a working server to the above path and run the following command to import the certificate into the certificate store.

"C:\Program Files\Veritas\VERITAS Object Bus\jre\bin\keytool.exe" -import -noprompt -file "C:\Program Files\Veritas\VERITAS Object Bus\bin\vxvmcert.pem" -alias VxVMCERT -keystore "C:\Program Files\Veritas\Veritas Object Bus\jre\lib\security\cacerts" -storepass changeit

2) Once the file is made available, run the commands below to generate the missing registry keys.

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\Network\Params\Security /v SSLCERTPATH /d "C:\Program Files\Veritas\VERITAS Object Bus\bin\vxvmcert.pem" /f /reg:64

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\Network\Params\Security /v SSLKEYPATH /d "C:\Program Files\Veritas\VERITAS Object Bus\bin\vxvmcert.pem" /f /reg:64

3) Restart the Veritas Enterprise Administrator (vxsvc) service from Windows Services Console (services.msc)

IMPORTANT: If the Veritas Installation is performed at a non-default path, ensure that the VxVMCERT.pem file is copied to the appropriate path and the above keytool.exe and REG ADD commands are modified accordingly.