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

[mjr.epicfail]

Hi Marco,

Its almost a shoot and forget type of script, I'd highly recommend doing it.
I didn't check if the failed item prevents a restorepoint of that mailbox, if so you it could be you are missing out on backups if you don't fix it.

[Mildur]

Hi Marco

I asked the team for an estimated release date of the patch. We expect it in 1-2 weeks.

Best,
Fabian

[Gostev]

I heard more like 2-3 weeks at least because it will be the part of a bigger patch - the immediate release vehicle that has been in the works for quite some time now - and due to its size "landing" may take a while. On the other hand, there's no pressure to scrap that code branch due to simple manual fix available for the issue discussed in this topic (unlike for other issues this patch fixes).

[m.novelli]

Marco

[andrdio]

After making thise changes and restarting the services, it works again.

This worked for me too.
Thanks!

[Mildur]

Hi all

The fix for this issue is now included in our newest patch (P20240418 - 7.1.0.2031) for Veeam Backup for Microsoft 365 v7a:
https://www.veeam.com/kb4533

Best,
Fabian

[m.novelli]

Super!

[compufreak]

Same problem here changed nothing? Any feedback or idea what is causing this?

[Mildur]

Hi Francois

Welcome to the forum.
Please check out the kb article: https://www.veeam.com/kb4569

You can either update to the latest version of v7a (7.1.0.2031) or use the manual workaround for previous versions. That will solve the issue.

Best,
Fabian

[murdsn]

Is it recomended to remove the line from the config file when upgrading to the fix version? Or does it just totally not matter?

[mjr.epicfail]

Hi,

It doesn't matter.
The result is the same.

[sopinfra]

Hi,
Is there any risk by updating to the latest version(7.1.0.2031) from 7.0.0.3604 P20230512 ?

Edwin

[Polina]

Hi Edwin,

Upgrades between v7 and v7a patches are fully supported. There shouldn't be any issues.