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

Microsoft Teams backup fails with the error: Error: Cannot parse page operation response

KB ID: 4182
Product: Veeam Backup for Microsoft Office 365 | 5.0
Published: 2021-06-17
Last Modified: 2021-06-30
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

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

Backup of Microsoft Teams in Veeam Backup for Microsoft Office 365 fails with the following error:
 Error: Cannot parse page operation response.

Cause

This issue is related to recent changes made by Microsoft to the GUID format of certain Microsoft Teams components. These changes affect the logic that Veeam Backup for Microsoft Office 365 uses to process Microsoft Teams tabs. 

Solution

Hotfix Version Compatbility

The hotfix for this issue was created only for Veeam Backup for Microsoft Office 365 builds 5.0.1.225 or 5.0.1.252.

If the currently installed build of Veeam Backup for Microsoft Office 365 is lower, you must upgrade before installing this hotfix.

Hotfix Installation

  1. Stop all Backup Jobs

  2. End all active Restore sessions (if any)

  3. Stop the following Services on the Veeam Backup for Microsoft Office 365 server.
    • Veeam Backup for Microsoft Office 365 Service
    • Veeam Backup Proxy for Microsoft Office 365 Service
    • Veeam Backup for Microsoft Office 365 RESTful API Service

  4. Download the private fix using the button in the More Information section below.

  5. Extract the contents of the ZIP file to the C:\Temp folder.

    Note: The ZIP contains two folders; each is named after the version for which the hotfix is built.

  6. Run the following cmdlet in Windows PowerShell using the Administrator mode to remove security locks:

    Get-ChildItem -Path "C:\Temp\<hotfix_folder>\Veeam.Graph.Teams.dll" -Recurse -Force | Unblock-File

  7. On the Veeam Backup for Microsoft Office 365 controller server, find the original Veeam.Graph.Teams.dll in each of the folders listed below.  Rename the original, or move it to another folder,  then copy the Veeam.Graph.Teams.dll from the Hotfix folder for the installed build of Veeam Backup for Microsoft Office 365
    • C:\Program Files\Veeam\Backup365
    • C:\Program Files\Veeam\Backup365\Packages\Proxy
    • C:\Program Files\Veeam\Backup and Replication\Explorers\Teams

  8. Start the services stopped in 3

  9. Upgrade the backup proxy servers using the Veeam Backup for Microsoft Office 365 console.

  10. Run a job that backs up Microsoft Teams data and check whether the issue persists.

 

If the issue persists after installing the hotfix, please collect log files and open a Veeam Support case.

More Information

MD5: 252FF3D5E4F6D9EFE1DE52001F91CE03
SHA-1: BAF94D7F3981653A569933107472FBE8EA8DCF94
Click here to send feedback regarding this KB, or suggest content for a new KB.
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.

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 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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.