There is an error in XML document

[bcravn]

Across several of our customers, we are seeing a lot of errors like:

13-12-2023 07:12:05 :: Processing mailbox xxxxxx failed with error: There is an error in XML document (1, 5332).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:00:24
13-12-2023 07:13:29 :: Processing mailbox xxxxxfailed with error: There is an error in XML document (1, 115683).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:00:07
13-12-2023 07:13:53 :: Processing mailbox xxxxx failed with error: There is an error in XML document (1, 59061).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:01:41

We have a case for it:
Case #07047525
But we find it quite hard just to tell all of our customers, "to fix it yourself".
So far we have not been able to find what they have in common. Because its not all mailboxes within the same tenant, and its not all tenants..

Should be noted, that we are running VBO 7, and the customers are not even sharing the same VBO or backup proxies. (All of them same version, however.)

[Mildur]

Hello Bjarke

I checked the case and the error message.
Our support team has multiple cases with the same error message. The error it's currently investigated by our RnD teams.

UPDATE - SOLUTION
We have released a KB article with a hotfix regarding this issue:
https://www.veeam.com/kb4527

Best,
Fabian

[Daniel84]

Hello,

since today, we are getting an error when backing up mailboxes using Veeam Backup for Microsoft 365 for one of our Tenant:

Code: Select all

Processing mailbox XXX failed with error: Fehler im XML-Dokument (1,1452).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/services/2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>.
Processing mailbox XXX failed with error: Fehler im XML-Dokument (1,7101).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/services/2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>.
Processing mailbox XXX failed with error: Fehler im XML-Dokument (1,22954).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/services/2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>.
Processing mailbox XXX failed with error: Fehler im XML-Dokument (1,2615).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/services/2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>.
Processing mailbox XXX failed with error: Fehler im XML-Dokument (1,5106).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/services/2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>.

Does anyone know what kind of error this is and how to fix it?

Our Veam Backup for Microsoft 365 Version: 7.1.0.1301

[Mildur]

Hello Daniel

Welcome to the forum.
RnD is aware of this issue. We are investigating it.
Please open a case with our customer support team and provide them with a current log package. If we have to release a private hotfix, you need a case number to retrieve it.

Best,
Fabian

[sascha.miloradovic]

Same issue here across multiple tenants and only appearing on certain mailboxes (so like 95% are working) - Case #07042781

13.12.2023 14:02:03 :: Processing mailbox XXXXXXXXXXXXXXXXXXX failed with error: There is an error in XML document (1, 84025).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:17:49

[mjr.epicfail]

Same for us, case id 07045802

[sandsturm]

we have the same issue in our environment.
Will there be an official solution for that or do I have to create a case to get a private fix?

thx
sandsturm

[Mildur]

Hi Sandsturm

The investigation is still in progress. Once we identify the root cause of the issue, we'll release an official statement along with a solution.
A support case will help you to be prepared in case we will deliver a private hotfix. It will also help us in our investigation.

Best,
Fabian

[charles.k.AVP]

Also experiencing this across multiple clients. I have been assigned Case #07049833.

[ajriek]

We have the same issue with case # 07049447

[pettcomputers]

Same as the others, case# 0705016.

[Mike Resseler]

All,

As additional information... The issue is that in the background, M365 started to return a new object type which is not supported in their own schema. Because of that, we cannot identify this which causes this error. Our RnD teams are working on bringing a fix as fast as possible, me or @Polina will keep you posted once this fix is available with support.

Mike

[AlexLeadingEdge]

Same issue here too. Please let me know when there is a fix.

Code: Select all

14/12/2023 9:59:07 am :: Processing mailbox REDACTED failed with error: There is an error in XML document (1, 89733).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/services/2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/services/2006/types'>. :: 0:00:51

[vfwdit]

All,

As additional information... The issue is that in the background, M365 started to return a new object type which is not supported in their own schema. Because of that, we cannot identify this which causes this error. Our RnD teams are working on bringing a fix as fast as possible, me or @Polina will keep you posted once this fix is available with support.

Mike

I *think* this problem is triggered when a user forwards a message in their mailbox.

We have this problem on 3 of our mailboxes and it happened pretty much at the next backup AFTER they forwarded a message in their mailbox. Probably what 'SharingMessage' is.

[rlspeeks]

Case # 07050453

[cb-mckomp]

Case #07050542

[joevilhs]

Case #07050557

[sbabcock]

Same here - happened for 1 user in an organization - the rest look ok

2023-12-13 5:01:57 PM :: Processing mailbox xxx@abc.com failed with error: There is an error in XML document (1, 4882).. The specified type was not recognized: name='SharingMessage', namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', at <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:01:09

Any update on Hot Fix

I have not created a ticket as I assume there will be a general rollout of any fix

[popjls]

Same problem, thought it was us. Guess not.

[DWG-MWE]

I also have the same problem - If I found the email with the incorrect type - I would simply remove it... I'm also hoping for a fix

Processing mailbox 1234@xxx.de failed with error: Fehler im XML-Dokument (1,7813).. Der angegebene Typ wurde nicht erkannt: Name='SharingMessage', Namespace='http://schemas.microsoft.com/exchange/s ... 2006/types', bei <Message xmlns='http://schemas.microsoft.com/exchange/s ... 2006/types'>. :: 0:01:02

[agrob]

+1 We have the same issue on multiple mailboxes.

[Seb.pythoud]

+1 - Case #07050778

[tommy.lidal]

3 mailboxes with same problem, Not started a case since casePage referes to the KB.

[RolfMueller]

+1 #07050831

[pputt]

Case #07050862

[Mildur]

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

Best,
Fabian

[donkeymagic]

Got one customer affected by this at present. Thanks for posting the KB, will follow that rather than flood Veeam with another case.

[NTIC 94130]

Hello,
Same behaviour here, 4 accounts with this error. Following here instead of creating new case.

[JasonSarratt]

Same issue here going for the past few days

[AlexLudwig-ITDienst]

The same here. I got the same error from a customer today.