“Failed to resolve team (ID: , name: ): Organization (ID: ) which the team (ID: ) belongs to not found” when performing Microsoft Teams backup
KB ID: | 4268 |
Product: | Veeam Backup for Microsoft Office 365 | 5.0 |
Published: | 2022-01-03 |
Last Modified: | 2022-01-07 |
Challenge
Starting January 1st, 2022 an incremental backup of Microsoft Teams objects may fail with the error:
Failed to resolve team (ID: {%id%}, name: {%name%}): Organization (ID: {%id%}) which the team (ID: %id%) belongs to not found
This issue affects customers who back up Microsoft Teams to Jet-based backup repositories since 2020.
Cause
The issue is caused by a mismatch in the Organization ID value that was created for Microsoft Teams in the backup repository database.
Solution
Hotfix Requirement
This hotfix requires Veeam Backup for Microsoft Office 365 build 5.0.3.1051.
If the currently installed build of Veeam Backup for Microsoft Office 365 is lower, you must upgrade before installing this hotfix.
Hotfix Installation
- Check that the installed version of Veeam Backup for Microsoft Office 365 is compatible with the hotfix.
- Stop all Backup Jobs
- End all active Restore sessions (if any)
- Stop the following Services on the Veeam Backup for Microsoft Office 365 server.
- Veeam Backup for Microsoft Office 365 Service
- Veeam Backup Proxy for Microsoft Office 365 Service
- Veeam Backup for Microsoft Office 365 RESTful API Service
- Download the private fix using the button in the More Information section below.
- Extract the contents of the ZIP file to the C:\Temp folder.
- Run the following cmdlet in Windows PowerShell using the Administrator mode to remove security locks:
Get-ChildItem -Path "C:\Temp" -Recurse -Force | Unblock-File
- On the Veeam Backup for Microsoft Office 365 server, back up the original DLLs and replace them with the ones from the Fix Pack in the following folders:
- C:\Program Files\Veeam\Backup365
- C:\Program Files\Veeam\Backup365\Packages\Proxy
- Start the services stopped on step 3.
- Upgrade the backup proxy servers using the Veeam Backup for Microsoft Office 365 console.
- Run a job that backs up Microsoft Teams data and check whether the issue persists.
If the issue persists after installing the hotfix, please collect log files and open a Veeam Support case.
More information
MD5: 4C3A51E2CE2C0BB5827C8322231B268D
SHA-1: 2A25996129364199E6E9F28B09DE94019986252B
SHA-1: 2A25996129364199E6E9F28B09DE94019986252B
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL +Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL +Enter.