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

[VNR-LF]

started seeing this issue last night, will open a ticket. thanks for keeping us updated!

[frisco]

Any status updates? Have a ticket 04986024 opened yesterday midday and got put on Hold status and would be updated when hotfix is ready. Forum members are indicating they've already received and applied the hotfix but I still haven't heard anything.

[Polina]

Hi Matt,

The hotfix is now delivered to customers depending on their current build and previous fixes installed. Both R&D and support teams are doing their best to resolve the issue for all of the affected customers. You will be notified immediately when the fix for your VBO environment is available.

Hope for your understanding.

[karsten123]

Case #04987005

hotfix applied. problem solved. perfect.

thx

[frisco]

Same! Hotfix applied and problem solved. Thanks

[senchin]

I am still waiting for support to send me the hotfix even after having a case open for a few days. Anyone else still waiting? I find it interesting that I am learning of the fix here rather than support notifying me that it is available.

[ajriek1970]

The hotfix is out and I just applied it to our internal and customer facing VBO. Both are fixed and working again.

[Gostev]

I am still waiting for support to send me the hotfix even after having a case open for a few days. Anyone else still waiting? I find it interesting that I am learning of the fix here rather than support notifying me that it is available.

Please note that pilot hotfixes are not meant for wide distribution, but rather to confirm on a few installations that they solve the issue. They are then re-built correctly (as pilot modules have debug configuration enabled and are not even signed) and only then distributed to all affected customers by support engineers and via a KB article. Thanks!

[cerberus]

Confirmed the hotfix is now working for us as well.

[popjls]

Same issue here, have opened a ticket: #02369041

[petr.nikitin]

You may find publicly available hotfix here:
https://www.veeam.com/kb4201

[tim.palmer]

Looks like there's a KB available for public accessibility

https://www.veeam.com/kb4201

[Mildur]

Petr has posted this already two days ago

[dasfliege]

Since applying the hotfix, i receive the following error. Anyone else had the same issue?

Failed to process team: xxxxxxx. Method not found: 'Void Veeam.Graph.Teams.Loaders.TeamAppLoader..ctor(Veeam.Graph.IGraphRequestExecutor)'.

[Polina]

@dasfliege

Please make sure you applied the fix correctly. Most likely, some of the required dll files were not updated.

[bpaquin]

Got the hotfix, fixed the issue, thank you !

[jimmyhurr]

Hot fix applied here also, and this fixed it.

Many thanks.

[mwilliams7247]

Sounds great that there is a hotfix for this, but how does one obtain that if they are on the "trial/free" (Less than 10 user) licenses?

I demo this in my lab for customers and it would be great to show them it working error free...

[Andreas Neufert]

You can download it here: https://www.veeam.com/kb4201

[btownsen]

We upgraded our site today to 5.0.2.22 and applied the updates in KB4187 (linked in KB4201) and show now as on 5.0.2.42 but we are still seeing this error. Did I miss something?

[Gostev]

Sounds like it. Did you open a support case?

[btownsen]

Yes sir 04999331

[btownsen]

Ok, face the music moment. We upgraded the proxies after install the 5.02.22 update but when I glanced after the patch there was no out of date message on them so I moved on. After working with support I took a better look and noticed the version difference. I upgraded the proxies now everything is working properly.

[wayne7215]

Strange, are we the only one who faces the issue from last August again since 2 days? We get now the error "Object reference not set to an instance of an object." even with 5.0.3.1051.
Was the fix not implemented into KB4235?

[Dima P.]

Hello wayne7215,

The fixes from older versions are automatically inherited by the latest product releases. If you confirm that all components are up to date, please raise a support case and share the case id with us. Thank you!

[wayne7215]

Hi Dima

The case ID 05213910

Thx

[wayne7215]

Just an update, support suggested to create a new backup job for the problematic site we got the error to generate a new token. New job was running successfully and afterwards also the old job is running without any error.
So it was not related to the hotfix, the Object reference not set to an instance of an object error is very broad.

[Johnny L]

@Wayne7215

My goto-solution for isolated issues (weird issues with a single site, mailbox etc) is to:
1) Exclude the item from the original job
2) Create a new job for the problematic item using the original proxy and repository.
3) Get-VBOJob -Name "NameOfNewJob" | Start-VBOJob -RunAsSync -Full

This is often the solution from Support either way, so I just do it before doing anything else.

"Something" has changed from Veeam or Microsoft, so I usually need do this a couple of times each week on different organizations (we're an MSP)..