- Veeam Support Knowledge Base
- Veeam Backup for Microsoft 365 5c cumulative patch KB4187
Veeam Backup for Microsoft 365 5c cumulative patch KB4187
| KB ID: | 4187 |
| Product: | Veeam Backup for Microsoft Office 365 | 5.0 |
| Published: | 2021-07-12 |
| Last Modified: | 2026-10-29 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Requirements
Please confirm you are running Veeam Backup for Microsoft 365 build 5.0.2.22 prior to installing this cumulative patch KB4187. You can check this under Help and Support > About in Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 5.0.2.42.
As a result of ongoing R&D effort and in response to customer feedback, cumulative patch KB4187 provides a set of bug fixes, the most significant of which are listed below:
Resolved Issues
General
- Under certain conditions a proxy may fail with the “Out of Memory” error during backup to an object storage repository.
Backup
- Microsoft Teams backup may fail with “Folder processing failed: Team Chat. Restriction contained too many elements” error.
- Backup of Team Chat messages created after October 2020 may fail with the “Failed to get TeamsMessagesData folder” error.
- Microsoft Teams backup fails with “Object reference not set to an instance of an object” error.
- OneDrive backup fails with “Object reference not set to an instance of an object” error if there’re any large OneNote files that are open and being edited during backup.
Restore
- In BaaS scenarios, exporting backup data to a local disk on the tenant side fails with the timeout error.
- Export operation in Veeam Explorer for Microsoft Exchange may fail with the “Connection to server was unexpectedly closed” error.
- For larger Office 365 organizations, some OneDrive accounts may not be displayed in the “Copy OneDrive” wizard
RESTful API
- SharePoint site title field is empty if such a site has been added to a backup job explicitly via REST API and the site title has not been explicitly specified.
- Removing a group with audit items via REST API doesn't work as expected but reports back response code 200.
- In BaaS scenarios with the modern app-only approach, obtaining a token for tenant authentication via REST API fails if a combination of capital and lower-case letters is used to specify the client_id parameter.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.