Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
This Cumulative Patch can be used to:
After installing the Cumulative Patch, the Veeam Backup for Microsoft 365 build number will be 7.0.0.3604 P20230512.
Below are details about each of the Cumulative Patches that have been released for Veeam Backup for Microsoft 365 7.
Each subsequent Cumulative Patch also includes all fixes present in the previous Cumulative Patches.
Please, be advised that Veeam Backup for Microsoft 365 7 P20230704 (7.0.0.3968) has been retracted due to an issue relating to the use of Connect-ExchangeOnline and Disconnect-ExchangeOnline cmdlets that were leveraged in some service operations.
This issue is under investigation and will be resolved soon.
If you have already deployed P20230704 (7.0.0.3968) and have observed no issues, there are no additional actions to be taken at this time. If you have any questions or experience memory allocation issues after deploying the cumulative patch (P20230704 (7.0.0.3968)), we urge you to revert to the previous version of Veeam Backup for Microsoft 365 - KB4481.
General
Write lock may not be acquired with read lock held. This pattern is prone to deadlocks.
SQLite Error 19: 'UNIQUE constraint failed: GroupMembers.GroupInternalAccountId, GroupMembers.MemberInternalAccountId'.
Backup and Backup Copy
SharePoint Foundation is not the owner of this file.
An item with the same key has already been added.
Index was outside the bounds of the array.
Download request retry timeout exceeded.
Object reference not set to an instance of an object.
UnknownError
Object reference not set to an instance of an object
The remote server returned an error: (404) Not Found.
Mailbox does not have a valid Microsoft 365 license, a subsequent job retry also performs an attempt to resolve users without a valid Microsoft 365 license and completes with a warning state.
1605, JET_errKeyDuplicate, Illegal duplicate key.
Restore
Failed to convert field: Service (value: %value%, type: LookupMulti). The field was skipped.
The value 98634 must be in the range from 0 to 98633. Parameter name: value.
-1605, JET_errKeyDuplicate, Illegal duplicate key.
Restore Portal
REST APIs
500 Internal Server
PowerShell
Cannot access a disposed object.
Integration
General
Write lock may not be acquired with read lock held. This pattern is prone to deadlocks.
Backup
On incremental OneDrive and SharePoint backup job runs, new items may be skipped from a backup if, between backup job runs, a large number of items or folders were added/created in the source and then deleted in bulk.
For more information, review: KB4447REST APIs
The (GET) v7/Jobs request returns an incorrect value for the "lastRun" parameter.
The (GET) v7/Jobs request doesn’t return the "lastBackup" parameter for backup jobs that have finished with warnings.
General
Veeam Backup for Microsoft 365 7 writes successful authorization attempts to the Microsoft Windows event log every second, flooding the log with 4904/4905 security events.
Backup
Failed to process site: %name% (%site URL%). The remote server returned an error: (429).For more information, review KB4442.
JetError -1605 pattern cannot be determined
A Microsoft Teams backup job may fail on processing team tabs with the error:
Object reference not set to an instance of an object.For more information, review: KB4201
The remote server returned an error: (401) Unauthorized. SharePoint Loop app is currently available in Preview, and sites that it creates are unsupported and will be skipped from processing.This cumulative patch does not add support for sites created by Loop; it allows Veeam Backup for Microsoft 365 jobs to skip such sites silently.
REST APIs
Object reference not set to an instance of an object.
Object reference not set to an instance of an object.
Mailbox does not have a valid Microsoft 365 licenseThese warnings were suppressed in Veeam Backup for Microsoft 365 v6a P20221215 (build 6.1.0.438). However, upon additional observation and testing after the release of that cumulative patch, we have identified some edge cases where the fix may not help. Starting with Veeam Backup for Microsoft 365 v7 (build 7.0.0.2911), the suppression of the warning was rolled back.
To manually update an existing Veeam Backup for Microsoft 365 7.x deployment to the latest Cumulative Patch listed on this page, follow the same steps as upgrading Veeam Backup for Microsoft 365.
Your feedback has been received and will be reviewed.
Please try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.