[FIX] Object reference not set to an instance of an object…

Hi! As you know, after updating VMware vCenter to 6.7 Update 1, processing of all VMs fails with “Object reference not set to an instance of an object“. The issue is triggered by an update to the vSphere API version in vCenter 6.7 U1. It appeared to be a small API change which had an unexpectedly big impact on Veeam B&R. Here’s the post to introduce the workaround, waiting Veeam B&R 9.5 Update 4…


Create the following registry value under “HKLM\SOFTWARE\Veeam\Veeam Backup and Replication” key on the backup server:

Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1 = 6.7

Step by step guide:

First, launch “regedit” command line:

Then, create the “VMwareOverrideApiVersion” key in “Veeam Backup & Replication” directory (key type “Multi-String Value“):

Add the value data “6.7.1=6.7“:


Basically, you can re run your backup job.

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality because we don’t know the specific API changes that made VMware increment the API version. We’re working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release: Veeam Backup & Replication 9.5 Update 4.

Step by Step Guide Veeam B&R 9.5 U3a Upgrade!

You can learn more about Veeam Backup & Replication 9.5 here.

VeeamON Chicago – Vision & Strategy 2018 – Recap!

VeeamONForum France Recap!

VeeamON Forum France – Interviewed by LeMagIT: LeMagIT


Please follow and like us:

Leave a Reply


Enjoy this blog? Please spread the word :)