#1 Global Leader in Data Resilience

Veeam Backup for Microsoft 365 4c cumulative patch KB4099

KB ID: 4099
Product: Veeam Backup for Microsoft Office 365 | 4.0
Published: 2021-02-11
Last Modified: 2021-02-16
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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.

Requirements

Please confirm you are running Veeam Backup for Microsoft 365 version 4c (builds 4.0.1.531, 4.0.1.545, 4.0.1.612) prior to installing this cumulative patch KB4099. You can check this under Help and Support > About in Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 4.0.1.625.

Cumulative patch KB4099 addresses the data loss issue described in the KB4103 and includes a set of other fixes, the most significant of which are listed below:

Resolved Issues

  • Under certain conditions retention policy mistakenly cleans actual Exchange backup data from Jet-based repositories set with snapshot-based retention of less than 2 years.
  • For SharePoint backup, creation of the new 2021 repository database triggers full synchronization instead of incremental backup on the next backup job run.
  • SharePoint and OneDrive backup may fail with “(500) Internal Server error” or “(400) Bad Request” error.
  • Archive mailbox backup may fail with “Failed to access archived message folder root. SOAP header Action was not understood” error.
  • SharePoint backup may fail with “Invalid MIME content-length header encountered on read” error.
  • List items restore may fail with “Cannot find corresponding Content-Type for: %version%. Original ContentTypeID” error.
  • Executing the Export-VEXItem cmdlet may fail with “Method not found” error.

Solution

To install the cumulative patch KB4099:

  1. Download VeeamBackupOffice365_4.0.1.625_KB4099.zip
  2. Execute VeeamBackupOffice365_4.0.1.625_KB4099.msp as administrator on the Veeam Backup for Microsoft 365 server.
  3. Execute VeeamExplorerForExchange_4.0.1.625_KB4099.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed.
  4. Execute VeeamExplorerForSharePoint_4.0.1.625_KB4099.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed.

If there are any remote proxies in your environment, please update those as described here.

MD5: eff8bfe1603080f1e64bdac7fdfc94ea
SHA-1: d0f7174c57e237c6cf4ac7a2cc69ae0cc98dc298
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.