After FSAUtility Placeholder Migration from Celerra to Windows, Placeholders fail to retrieve.

Problem

When creating PlaceHolder (PH) files on the target Windows file server FSAUtility -PM uses the URL from the PH file that exists on the item in Celerra. However, this does not take into account that the secondary connection for the file system may be HTTPS.  Celerra will use part of the URL, but then use the secondary connection to determine if the connection to the Enterprise Vault (EV) server should be made via HTTP or HTTPS.  This will cause the PH files to be created with HTTP in the path and these will not work if EV is configured with an HTTPS connection which rejects HTTP connections.

Error Message

Access Denied

Cause

Celerra does not allow the OFFLINE_PATH value, of the OFFLINE_ATTRS, on a file to be set to HTTPS. This value for Enterprise Vault Placeholders will always be an http:// value.  The FSAUtility -PM option uses the OFFLINE_PATH value, without modification, to set the value of the PH that is created on the Windows file server.

Solution

As a workaround for this issue, create the following Registry value on the target Windows file servers, with a value of 1:
 

Once the above registry value is created restart the Placeholder service.  The above registry value, when set to 1, will recreate the URL of a PH dynamically upon a retrieval request using the current Web Application URL of the EV server.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Etrack : 3893295