Object reference not set to an instance of an object

[shirag]

Hello,

When i open the veeam backup and replication 9.5 console i get a message : "Object reference not set to an instance of an object ".
All my Jobs are running OK and i dont get failuers at all.
I tried to restore some files and it work..

I start to get this message after i moved a backup job folder from the main backup folder and after 2 days put back the folder where it belongs..

Do you have any idea what is the problem?

Thanks
Shira Golan

[Mike Resseler]

Shira,

It will be difficult to try to figure this out through the forums. Can you create a support call, post the case ID here and the outcome afterwards also? Our support engineers will be able to dig into the logs to figure out what exactly the problem is

Thanks
Mike

[shirag]

my support case is 02633155

Thanks

[Kage]

hi there,

im also getting the same error message "Object reference not set to an instance of an object". However, it only popup when i try to open my repository from Files menu. it doesnt allow me to browse my repository.

wht i did is rescan the repository. and after that it doesnt popups anymore.

[Mike Resseler]

Hmmm. So a rescan took the error away? Keep us informed if it appears again and then create a support call.

[Helferlein]

I have the same after upgrading VBR to Update 4.

Actually this error comes when backing up our Azure VM's which are upgraded to Agent Version 3 after installing Update 4.
The VMs dont get backed up since.

I already restarted the Veeam agent on those servers but this did not help.

Any ideas?

[Mike Resseler]

Peter,
Unfortunately the error could mean many things. Please create a support call so that the logs can be investigated (post the CASE ID here and the outcome after the research of the engineers)

Thanks
Mike

[Helferlein]

Thanks Mike.
Case No. is 03422335

[Helferlein]

Thanks to Veeam Support since they provided me with the following workaround:

Clone the job where the vm's are failing and map it back to the original repository of the original job.
Then run the job and it just should work out fine.

Since after that the name of the job and the repository name will be changed to '..._clone' you may just clone it back again the same way just with the original name and map the repository back to the original name. Then you have a running job with the original name again

[Mike Resseler]

Peter,

Thanks for coming back to us with the resolution that Veeam support provided you. Any change they also told you what went wrong?

[Helferlein]

Just checked in the case and Aleksey mentioned that they already have a fix for it.
But I do not know what's the fix number.
So anybody with the same problem should just reach out to support to get the fix.