Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Upgrade vSphere Replication 6.X to 8.X "Failed to connect to VR appliance" after entering source appliance root password on step 18. Upgrade option on console. (67807)

Last Updated: 2/12/2020Categories: TroubleshootingTotal Views: 2655Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vSphere Replication 6.1.2.2 upgrade to 8.1.1 is failing at step 18. Upgrade. Failed to Connect to VR Appliance [vrappliance.fqdn].
https://docs.vmware.com/en/vSphere-Replication/8.1/com.vmware.vsphere.replication-admin.doc/GUID-6DBB9977-DDCF-46CF-94DA-6B8BE683809B.html

hms-boot.log of new VR 8.1.1 Appliance

Failed to connect to VR appliance [vrappliance.fqdn]
(vmodl.fault.SystemError) {
faultCause = null,
faultMessage = null,
reason = Missing non-optional return value
}
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.checkNonOptionalValueProvided(ResponseImpl.java:247)
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:229)
at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:156)
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:53)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:106)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:629)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:610)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:360)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:311)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:184)
at com.sun.proxy.$Proxy37.findAllByDnsName(Unknown Source)
at com.vmware.hms.config.vix.VixRemoteExecutor.search(VixRemoteExecutor.java:691)
at com.vmware.hms.config.vix.VixRemoteExecutor.findHmsVm(VixRemoteExecutor.java:626)
at com.vmware.hms.config.vix.VixRemoteExecutor.<init>(VixRemoteExecutor.java:142)
at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.connectToVrAppliance(Vr81MigrationUpgradeWorkflow.java:447)
at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.lambda$compileUpgrade$1(Vr81MigrationUpgradeWorkflow.java:1201)
at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.run(Vr81MigrationUpgradeWorkflow.java:519)

Cause

In the vSphere Replication Appliance VAMi. The Network tab will show the VRHostname as the DNS shortname instead of its full fqdn.  The vSphere web client will show this on the VR Appliance VM's, summary tab.

The new VR Appliance 8.1.1 will be looking for the full fqdn of the original VR Appliance, that you set in the wizard.

Impact / Risks

none

Resolution

Ensure you have DNS configured correctly with forward and reverse lookup for the PSC, vCenter and VR Appliance.

Log into the original vSphere Replication VAMi page https://VRApplianceIP:5480

Select Networking tab. Change the VR Appliance's Hostname from shortname to full fqdn.

Enter password for your account.

Perform a Save and Restart to update the vCenter.

Proceed with Upgrading to 8.1.1.

https://docs.vmware.com/en/vSphere-Replication/8.1/com.vmware.vsphere.replication-admin.doc/GUID-6DBB9977-DDCF-46CF-94DA-6B8BE683809B.html

Workaround

none

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
PowerCLI connect-viserver を使用した vCenter Server へのスマート カード ログインに失敗する (67789)

KB
•
将 vCenter Server Appliance 从 6.5 升级到 6.7 后扫描更新遇到错误 (67771)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vIOMMU が有効な場合、Windows 10 v1903/19H1 および Windows Server 2019 v1903/19H1 がパワーオン時にハングするか BSOD が発生する (68043)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

Related Versions:

VMware vSphere Replication 8.x

VMware vSphere Replication 6.x

Take Our Survey

Support Assistant