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

Veeam Backup for Microsoft Office 365 4a cumulative patch KB3089


Veeam Backup for Microsoft Office 365 4a cumulative patch KB3089. 


Please confirm you are running Veeam Backup for Microsoft Office 365 4a (build prior to installing this cumulative patch KB3089. You can check this under Help > About in Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 

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

Resolved Issues 

Object storage repositories

  • Configuring object storage consumption limit to more than 1TB in the product UI doesn’t apply these changes to the configuration database.  
  • Adding an S3 compatible object storage repository fails with the “Failed to request region for bucket %Bucket Name%, bucket skipped” error. 
  • Adding an Amazon S3 object storage repository with a bucket in the AWS GovCloud (US) region fails with the “The AWS Access Key Id you provided does not exist in our records” error. 
  • Object storage repository synchronization fails with the “JetError -1069, JET_errVersionStoreOutOfMemory, Version store out of memory” error. 
  • Repository upgrade fails with the “JetError -1311, JET_errTooManyOpenTables” error.  
  • Backup job fails with the “JetError -1311, JET_errTooManyOpenTables” error. 
  • Under certain conditions, moving existing SharePoint or OneDrive for Business backup data from a local to an object storage repository may fail with the “Unspecified Error”. 
  • Moving existing backup data from a local to an object storage repository fails with the “JetError -1101, JET_errOutOfSessions, Out of sessions” error. 
  • Adding or editing an object storage repository and selecting (or creating) a folder in the Amazon S3 bucket fails with the “Could not establish trust relationship for the SSL/TLS secure channel” error. For more details, see KB3095
  • Creating a folder in an S3 compatible object storage bucket fails with the “Unable to create folder (name: <folder_name>)” error. For more details, see KB3097


  • Working with Office 365 organizations using U.S. Government GCC High plans fails with the “ProtocolError - The remote server returned an error: (403) Forbidden” error. 
  • Adding Office 365 organizations using U.S. Government plans fails with the “Confidential Client is not supported in Cross Cloud request” error. 
  • Incremental backup jobs processing OneNote data fails with the “File not found in the database” error.  


  • Under certain conditions, backup to a repository extended with Amazon S3 or S3 compatible object storage or retention jobs applied to such repositories may fail with the “Specified argument was out of the range of valid values”. 
  • Backup to object storage repository fails with the “JetError -1069, JET_errVersionStoreOutOfMemory, Version store out of memory” error. 
  • Under certain conditions, Office 365 groups backup to a repository extended with object storage fails with the “This id is of the wrong type for this conversion operation” error. 
  • Adding users without a Display Name to a backup job fails with the “Value cannot be null. Parameter name: key” error. 
  • Backup job configured to exclude SharePoint sites with changed URLs completes with a warning. 
  • Incremental backup job ignores changes in OneDrive accounts URLs that may have occurred after the full backup job run. 
  • When editing a backup job, the “Personal sites” node remains available for selecting even if it has already been added to the same backup job. Likewise, individual personal sites remain available for selecting, even if the entire “Personal sites” node has already been added to the same backup job. 


  • Export to PST fails with "Unable to read beyond the end of the stream"
  • When exploring backup jobs configured with exclusions, Veeam Explorer for Microsoft SharePoint fails with the “Some backup data is not available” error. 


  • Under certain conditions, execution of the Get-VBOUsageData PowerShell cmdlet fails with the “Specified cast is not valid” error.  
  • An output of OneDrive data requested with the Get-VBOEntityData PowerShell cmdlet may be incorrect if the OneDrive account URL has been changed after the full backup job run. 


To install the cumulative patch KB3089: 
  1. Download VBO4a-KB3089.msp 
  2. Execute VBO4a-KB3089.msp as administrator on the Veeam Backup for Microsoft Office 365 server. 
If there are any remote proxies in your environment please update those as described here

NOTE: Veeam Backup for Microsoft Office 365 RESTful API Service will not be started automatically after the update. Please start it manually to continue using REST API. 

More information


MD5: 1b737c044fcc990a5bd8c324b42c9541
SHA-1: ca72a9c0c000a606e16faecb2f47d489b88c3518
Veeam Backup for Microsoft Office 365
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

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


error icon

Oops! Something went wrong.

Please go back try again later.