Skip to main content

VBO365: Object reference not set to an instance of an object (Teams)

  • August 26, 2021
  • 16 comments
  • 3394 views

regnor
Forum|alt.badge.img+14

I have just discovered on Twitter that there’s currently a problem with Teams Backup in Veeam Backup for Office 365 which could affect many installations.

It looks like Microsoft did change something on their side and so Teams backup is failing with the following error: “Object reference not set to an instance of an object”

If you are affected by this problem, you can request the hotfix from Veeam Support.

Here is the corresponding R&D forums topic: https://forums.veeam.com/veeam-backup-for-office-365-f47/teams-backup-failing-with-object-reference-not-set-to-an-instance-of-an-object-t76162.html

16 comments

Mildur
Forum|alt.badge.img+12
  • Influencer
  • August 26, 2021

Hotfix was installed yesterday on three of my vbo365 servers.

Backups are running fine again.


regnor
Forum|alt.badge.img+14
  • Author
  • Veeam MVP
  • August 26, 2021

Good to hear @Mildur:thumbsup:


Nico Losschaert
Forum|alt.badge.img+11
  • On the path to Greatness
  • August 26, 2021

@Mildur , do you have a link with the hotfix, I need it too :wink: , or is creating a Veeam case required?


Mildur
Forum|alt.badge.img+12
  • Influencer
  • August 26, 2021

A case is required. The Hotfix is a “private Hotfix” at the moment.

@Nico Losschaert 


Nico Losschaert
Forum|alt.badge.img+11
  • On the path to Greatness
  • August 26, 2021

Thx @Mildur, will do :wink:


regnor
Forum|alt.badge.img+14
  • Author
  • Veeam MVP
  • August 26, 2021

It looks like support is really fast with providing this hotfix, and I think you can alsoreuse it for your other customers.


Mildur
Forum|alt.badge.img+12
  • Influencer
  • August 26, 2021

Yes, i have used the same hotfix on three systems now


Nico Losschaert
Forum|alt.badge.img+11
  • On the path to Greatness
  • August 26, 2021

Yes, after 10 minutes I received already a link to the hotfix :sweat_smile:


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • August 26, 2021

Amazing how MS changes things but then how quickly Veeam fixes it. #Veeamazing


Nico Losschaert
Forum|alt.badge.img+11
  • On the path to Greatness
  • August 26, 2021

Indeed @Chris.Childerhose , that’s why Veeam Support is the best Support department of the large Vendors!!!


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • August 26, 2021

Indeed @Chris.Childerhose , that’s why Veeam Support is the best Support department of the large Vendors!!!

I won't disagree there 😂


Mildur
Forum|alt.badge.img+12
  • Influencer
  • August 26, 2021

Yes, after 10 minutes I received already a link to the hotfix :sweat_smile:

They are fast :)


regnor
Forum|alt.badge.img+14
  • Author
  • Veeam MVP
  • August 26, 2021

Indeed @Chris.Childerhose , that’s why Veeam Support is the best Support department of the large Vendors!!!


Nothing to add there 😅


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • August 26, 2021

A case is required. The Hotfix is a “private Hotfix” at the moment.

@Nico Losschaert

:thumbsup:


Mildur
Forum|alt.badge.img+12
  • Influencer
  • August 27, 2021

A KB Article with the hotfix was released:

https://www.veeam.com/kb4201


regnor
Forum|alt.badge.img+14
  • Author
  • Veeam MVP
  • August 27, 2021

A KB Article with the hotfix was released:

https://www.veeam.com/kb4201

Thanks for sharing 😊