There is an error in XML document

[Mildur]

@ACrispiels
You need to install the hotfix from KB4527 after the upgrade to 7.1.0.1301:
https://www.veeam.com/kb4527

@joevilhs
Please open a case with our customer support team if the hotfix doesn‘t solve the issue.

Best,
Fabian

[ACrispiels]

@Mildur, thank you, ok for me after applying the suggested KB4527 (post to the upgrade to 7.1.0.1301).

[mamosorre84]

The hotfix worked for me..thank you Veeam Team!!

[omichalski]

Hello,

Our company gets the same error on our mailboxes, I followed guide from https://www.veeam.com/kb4527 but I don't have these locations on our server:

C:\Program Files\Veeam\Backup365
C:\Program Files\Veeam\Backup365\Packages\Proxy
C:\Program Files\Veeam\Backup and Replication\Explorers\Exchange
C:\Program Files\Veeam\Backup365\Packages\Appliance\

hotfix file, Veeam.Ews.dll, appears in C:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\WebRestore\dll_backup\Veeam.Ews.dll and only there. I replaced it but we still get the error. Do I create missing directories?

We use latest build, 7.1.0.1301.

[Mike Resseler]

@omichalski are you applying the hotfix on the VB365 server? It seems that you are applying it on a server that has the explorers and potentially the desktop UI installed, but that server is probably not the VB365 main server.

[omichalski]

Thank you for reply, that refreshed my memory. Our partner installed server on dedicated virtual disk, I found the "missing"directories

[AndreBIAL]

Hello,

after follow the hotfix installation instructions, Veeam services doesn't start. In event viewer I see this generic error: "The Veeam Backup for Microsoft 365 Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."

Anyone with this behavior? I tried a reboot but not success.

Thanks!

[mrshahin]

Hi,I see the same issue for the Archive mailbox of 2 of our users but my V365 verion is 7.0.0.4388 beeld: P2023 1015!
can we use this hotfix as well? if yes, which one?

[Mildur]

@mrshahin
Yes. You are on 7.0.0.4388.
Use privateFix_12.0.0.4388 as explained in the kb article.

Best,
Fabian

[Mildur]

@AndreBIAL
Please open a case with our customer support team if you face issues with installing the hotfix.

Thank you,
Fabian

[m.novelli]

Idem

Marco

[AlexLeadingEdge]

We have a second client with this issue today. Hotfix applied and the backup has completed successfully.

[dpeach01]

I have 4 mailboxes with the same error. I will follow this thread awaiting a solution.

[Mildur]

@dpeach01
No need to wait. The kb article with the solution is linked multiple times in this topic.
https://www.veeam.com/kb4527

Best,
Fabian

[jimvad]

Wanted to post an update myself. Received the same message as others overnight for two users in the same department. Checked with them this morning to see if they forwarded or shared anything between them yesterday and sure enough one shared their calendar with the other. Just wanted to share.
About to run the KB update. Thanks!

[nicof1979]

I added a link to the KB in my first comment in this topic:
https://www.veeam.com/kb4527

Best,
Fabian

Same issues, solved with: https://www.veeam.com/kb4527

Thks @mildur

[david.sole]

Hi Team,

Same problem here, some mailboxes of any organization aren't backed up. We're currently applying the hotfix, waiting for results.

I can't underestand why our backup jobs are ending "yellow" when some mailboxes, or many in some cases, are processed with errors that prevents copy it's data... In this case I think that the backup result must be red... A bit confusing how Veeam for Microsoft 365 is reporting jobs results.

Many thanks,

[Mike Resseler]

Hi David,

The hotfix should solve the issue.

RE: Yellow. This has been an ongoing discussion for many years already . We used to have it red, but most of our customers prefer to have it yellow as certain data has been protected.

[Gostev]

In Veeam's classic paradigm of job statuses it should be red (error) for sure, as some production data is not getting backed up. In cases of strong disagreements with some customers, which in VBR we only had about some particular events once or twice in past 15 years. we should make it an error by default + a registry key to override.