Hotfix for Symantec Enterprise Vault (EV) for File System Archiving 9.0, Service Pack 3 (SP3) Build 1164, PH creation on Celerra VNX 5700 using HTTPS results in UNKNOWN_PROTOCOL error

Article:TECH186146  |  Created: 2012-04-10  |  Updated: 2014-06-24  |  Article URL http://www.symantec.com/docs/TECH186146
Article Type
Technical Solution


Issue



Which version of Symantec Enterprise Vault (tm) can this hotfix be applied to?
This hotfix can only be applied to the following versions of Enterprise Vault for:

Enterprise Vault for File System Archiving 9.0.3, Build 1164 


Solution



What issue(s) does this hotfix resolve?
When attempting to create a placeholder post-archiving of an item, an error was experienced when the connection type was set to HTTPS.
The way in which placeholders are created in HTTPS configured environments has been changed and placeholders are now created successfully.
 

Which files does this hotfix replace? 

File Name File Version New File Version
KVS.EnterpriseVault.FileServerArchiveCommon.dll 9.0.3.1164 9.0.3.1240


How to Install this hotfix:

1. Stop the Enterprise Vault Admin Service on EV server. Note, this will cause all other services to stop.
2. Take a backup copy of "KVS.EnterpriseVault.FileServerArchiveCommon.dll", locatable in the Enterprise Vault installation folder (which by default is "C:\Program Files\Enterprise Vault", or "C:\Program Files (x86)\Enterprise Vault" on a 64-bit machine).
3. Copy the updated "KVS.EnterpriseVault.FileServerArchiveCommon.dll", packaged in this hotfix, to the Enterprise Vault installation folder, replacing the original.
4. Start the Enterprise Vault Admin Service.

How to Uninstall this hotfix:
1. Stop the Enterprise Vault Admin Service on EV Server.
2. Take the backed up copy of the files listed in the "Files updated" section and replace the hotfixed files, locatable in the Enterprise Vault installation folder(which by default is "C:\Program Files\Enterprise Vault", or "C:\Program Files (x86)\Enterprise Vault" on a 64-bit machine).
3. Start Enterprise Vault Admin Service.

Note:

1.  Where the EV site is configured to use https it is necessary to create certificates for EV server as well as Celerra file servers. The certificate for the EV Server should be created with the same name used when creating the connection from celerra to EV Site in the following command

fs_dhsm -connection certfs -create -type https -secondary https://EVserverAlias.abc.com/EnterpriseVault -user evadmin@abc.com -password "Admin1234"  -cgi n

 

As EV uses Alias name everywhere the certificate for EV server should be created using alias name.

 

2.  Where default ssl port (443) is not being used, the https (or http port in case of non SSL communication) port on celerra should be changed using the following commands

fs_dhsm -connection certfs -create -type https -secondary https://EVserverAlias.abc.com/EnterpriseVault -user evadmin@abc.com -password "Admin1234"  -cgi n –httpsport port_number

where port_number is the desired port number.

 

And in case of http connection:

fs_dhsm -connection certfs -create -type http -secondary http://EVserverAlias.abc.com/EnterpriseVault -user evadmin@abc.com -password "Admin1234"  -cgi n –httpsport port_number 

where port_number is the desired port number.

 


Attachments

Attachment filename EV_9.0.3_Hotfix_Etrack2700712.zip
EV_9.0.3_Hotfix_Etrack2700712.zip (119 kBytes)

Supplemental Materials

SourceETrack
Value2700712
Description

Placeholder creation on Celerra using HTTPS results in UNKNOWN_PROTOCOL error



Article URL http://www.symantec.com/docs/TECH186146


Terms of use for this information are found in Legal Notices