Unable to create Remote Agent for Deduplication on a BE 2010 R2 Remote Agent or a system that was upgraded from a BE 2010 Remote Agent
After the creation of the Remote Agent for Deduplication and a restart of the Backup Exec services, the Deduplication Folder does not show up under the Remote Agent in the Devices tab.
Enabling SgMon on the remote system and setting the debug level in the RAWS pd.conf file to 10 results in an error being reported when the pdregister command tries to run:
[ndmp\ndmpsrvr] - DeviceIo: STS: Error: PDVFS:  pdvfs_create_ost_agent: failed to execute command: C:\Program Files\Symantec\Backup Exec\RAWS\\pdregister --action certificate --type Agent --todisk --keydir "C:\WINDOWS\TEMP\pdvfs_keydir_46"
[ndmp\ndmpsrvr] - DeviceIo: STS: Error: pd_register ERROR PdvfsRegisterOST for MEDIASERVERNAME failed (22 Invalid argument)
[ndmp\ndmpsrvr] - DeviceIo: STS: Error: get_agent_cfg_file_path_for_mount pd_register failed for configuration file C:\Program Files\Symantec\Backup Exec\RAWS\\MEDIASERVERNAME.cfg
[ndmp\ndmpsrvr] - DeviceIo: STS: Warn: get_agent_cfg_file_path_for_mount cannot read PureDisk agent configuration file C:\Program Files\Symantec\Backup Exec\RAWS\\MEDIASERVERNAME.cfg (2060001)
Attempting to run pdregister.exe manually results in an error that libeay32.dll could not be found.
Another way to confirm the existence of this problem is to check the dates of the pdACE.dll and pdACE_ssl.dll on the Remote Agent. If the date on these files is 12/2/2009 and this is a Backup Exec 2010 R2 or later installation, then this problem will occur on this sytem.
This problem is caused by a failure to update the pdACE.dll and pdACE_ssl.dll on the Remote Agent. This happens when an older version of these files is present on the system.
The problem can be resolved by uninstalling the Remote Agent completely. Make sure that there are no files left in the Backup Exec program files directory on the Remote Agent system. Then, re-install the agent from a Backup Exec 2010 R2 SP1 or later system.
This problem is resolved in Backup Exec 2010 R2 Hotfix 154003 (http://www.symantec.com/docs/TECH154003) and Backup Exec 2010 R3