Veeam.Archiver.Service terminates due to 'System.OutOfMemoryException' after updating to Veeam Backup for Microsoft 365 7.0.0.3968

KB ID: 4481
Product: Veeam Backup for Microsoft 365 | 7.0
Published: 2023-08-04
Last Modified: 2023-08-04
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.

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.

Challenge

Veeam.Archiver.Service consumes all available virtual memory and then terminates.

The issue can be confirmed with the following Windows Events (System log):

The Veeam Backup for Microsoft 365 Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

Cause

Veeam Backup for Microsoft 365 7.0.0.3968 has been impacted with an issue on the server relating to the use of the Exchange Online PowerShell module leveraged in some service operations. 

Solution

Currently Veeam is working closely with Microsoft Support to review the behavior. For the meantime, if you are affected by this issue, it is recommended to revert to the previous version of Veeam Backup for Microsoft 365. This Knowledge Base article will be updated as the investigation between Veeam and Microsoft presents new information.

Downgrade to build 7.0.0.3604 by completing the following steps:

  1. Navigate to Control Panel and select "Uninstall a program" option
  2. Uninstall Veeam Backup for Microsoft 365. This operation will not require the reconfiguration of the backup infrastructure, as the configuration databases will remain after the uninstallation.
  3. Download version 7.0.0.3604 installer.
  4. Mount installer ISO on Veeam server and install Veeam Backup for Microsoft365 from it.
  5. Upgrade all remote proxies

More Information

Report bugs and issues for the Exchange Online PowerShell module https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps

Frequent use of the Connect-ExchangeOnline and Disconnect-ExchangeOnline cmdlets in a single PowerShell session or script might lead to a memory leak. The best way to avoid this issue is to use the CommandName parameter on the Connect-ExchangeOnline cmdlet to limit the cmdlets that are used in the session.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.