1-800-691-1991 | 9am - 8pm ET
EN

Release Information for Veeam Backup for Microsoft Office 365 5c

KB ID: 4181
Product: Veeam Backup for Microsoft Office 365
Published: 2021-06-15
Last Modified: 2021-09-01

Requirements

Please confirm that you are running one of the following versions of Veeam Backup for Microsoft Office 365 before upgrading to 5c:

  • 3.0 (build 3.0.0.422)
  • 4.0 (build 4.0.0.1345)
  • 4a (builds 4.0.0.1553, 4.0.0.1580)
  • 4b (builds 4.0.0.2516, 4.0.0.2549)
  • 4c (builds 4.0.1.519, 4.0.1.531, 4.0.1.545, 4.0.1.612, 4.0.1.625)
  • 5.0 (builds 5.0.0.1061, 5.0.0.1063)
  • 5a (build 5.0.0.1070)
  • 5b (builds 5.0.1.179, 5.0.1.207, 5.0.1.225, 5.0.1.252)

You can check this under Help and Support > About in the Veeam Backup for Microsoft Office 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to 5.0.2.22.

IMPORTANT

Before you apply this update, be sure to review the ‘Upgrading Veeam Backup for Microsoft Office 365’ section of the Release Notes document.

For detailed information about this release, please refer to the Release Notes document.

What’s New

Resolved Issues

General

  • Under certain conditions Veeam Backup for Microsoft Office 365 console fails to open with “The added or subtracted value results in an un-representable DateTime” error recorded in the log file.
  • Retention job on a local JET-based backup repository fails with “Object reference not set to an instance of an object” if Contacts and Calendar folders are excluded from the retention policy.
  • Assigning a Veeam Backup for Microsoft Office 365 license to a backed-up user fails with “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key” error recorded in the log file if an organization type has been changed in the console from Microsoft Office 365 or On-premises to Hybrid.
  • Under certain conditions Exchange mailbox backup fails with “Unable to access repository (%path%) JetError -1303, JET_errTableDuplicate, Table already exists” error.

Backup

  • Teams backup fails with “Cannot parse page operation response” error. For more details, see KB4182.
  • Incremental backup of SharePoint data to a repository extended to object storage may stall if the site folder structure has been changed in a specific manner after the last backup job run.
  • Exchange backup fails with “The request failed with HTTP status 503: Service Unavailable” error, if the backed-up user account has an incorrect SMTP address in their EmailAddresses property.
  • Exchange archive mailbox backup may fail with the “Exchange Web Services error code: ErrorMailboxMoveInProgress” error.
  • Incremental backup of a personal SharePoint site may fail with a “401 Unauthorized” error if the user account has been migrated to another geolocation after the last backup job run.

Restore

  • Under certain conditions, file restore with Veeam Explorer for Microsoft OneDrive for business fails with the “Failed to find any users” error.
  • In Veeam Explorer for Microsoft Exchange operating via Veeam Cloud Connect, the “Compare to production” operation for public folder mailboxes fails with the “Failed to access mailbox. Mailbox does not exist” error.
  • Exploring Teams objects in Veeam Explorer for Microsoft Teams may fail with an “Object reference not set to an instance of an object” error.

Object Storage

  • Synchronization of a repository extended to S3 compatible object storage may fail with “Unrecognized GUID format” or “Incomplete commit found” errors.

More information

SHA-1:4733ca3605f0e256bf293f6e0916d27cf2e79972
MD5:8d517c0d3476100464b60f9722bb8919
KB ID: 4181
Product: Veeam Backup for Microsoft Office 365
Published: 2021-06-15
Last Modified: 2021-09-01

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.