Article number
000003453
Affected Versions
All
Source Hypervisor
All
Target Hypervisor
All

Error: “The remote name could not be resolved” during install or upgrade of VRA

Viewed 539 times

Summary

This article covers a scenario in which a VRA installation or upgrade fails with a web exception specifically due to DNS.

Root Cause

This is a configuration issue either with DNS or other name resolution solutions (ie. Windows hosts file)

The "Object reference not set to an instance of an object" actually occurs on rollback of the task and that is what gets printed on the ZVM:

VraUpgradeTask,UpgradeVraFuncLocked,"Upgrade failed, set upgrade failed status","System.NullReferenceException Void DestroyVM(Zerto.Zvm.Common.VirtualizationManager.VCenter.VMIdentifier, Boolean) System.NullReferenceException: Object reference not set to an instance of an object.

Symptoms

  • During VRA installation or upgrade (Auto or manual), the task may fail reporting the following error:
"Object reference not set to an instance of an object."
  • In the ZVM logs, you see the following entries:
OvfDeployer,OvfUploadVmdkFile,Going to upload C:\Program Files\Zerto\Zerto Virtual Replication\vra\vra-disk1.vmdk to https://hostname/nfc/52c66783-3f2c-7482-2b54-08a78fc22567/disk-0.vmdk,

Basics,Error,"error while inserting C:\Program Files\Zerto\Zerto Virtual Replication\vra\vra-disk1.vmdk into vm. Exception System.Net.WebException: The remote name could not be resolved: 'hostname'

 
OvfDeployer,Deploy,Failed to upload OVF file,"VCenterConnectionLayer.VMBasicsException Void Error(Zerto.Infra.Log.LogLevel, System.Exception, System.String, System.Object[]) VCenterConnectionLayer.VMBasicsException: error while inserting C:\Program Files\Zerto\Zerto Virtual Replication\vra\vra-disk1.vmdk into vm. Exception System.Net.WebException: The remote name could not be resolved: 'hostname'
  • The hostname is NOT the FQDN and ping from ZVM to hostname will fail
  • Ping from ZVM to FQDN or IP is successful

Solution

1. Have customer enter/fix the DNS entry on their DNS server or ensure ZVM is pointed to correct DNS server.

2. As a temporary workaround or troubleshooting step, you can edit the ZVM's hosts file:
a. Open the hosts file (ie: C:\Windows\System32\drivers\etc\hosts) with administrative privileges
b. Add a line to map the IP to the host name and save file
c. Retry to upgrade/install task via ZVM GUI