Teams backup failing with: Object reference not set to an instance of an object.

[cerberus]

Case #04981502

This error started showing up in our logs on Friday (08-20-2021) and VBO 5.0.2.22 is failing to backup Teams.

According to support some backend changes in O365 last week is causing this, they are aware of the issue and its with R&D and Q&A.

I was not able to find any hits on this issue as of yet, so posting this as a FYI for others.

No ETA on fix or any other details at this time due to the newness of the problem.

[corymcmahon]

We are seeing this happening this morning in backup failures.

[grantemsley]

I've been seeing the exact same thing. Should I open my own ticket or just wait?

[Mike Resseler]

Grant, please open also your own ticket.

[cerberus]

Looks like Veeam is on top of this one, latest update I got was: "QA team has isolated the issues with the API that was changed by Microsoft, and they are working to implement a fix as quickly as possible."

We'll likely be seeing a new VBO build soon.

[Robvil]

Same here starting today.

Failed to process team: Webshop. Object reference not set to an instance of an object.

Case ID: #02265478

/Robert

[Mildur]

3 different VBO365 installations with the issue.
Will open a support case tomorrow for one of them.

[BrianD]

Same here, started failing Sunday night. Ticket open 04982535. I think we are waiting on a hotfix.

[lharmer]

We are also seeing this as of this morning for multiple organisations with Teams data.
Logs uploaded on #04984913

[dan.kennedy]

Same issue here - seeing this across multiple customer jobs
Logs uploaded to case #04985381

[Polina]

Hi All,

The root cause has been identified and the fix should be available via support in a few hours.

[Mildur]

Thanks Polina

[Switchie_Urs]

same here. started today for multiple organizations. logs uploaded to Case #04985525

[Mildur]

Case #04985653

[bpaquin]

Same error here, started today, will wait for a hotfix I guess...

[Mike Resseler]

Yes, we are spreading out the hotfix. Please create a support case for faster solution

[Mildur]

Thanks Mike, we received the hotfix.
I am implementing it right now to the first environment.

[lharmer]

Hotfix received and applied, seems to have resolved the issue. Thanks Veeam, speedy turnaround!

[ajriek1970]

Case #04986340

[Moodie007]

We are having the same issue. Can we have the hotfix please case #04986461. Thanks.

[Markus Weiss]

Looks like the same issue ... Case # 04986783
can I have the hotfix please?

[ittrend4710]

Same here...

...please inform if hotfix is available.

Best, Mike

[Mildur]

The hotfix is available.
Only from veeam support.

You need a paid license of course to get hotfixes.
Community edition has normally to wait for a new build.

[ittrend4710]

We've a paid license ... no problem, but I don't want to waste my time creating a case etc.

Date needed for public hotfix or new build...

Regards

[Mildur]

I had created one case for all my customers.
You can use the same hotfix for all customers.
Important is, that you have the newest vbo365 version (version 5.0.2.22) installed.

[xiffus]

We have also this problem: Case-Nr.04986836
Can I have the hotfix?

[Pagrossman]

Hello everyone,

We have the same issue on all our Veeam servers...

Case #04986963

[kristofpoppe]

Also here confirmation of the same problem on version 5.0.2.22
Case opened and waiting to receive hotfix.
Case #02463114

[nielsengelen]

For those affected, hotfixes are delivered via support. The hotfix for this specific issue is also available so opening a case is required for assistance. You can refer to this topic in the ticket.

[BrianD]

Fix applied and re-ran the backup job. Success with no warnings and failures - just in time so i can enjoy weekend

Nice one Veeam, great support guys.