Failed to process team: <team name> UnknownError. The remote server returned an error: (410

[dali@iae.nl]

Before creating a case we get some errors at type Teams and Teams posts:
Type: Teams
Failed to process team: <Team name>. UnknownError. The remote server returned an error: (410) Gone.
Type: Team posts
<Team name> Error 7:02:08 AM 7:02:09 AM 0 0 B Processing team posts <Team name> failed with error: UnknownError. The remote server returned an error: (410) Gone.

Is there already any information how to investigate this errors?

[Mildur]

Hi Li

I see similar support cases where a hotfix was provided.
Please open a support case and provide them with your log files. If you face the same issue, our support team will provide you with the hotfix. Don't forget to share the case number with us here.

Best,
Fabian

[dali@iae.nl]

Case #05866285 : The remote server returned an error: (410) Gone.

[dali@iae.nl]

Now got a fix. See tomorrow if that works.

[Mike Resseler]

Let us know if it fixed the issue. By the way, what version are you on? And what patch level?

[dali@iae.nl]

Fix solved the issue: File_05732410_13c4564a7c
Veeam.Graph.Teams.dll

[sdv]

Issue also fixed in Veeam O365 V7.0.0.2911

Here's our timeline of the same issue;
[2022 Mid-Augustus] #05586974 opened Veeam case about Teams site failed with 410 gone. Veeam points to Microsoft due to bug in Microsoft's API.
[2022 - End of august] Opened a case with Microsoft 32566353 and after months of troubleshooting MS admits it is a bug in the API (februay 2023 !!!)
[2023 March] We've upgraded Veeam O365 6.1.0.438 -> 7.0.0.2911. Issue is fixed.
[2023 March] #05926830 opened a new Veeam case and point to the one in Mid-augustus and confirmed the issue was at Veeam's end which has been fixed with version 7.

I'm still confused wether or not it is a MS API bug or a Veeam bug and to why it was taking so long.
Perhaps a different api call was made available by MS for the backup software to use?
I can't seem to find this fix in release notes.

[Mike Resseler]

Hmmm, we were aware that there was an issue and it was fixed on their end. But it should not cause any issues anymore in the previous version also. I will need to investigate whether this is still a problem on the previous version.

Thanks for letting me know