Operational Defect Database
BugZero found this defect 1070 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4181
Release Information for Veeam Backup for Microsoft 365 5c
Last update date:
1/28/2022
Affected products:
Veeam Backup for Microsoft 365
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Requirements
Please confirm that you are running one of the following versions of Veeam Backup for Microsoft 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 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to 5.0.2.22.
What’s New
Support to install on top of Veeam Backup & Replication 10a Cumulative Patch P20210609.
Resolved Issues
General Under certain conditions Veeam Backup for Microsoft 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 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. 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
This update has been superseded by Veeam Backup for Microsoft 365 5d.
