Operational Defect Database
BugZero found this defect 1043 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4187
Veeam Backup for Microsoft 365 5c cumulative patch KB4187
Last update date:
10/13/2021
Affected products:
Veeam Backup for Microsoft 365
Affected releases:
5.0
Fixed releases:
No fixed releases provided.
Description:
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.
Solution
To install the cumulative patch KB4187: Download VeeamBackupOffice365_5.0.2.42_KB4187.zip Execute VeeamBackupOffice365_5.0.2.42_KB4187.msp as administrator on the Veeam Backup for Microsoft 365 server. Execute VeeamExplorerForExchange_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed. Execute VeeamExplorerForSharePoint_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed. Execute VeeamExplorerForTeams_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft Teams is installed. If there are any remote proxies in your environment, please update those as described here.
