#1 Global Leader in Data Protection & Ransomware Recovery

Exchange Backup Fails With: "Failed to get folder properties. Not allowed to access Non IPM folder"

KB ID: 4569
Product: Veeam Backup for Microsoft 365
Published: 2024-04-03
Last Modified: 2024-04-09
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.

Resolution Version Requirement

This issue affects all versions of Veeam Backup for Microsoft 365, however, a solution is only available for the following versions:

  • Veeam Backup for Microsoft 365 6a P20230322 (build 6.1.0.1015)
  • Veeam Backup for Microsoft 365 7 (builds 7.0.0.2911 - 7.0.0.4901)
  • Veeam Backup for Microsoft 365 7a (builds 7.1.0.1301 - 7.1.0.1501)
Veeam Data Cloud for Microsoft 365 Customers
Customers utilizing Veeam Data Cloud for Microsoft 365, please be advised that no actions are required to address this issue. All the necessary actions were implemented in the Veeam Data Cloud backend on 2024-04-04, and upcoming tasks will be completed without issue.

Challenge

A backup job in Veeam Backup for Microsoft 365 processing Exchange data fails with the error:

Failed to get folder properties. Not allowed to access Non IPM folder

Cause

During Exchange backup, Veeam Backup for Microsoft 365 requests the properties of all mailbox folders, including the properties of hidden and legacy folders (e.g., ‘TeamsMessagesData’).

Due to a recent change in Microsoft 365, the properties of the ‘TeamsMessagesData’ folder cannot be retrieved using the EWS API, which is used by Veeam Backup for Microsoft 365 to process Exchange data backup.

Solution

To resolve this issue, Veeam Backup for Microsoft 365 must be configured to skip processing the ‘TeamsMessagesData’ folder.

There are three options to achieve this, choose only one:
All three options have the same effect: the TeamsMessagesData folder will be skipped during the Exchange data backup.

  • Option 1: PowerShell Script to Automate Modification of the Config.xml file. — (Recommended Solution)
    The new fully automated and recommended solution.
  • Option 2Manually modify the Config.xml file to enable a setting that causes the folder to be skipped.
    The original hands-on solution that was provided by this article.
  • Option 3: Install a hotfix to change the software default behavior to skip the folder.
    While modification of the Config.xml is the simplest and best solution, we understand that some customers may not wish to make configuration modifications or be able to access PowerShell. For those customers, a hotfix has been made available for build 7.1.0.1501 that will modify the default hardcoded value of the SkipTeamsMessagesDataFolders setting from False to True. Essentially, doing the same thing as the Config.xml setting, but at the program code level.
Config.xml Setting - Version Requirement

While this error can occur when using any version of Veeam Backup for Microsoft 365, this solution, wherein a setting is added to the Config.xml file, requires that at least Veeam Backup for Microsoft 365 build 6.1.0.1015.

This solution works for the following versions:

  • Veeam Backup for Microsoft 365 6a P20230322 (build 6.1.0.1015)
  • Veeam Backup for Microsoft 365 7 (builds 7.0.0.2911 - 7.0.0.4901)
  • Veeam Backup for Microsoft 365 7a (builds 7.1.0.1301 - 7.1.0.1501)

If a build of Veeam Backup for Microsoft 365 older than 6.1.0.1015 is presently installed, you must first upgrade Veeam Backup for Microsoft 365 prior to implementing the solution documented in this article. In such a scenario, rather than upgrading an older deployment to 6.1.0.1015, we suggest upgrading to the latest version of Veeam Backup for Microsoft 365 since version 6 is no longer supported.

Option 1: PowerShell Script to Update Config.xml — Recommended Option

The script below was created by Veeam and is provided as a courtesy to expedite the resolution of this issue. Note, however, that if any problems occur with the script, Veeam Support will recommend implementing one of the other solutions.

  1. Execute the following PowerShell script as Administrator on the Veeam Backup for Microsoft 365 server:

    Note: Any active Restore Session(s) will be halted when this script restarts the Veeam Backup for Microsoft 365 Service service. Backup jobs should not be affected because running jobs are managed by the Veeam Backup Proxy for Microsoft 365 Service service, which is not restarted by this script. After the Veeam Backup for Microsoft 365 Console is launched, the status of running jobs may take a moment to update.
$configFilePath = "C:\ProgramData\Veeam\Backup365\Config.xml"
$xmlContent = [xml](Get-Content $configFilePath)
if ($xmlContent.SelectSingleNode("//Archiver/Proxy[@SkipTeamsMessagesDataFolders='True']")) {
Write-Output "SkipTeamsMessagesDataFolders setting already exists. No changes made."
} else {
Copy-Item -Path $configFilePath -Destination "$configFilePath$($(Get-Date -Format '.yyyyMMdd')).old"
$newElement = $xmlContent.CreateElement("Proxy")
$newElement.SetAttribute("SkipTeamsMessagesDataFolders", "True")
$archiverNode = $xmlContent.SelectSingleNode("//Archiver")
$archiverNode.AppendChild($newElement)
$xmlContent.Save($configFilePath)
Write-Output "SkipTeamsMessagesDataFolders setting added."
Restart-Service -Name "Veeam.Archiver.Service"
}
  1. Retry the job(s).

Option 2: Manually Update Config.xml

  1. Update the Config.xml file to skip the TeamsMessagesData folder.
    Only the config.xml file on the main Veeam Backup for Microsoft 365 server needs to be updated.
    1. Open the folder: C:\ProgramData\Veeam\Backup365\
      The ProgramData folder is hidden by default. Copy and paste the folder path into the Explorer address bar.
    2. Within that folder, create a copy of Config.xml with the extension .old (i.e., Config.xml.old).
      If the Config.xml file is not present, double-check the folder path (i.e., ProgramData not Program Files).
    3. Launch NotePad as an Administrator, and open C:\ProgramData\Veeam\Backup365\Config.xml
    4. Add the following line withinAnywhere below and above . the <Archiver> section and save the file.
    <Proxy SkipTeamsMessagesDataFolders="True" />
Example
Example
  1. Restart the Veeam Backup for Microsoft 365 Service service.
    Note: Restarting the Veeam Backup for Microsoft 365 Service will cause any active Restore Session to halt. Active backup jobs should not be affected because once they are started, they are managed by the Veeam Backup Proxy for Microsoft 365 Service service, which does not need to be restarted. After the Veeam Backup for Microsoft 365 Console is launched, the status of running jobs may take a moment to update.
  2. Retry the job(s).

Option 3: Install Hotfix to Change Default Handling of TeamsMessagesData Folder

This option is only recommended if no other hotfixes have been installed.

  1. Ensure you are running Veeam Backup for Microsoft 365 7a P20240123 (build 7.1.0.1501)
    No hotfix is planned for version 6 or 5, as they reached End of Fix on 2023-03-01 and 2022-04-01, respectively.
  2. Ensure that there are no Backup jobs or Restore sessions running.
  3. On the Veeam Backup for Microsoft 365 server, stop the following services:
    • Veeam Backup for Microsoft 365
    • Veeam Backup Proxy for Microsoft 365
  4. Download the hotfix.
Download Hotfix

Filename: kb4569.zip
MD5:  205249BE95BE7479DA155ED70A54CDE7
SHA-1: 67D67618A3338B7B22A0858A8B39CFE5A13F9C1B

  1. Extract the fix to: C:\Temp\KB4569\
  2. After extraction, unblock the files using the following PowerShell cmdlet:
Get-ChildItem -Path "C:\Temp\KB4569\" -Recurse -Force | Unblock-File
  1. Backup the original DLL and replace it with the one from the fix in the following locations:
    • C:\Program Files\Veeam\Backup365\Veeam.Archiver.Controller.dll
    • C:\Program Files\Veeam\Backup365\Veeam.Exchange.Interfaces.dll
  2. Start the services that were stopped in Step 3.
  3. Retry the jobs.
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.