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

[ReKe]

Switching to Teams Export APIs does not help with the current 'non IPM' issue. To be honest, I wonder where this suggestion has come from, because it doesn't make much sense. The new APIs are used to back up messages in Teams, while the current issue occurs during Exchange mailbox backup.

@Polina

Please make sure that your support doesn't send out mails with the number one solution to activate Teams Export APIs, a complete day after your post.

I got this answer right now (Case 07207623).

The solution for us was to edit the Config.xml

[Gostev]

The official Support KB about this issue (see the first post of this topic) does not require activatig Teams Export APIs.

[ReKe]

@Gostev

That's clear. But why your support still mention it in actual ticket replys as number one solution for this issue?

[MONJEM]

Good ol' Microsoft strike again with changing something that causes major issues that then wastes a lot of time for IT admins, I have 4 tenants with this issue but at least Windows 11 looks pretty !!!

[Gostev]

But why your support still mention it in actual ticket replys as number one solution for this issue?

I would expect this recommendation to depend on whether or not the particular customer is backing up Teams. Because without doing this, their Teams will no longer work due to the same change that caused the whole issue.

[ReKe]

No mention about Teams Backups in the reply.

There are two possible ways to address this issue.
1) Enabling Veeam Backup for Microsoft 365 to backup Teams public channel posts using the Teams Export APIs.

The second one is how to edit the Config.xml.

[tpayton]

https://www.veeam.com/kb4569 has been updated to clarify version requirements and deployment instructions.

Some critical points based on KB feedback that has been received:

• The minimum compatible version for this solution is Veeam Backup for Microsoft 365 6a (build 6.1.0.1015).

• Customers using Veeam Data Cloud for Microsoft 365 do not need to take any actions; the solution was implemented today.

• Only the C:\ProgramData\Veeam\Backup365\Config.xml file on the primary Veeam Backup for Microsoft 365 server needs to be updated. No changes are required on proxies.

• Some customers reported that they could not find the Config.xml file. Those customers appear to have navigated to the wrong folder (i.e., C:\Program Files\Veeam\Backup365 instead of C:\ProgramData\Veeam\Backup365\).

• Some customers reported that changes to the Config.xml file were reverted after they started the services. After further review, this was determined to be caused by a misunderstanding in which the customer caused the Config.xml file to become invalid by deleting other lines in the Config.xml file. If the Veeam Backup for Microsoft 365 Service determines that the Config.xml contents are invalid, it recreates the Config.xml file.

[Wall86]

Powershell script. Used this for applying the XML Fix across 80+ Veeam 365 deployments

Code: Select all

[xml]$xml = Get-Content "C:\ProgramData\Veeam\Backup365\Config.xml"

if ($xml.Veeam.Archiver.Proxy -eq $null) {
    Copy-Item "C:\ProgramData\Veeam\Backup365\Config.xml" "C:\Temp\Config.xml" -ErrorAction SilentlyContinue
    $proxy = $xml.CreateElement("Proxy")
    $proxy.SetAttribute("SkipTeamsMessagesDataFolders", "True")
    $xml.Veeam.Archiver.AppendChild($proxy)
    $xml.Save("C:\ProgramData\Veeam\Backup365\Config.xml")    
    Restart-Service -Name Veeam.Archiver.Proxy -ErrorAction SilentlyContinue
    Restart-Service -Name Veeam.Archiver.Service -ErrorAction SilentlyContinue
}

[Polina]

@ReKe
Noted; thanks for letting me know.

[brendan]

had this issue overnight, applied kb4569 and it looks like it's now working again

big thumbs up to the Veeam staff
generally pretty quick to respond to issues like this, and actively responding to stuff in their forums. the 'How to/install' guides are top notch as well - so much better than the other software vendors we use

[VNR-LF]

https://www.veeam.com/kb4569 has been updated to clarify version requirements and deployment instructions.

Some critical points based on KB feedback that has been received:

• The minimum compatible version for this solution is Veeam Backup for Microsoft 365 6a (build 6.1.0.1015).

• Customers using Veeam Data Cloud for Microsoft 365 do not need to take any actions; the solution was implemented today.

• Only the C:\ProgramData\Veeam\Backup365\Config.xml file on the primary Veeam Backup for Microsoft 365 server needs to be updated. No changes are required on proxies.

• Some customers reported that they could not find the Config.xml file. Those customers appear to have navigated to the wrong folder (i.e., C:\Program Files\Veeam\Backup365 instead of C:\ProgramData\Veeam\Backup365\).

• Some customers reported that changes to the Config.xml file were reverted after they started the services. After further review, this was determined to be caused by a misunderstanding in which the customer caused the Config.xml file to become invalid by deleting other lines in the Config.xml file. If the Veeam Backup for Microsoft 365 Service determines that the Config.xml contents are invalid, it recreates the Config.xml file.

isn't it also necessary to upgrade the remote proxies (if any) after restarting the services?

[mjr.epicfail]

tpayton wrote: ↑Apr 04, 2024 8:17 pm

isn't it also necessary to upgrade the remote proxies (if any) after restarting the services?

No, just the config on the main server.

[VNR-LF]

ok, thanks. i can confirm the workaround fixed the issue for me as well. and i'd like to chime in: big thumps up to the veeam staff for the quick workaround

[Polina]

Thanks to ALL for sharing the positive feedback. Let's hope that one day issues with such a massive impact will become predictable and we can address them in advance.

[kaffeine]

I can confirm that the workaround worked for us as well.

[johnbo]

The workaround does work and its easy..

[tpayton]

Happy Friday! https://www.veeam.com/kb4569 has been updated again!

There are now three options to resolve the issue:

1. A PowerShell script to automate the modification of the Config.xml file. — [Recommended Solution]
2. The original manual Config.xml modification procedure.
3. A hotfix for build 7.1.0.1501 that resolves the issue by changing the default SkipTeamsMessagesDataFolders setting state within the dll itself.
   This option should only be used if no other hotfixes have been installed.

In the end, all three of these options do the exact same thing: they change the SkipTeamsMessagesDataFolders setting to True.

Other improvements worthy of note:

• The notice box at the top of the article is more explicit about which versions accept the setting change in the Config.xml file.
• After further review, we've determined that the Config.xml edit procedure does not require stopping jobs or the Veeam Backup Proxy for Microsoft 365 Service.

[ITP-Stan]

The fix works fine for me.

Make sure you are on V7. --> Note that the upgrade mechanism for older versions doesn't always find newer versions, use the site to download the latest!
Stop the 2 services.
Open the Config.xml file using administrator rights, I like to use Notepad++ who will automatically elevate itself to save such a file.
Add the line after the <Archiver> tag or before the </Archiver> tag.
Note the difference with the /, it's important to put the line in the correct place.
Start the 2 services, backup should work fine now.

Below are clear instructions:

1. Stop the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
2. Go to: C:\ProgramData\Veeam\Backup365
3. Make a copy of the Config.xml file
4. Edit the Config.xml file
5. Add

Code: Select all

<Proxy SkipTeamsMessagesDataFolders="True" />

right before the </Archiver> tag
6. Start the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
7. If you have multiple Proxies; Open the Veeam Backup for Microsoft365 Console -> Go to Backup Infrastructure -> Backup Proxies -> Right Click on the other proxies -> Click Upgrade.
7.1 In the step for the credentials make sure to use: HOSTNAME\USERname and the password. > Sometimes when you just leave it default the upgrade will fail for some reason.
8. Try the backup again

[m.novelli]

Happy Friday! https://www.veeam.com/kb4569 has been updated again!

There are now three options to resolve the issue:

1. A PowerShell script to automate the modification of the Config.xml file. — [Recommended Solution]
2. The original manual Config.xml modification procedure.
3. A hotfix for build 7.1.0.1501 that resolves the issue by changing the default SkipTeamsMessagesDataFolders setting state within the dll itself.
   This option should only be used if no other hotfixes have been installed.

In the end, all three of these options do the exact same thing: they change the SkipTeamsMessagesDataFolders setting to True.

Other improvements worthy of note:

• The notice box at the top of the article is more explicit about which versions accept the setting change in the Config.xml file.
• After further review, we've determined that the Config.xml edit procedure does not require stopping jobs or the Veeam Backup Proxy for Microsoft 365 Service.

Hi guys, do you plan to release this week a new build of VBO with the fix included or I should proceed with the PowerShell Script? I would prefer to install a new build of VBO , I have 30 - 40 or more customers to update...

Marco

[gds_nw4]

Do we have any date for update to solve the issue?

[mjr.epicfail]

Hi @gds_nw4.

The workaround solved the issue for you did it not?
I expect the "patch" will be making this value a fixed part of one of the DLL's instead of part of the config.xml

Are you expecting anything else?

[gds_nw4]

No that's ok, I prefer the patch, instead playing with xml

[camilosti]

Same here, without any change and from one day to the next it started to fail-

[mjr.epicfail]

Same here, without any change and from one day to the next it started to fail-

Well there was a change, at the Microsoft side. And it was announced that it would happen only not when exactly.

That’s also why the workaround was already in the Veeam software ready to be enabled.

[pesos]

Powershell option worked a treat.

/subscribe

[Goll420]

Found this thread before I came across the hotfix page. All working fine again, thank you guys!

[ndelamotte]

The PowerShell workaround works! Thanks!

[m.novelli]

Hi guys, do you plan to release an updated version of VBO to solve this issue? I'm on hold for all my customers
Thanks!

Marco

[Mildur]

Hi Marco

Yes, that's the plan. Our RnD team is preparing a new patch/build. But I don't have an ETA when it will arrive.
I recommend to run the PowerShell command from the KB to be able to continue protecting the mailboxes for your customers.

Best,
Fabian

[m.novelli]

They are 30 or 40 different installations... I would prefer to install the update to align all of them to the latest version and avoid to pass them twice

Marco