There is an error in XML document

[Polina]

Hi All,

RnD has identified the root cause and is working on a workaround. It will take some time to get it ready and verified, but I hope to see a hotfix available quite soon.

Thanks!

[mjr.epicfail]

Hotfix is available

https://www.veeam.com/kb4527

[mike.anderson]

+1 Case # 07051892

[rtheseeker]

we have some long running backup copy jobs; when I stop these services in Veeam would it affect those copies as well; the hotfix says just ensure no backup or restore jobs are running; what about backup copy jobs

[rtheseeker]

Ensure that there are no Backup jobs or Restore sessions running.: what about backup copy jobs from one object storage to another; shall we stop those first ?
On the Veeam Backup for Microsoft 365 server, stop the following services:
Veeam Backup for Microsoft 365
Veeam Backup Proxy for Microsoft 365
Veeam Backup for Microsoft 365 RESTful API

[Mildur]

Stopping those services will also cancel a backup copy job. Make sure there is no active session (backup, backup copy, restore) running before you stop the services.

Best,
Fabian

[JustBackupSomething]

Adding quick update for everyone, hotfix has been released today for 365.

KB: https://www.veeam.com/kb4527

[dali@iae.nl]

The hotfix https://www.veeam.com/kb4527 works perfect for us, thanks!

[dali@iae.nl]

The hotfix https://www.veeam.com/kb4527 worked perfect for us. Errors gone.

[AlexLudwig-ITDienst]

Hotfix has worked. Many thanks for the quick fixing.

[mschwarzer]

Many thanks to all of you, especially those who had a long last few days

[flisk]

Veeam Regarding the "xml" error we have deployed the following fix:
https://www.veeam.com/kb4527

[pgallenga]

The hotfix in the KB4527 seems to be missing a destination path, where I find the same Veeam.Ews.dll that has to be pathed:
C:\Program Files\Veeam\Backup365\Packages\Appliance\

I've also added a comment on the documentation.
Do anybody else find the Veeam.Ews.dll in that path on its installation?

[Mildur]

Hello Paolo

Veeam.Ews.dll does exist in C:\Program Files\Veeam\Backup365\Packages\Appliance\ on my Veeam Backup for Microsoft v7a server (7.1.0.1301). Are you replacing the files on your backup server or a remote management system? Which version of VB365 are you running?

If you have issues in replacing the files, you may open a support case to make sure everything is alright.

Best,
Fabian

[pgallenga]

Hello Fabian,
that's correct, the Veeam.Ews.dll library exists also in the ...\Packages\Appliance\ path, but that path is not specified in the HotFix KB4527 (point 7. of the Hotfix installation instructions).

I think that path should be added in the instructions, if that library is also to be replaced.

(running VB365 build 7.0.0.4388, checked on two installations: no issues after patching, everything works correctly).

[Mildur]

Ah, I understand now.
Let me clarify it with the team if you need to replace the DLL in this path. If so, we will add the path to the kb article.

Best,
Fabian

[steverrr]

Case #07053369

Hi, just trying to get quick confirmation on this-
We have the XML error. failing backups.
We are running version 6.0.0.385

The Hotfix seems to apply only to versions 7.xx??

What's the steps for fixing version 6.0.0.385?? Do we need to upgrade to latest 7.xx first??

[Gostev]

Hi. That is correct, you need to upgrade to the current version. No hotfixes are issued for V6 since it reached the End of Fix stage in February 2023. Thanks

[bailey.bixal]

Case #07053611

We're hitting issues with the hotfix. On 7.1.0.1301 and using the hotfix dlls we cannot restart the stopped services afterwards. Software will hard-crash as well, replacing the original dlls fixes the crashing, but of course leaves us with the XML error still

[steverrr]

Thanks for the answer. Update applied, app version now latest, repositories upgraded.
Then hotfix applied. One confusing item, the instructions say update repositories after hotfix, the hyperlink embedded describes the "out of date " fix, however mine were not marked out of date, JOBS failed. It wasn't till I clicked the "in app Upgrade Proxy/Repositories button" that the system upgraded and started functioning.

Might want to clarify that in the Hotfix instructions...otherwise I am fixed....Case #07053369

https://www.veeam.com/kb4527
Item 9 has an embedded hyperlink that points to this:
https://helpcenter.veeam.com/docs/vbo36 ... ink&ver=70

Upgrading Backup Proxy Servers
To communicate with backup proxy servers, Veeam Backup for Microsoft 365 uses the proprietary service — Veeam Backup Proxy for Microsoft 365 Service that is installed on the target proxy machine. When you upgrade Veeam Backup for Microsoft 365 to a newer version, this service becomes outdated and all backup proxies configured in your environment are marked as Out of Date and must be upgraded manually.

Mine were NOT out of date after Hotfix.

[Gostev]

Thanks Steve, @tpayton just fixed it.

[Mildur]

that's correct, the Veeam.Ews.dll library exists also in the ...\Packages\Appliance\ path, but that path is not specified in the HotFix KB4527 (point 7. of the Hotfix installation instructions).

I think that path should be added in the instructions, if that library is also to be replaced.

Hi Paolo

I got an answer from our team.
Files in this folder are used for our archiver appliance. This appliance is used for backup copy jobs to Azure or AWS archive storage. The appliance does not interact with the production environment.

You can replace the dll in the appliance folder for consistency reasons, but nothing would happen. That‘s why the path isn‘t mentioned in the user guide.

Best,
Fabian

[popjls]

C:\Program Files\Veeam\Backup and Replication\Explorers\Exchange

I'm running 7.0.0.4388 and is it normal that I don't have the Exchange folder under Explorers? Iv'e manually created it for now and added the .dll too and started all the services ok.

Edit: Jobs seems to be running ok.

[rtheseeker]

it worked fine for our environment as well. jobs are running fine since the update; tested restore as well

[George_Ene_Peg]

I can confirm the hotfix to be a solution. Thanks for the efforts team.

[AlexLeadingEdge]

Applied the Hotfix to 7.1.0.1301 and it appears to be working 100% again. Thanks guys

[joevilhs]

Hi there! we've applied the hotfix on ours last Friday, it did fix 4 out of 6 clients we backup, but 2 out of 6 still has the same issue. I've made sure that the proxy servers are also upgraded and did a reboot but the issue remains.

Anything else you can recommend I try?

TIA

[ACrispiels]

Same issue here going for the past few days from a customer

[sandsturm]

applying the hotfix helped in my case as well, all EXO backupjobs are running fine now.

Thanks a lot!
sandsturm

[ACrispiels]

Same issue here going for the past few days from a customer, not yet resolved (for me) with the latest manual upgrade to the release 7.1.0.1301.