Skip to main content
  • EN

The new year starts very well...with a new problem in regards to Office 365 backup.

Since 01/01/2022 teams backup could fail with the following error:

Failed to process team: XYZ Organization (ID: XYZ) which the team (ID: XYZ) belongs to not found.

Veeam is aware of this problem and currently preparing a hotfix for this issue. If you want to be among the first to receive the fix, then open a support case. If you can wait, I will update this post as soon as the fix is publicly available.

For further information see the following R&D forums post:

https://forums.veeam.com/veeam-backup-for-office-365-f47/o365-backups-fail-since-1-1-2022-01-00-t78479.html#p439853

 

Update #1:

The Hotfix is now available via Support

The hotfix for the latest 5d CP2 (build 5.0.3.1051) has been provided to support.

Update #2:

The fix is now available through this KB; only for the latest VBO build at the moment (Thanks @JMeixner):

https://www.veeam.com/kb4268

Update #3:

The hotfix has been replaced with a cumulative patch. You need to be at version 5d build 5.0.3.1033 or higher to install this patch.

https://www.veeam.com/kb4270?ad=in-text-link

Thanks @regnor for sharing, 2022 definitely not start so well for Microsoft products...

Thanks @regnor for sharing, 2022 definitely not start so well for Microsoft products...

I have the feeling that these won’t be the last surprises we get this year...:neutral_face:

Update: The Hotfix is now available via Support

The hotfix for the latest 5d CP2 (build 5.0.3.1051) has been provided to support.

Thanks for sharing. Will keep this on the list in case.  Wonderful Microsoft 😂

Now there is a KB article published on this topic, too.

https://www.veeam.com/kb4268

Thanks @JMeixner! I’ve updated my post.

Probably the last update for this topic; today a new cumulative patch has been released which includes the hotfix: https://www.veeam.com/kb4270?ad=in-text-link

Thanks @regnor 

Will tell my team to test the upgrade and then rollout to all of our vbo servers 👍

Just updated again today: https://www.veeam.com/kb4270

Looks like this issue is back again.   Did anyone else have the same problem for backups done 1-1-2024?

 

 

Have not seen this yet but will keep an eye out. The KB is for the older v5 so hopefully there will be something for the newer v7.

@scoutman75 So far I haven’t seen any issues. Are you on the latest VB365 build (https://www.veeam.com/kb4106)? If so, could you please open a case with our support and let them check your issue?

 

I am running v6.0.0.367  I will open a case.

 

I am running v6.0.0.367  I will open a case.

 

That is GA for v6 so why have you not patched to latest v6 as per the link Regnor posted or even upgraded to v7?  That could be the issue and patching to latest v6 I would highly recommend before opening a case.

ok i ran the update but it kept telling me i was running the latest version.  I am upgrading to v7 now.

ok i ran the update but it kept telling me i was running the latest version.  I am upgrading to v7 now.

Ok let us know how it goes after the upgrade to the latest release of v7.  You can upgrade to v7a from your version as noted here - Upgrading Veeam Backup for Microsoft 365 - Veeam Backup for Microsoft 365 Guide

I’ve got 2 instances running on version 6.0.0.385 and I’ve got the same issue showing back up. Going to try upgrading to v7 

I’ve got 2 instances running on version 6.0.0.385 and I’ve got the same issue showing back up. Going to try upgrading to v7 

This should help address the issue.  Keep us posted once updated.

Comment


Terms & Conditions