#1 Global Leader in Data Resilience

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: 2021-10-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please, try again later.

This update has been superseded by Veeam Backup for Microsoft 365 5d.

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:

  1. Download VeeamBackupOffice365_5.0.2.42_KB4187.zip
  2. Execute VeeamBackupOffice365_5.0.2.42_KB4187.msp as administrator on the Veeam Backup for Microsoft 365 server.
  3. Execute VeeamExplorerForExchange_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed.
  4. Execute VeeamExplorerForSharePoint_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed.
  5. 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.

MD5: 546BD6F775F46C5E3A930B320719EE0B                                                                                                                                 
SHA-1:  E17B67AFBEA518CE686B81F75F36EFE02040CE1D
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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.