-
Title
VMWare ESXi Export and Agentless Protection fails with "Error occurred during execution of a VDDK's method call, please check VMwareProxy service" -
Description
Adding ESXi VMs to agentless protection either new or previously protected fails with:
The remote name could not be resolved: 'xxxxxxxx'Call to service method http://xxxxxxxxxx:8017/apprecovery/api/vmwareproxy/vddk/connectEx?readonly=True&snapshotRef=3-snapshot-24&transportModes=file%25253anbdssl%25253anbd POST failed: The remote name could not be resolved: 'xxxxxxxx'Error occurred during execution of a VDDK's method call, please check VMwareProxy serviceUnable to open virtual disk 'Hard disk 1'. Please ensure that the specified transport mode(s) 'file:nbdssl:nbd' are available or reset preferred transport modes to defaults.
Export to ESXi either new or previously setup export fails with:
Replay.Core.Implementation.Export.VirtualMachineExporterBase
Attach failed with exception
Replay.Common.Contracts.Virtualization.VddkApi.VddkApiProxyFailedException: Error occurred during running of a VDDK's method call, please check VMwareProxy service ---> WCFClientBase.ClientServerErrorException: Call to service method http://xxxxxxxxxx:8016/apprecovery/api/vmwareproxy/vddk/connectEx?readonly=False&snapshotRef=&transportModes=file%25253anbdssl%25253anbd POST failed: Unable to connect to the remote server ---> Microsoft.Http.HttpStageProcessingException: Unable to connect to the remote server ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond -
Cause
The core's host name has a different entry in the registry than what the actual name of the machine is. -
Resolution
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Perform these changes in the core's Windows registry to fix this issue:
- Launch the registry editor in the core
- Navigate to HKLM\SOFTWARE\AppRecovery\Core\CoreSettings
- Notice the value the String key DisplayName has, and edit it to give it the core's correct host name
- Navigate to HKLM\SOFTWARE\AppRecovery\Core\VMProxy
- Look at the string key HostAddress and edit its value to have the core's correct host name
Verify that the export and protection jobs successfully complete.