#1 Global Leader in Data Resilience

Veeam Backup for Microsoft 365 5b cumulative patch KB4158

KB ID: 4158
Product: Veeam Backup for Microsoft Office 365 | 5.0
Published: 2021-05-11
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

Requirements

Please confirm you are running Veeam Backup for Microsoft 365 build 5.0.1.179, 5.0.1.207, or 5.0.1.225 prior to installing this cumulative patch KB4158. 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.1.252.

As a result of ongoing R&D effort and in response to customer feedback, cumulative patch KB4158 provides a set of enhancements and bug fixes, the most significant of which are listed below:

Enhancements

  • The default retention type when adding a new backup repository changed to Snapshot-based.
  • VMC logs truncation to free up space and avoid logs sprawl.

Resolved Issues

General

  • Backup data move job fails with the “Failed to allocate a managed memory buffer of 2147483647 bytes. The amount of available memory may be low” error.

Object storage repositories

  • Moving backup data to an object storage repository may fail with the “Failed to complete the remote task because the connection with the server was lost” error.
  • Retention type changes to item-level if a repository extended to object storage has been removed from Veeam Backup for Microsoft 365 console and then re-added back. This issue only affects repositories that were created with REST API or PowerShell, configured with the snapshot-based retention, and extended to object storage. For more details, see KB4176.
  • Moving SharePoint backup data to an object storage repository may stall.

Backup

  • Teams backup may fail with the “Resource does not exist” error.
  • In hybrid organizations, resolving an Exchange Online mailbox may fail with the “Failed to synchronize item changes in folder. SOAP header Action was not understood” error.
  • Backup job may fail to connect to an organization with “The remote server returned an error: (502) Bad Gateway” error received from Microsoft Graph.
  • Backup job that includes multiple Teams objects may stall or run very slow.

Restore

  • In Veeam Explorer for Microsoft Exchange, advanced search operation may fail with “The operation has timed out” error.
  • Restoring a deleted Team may fail with the “Property classification has an invalid value” error.

RESTful API

  • Saving a backed-up OneDrive account with REST API fails if the username contains the “|” character.
  • Saving Teams posts as MSG files with REST API may fail if multiple such requests are running concurrently.
  • Getting all items in a deleted list with the (GET) /v5/RestoreSessions/{restoreSessionId}/Organization/Sites/{siteId}/Items request fails with the “Object reference not set to an instance of an object” error.
  • REST API calls may fail with “This request operation sent to net.tcp://127.0.0.1:9193/%EndpointName% did not receive a reply within the configured timeout (00:01:00)” error.

Reporting

  • Generation of a Mailbox Protection report may fail with the “Object reference not set to an instance of an object” error if some of the mailboxes in the scope are missing the ExchangeGuid property.

Solution

To install the cumulative patch KB4158:

  1. Download VeeamBackupOffice365_5.0.1.252_KB4158.zip
  2. Execute VeeamBackupOffice365_5.0.1.252_KB4158.msp as administrator on the Veeam Backup for Microsoft 365 server.
  3. Execute VeeamExplorerForExchange_5.0.1.252_KB4158.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed.
  4. Execute VeeamExplorerForSharePoint_5.0.1.252_KB4158.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed.
  5. Execute VeeamExplorerForTeams_5.0.1.252_KB4158.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: 32423b5f5ae14cf8ac9eb2fe5255e4e4                                                                                                                                  
SHA-1:  
440de2c6bd53a8bb9718f3b232d059ce720a63a1
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.