SOAP Header Action was not understood

[lazyspec]

Hi,

Since yesterday some mailboxes getting this error during backup jobs :

Processing mailbox mail@domain.com failed with error: Mail item data export failed. SOAP header Action was not understood.

Has anyone else also experiencing the same issue ?

[nielsengelen]

Hi,

Veeam is aware of the issue and looking into it. A KB has been posted (https://www.veeam.com/kb4397) which will be updated as we receive new information of our findings.

[lazyspec]

Hi Niels ,

Thank you for replying .

[Dax - My-Tech!]

Don't know if there is correlation with this issue, but one of our customers (that is experiencing this issue), told us that some 365 accounts where "kicked out" from their sessions (smartphone clients, Outlook and even some logins through the web interface had been logged out and where asking for a new login).
The issue for that customer has not been completely random, it started with 5 mailboxes that couldn't be backed up, then 10, now 12.

[Mike Resseler]

It might be indeed a correlation but I cannot confirm it at this point in time. We have an open support case with MSFT investigating this. The issue is that it does seem a bit random from our point of view as we are not seeing it everywhere, even with all the tenants we have for testing (which are quite a lot). But our support team and engineers are continuously investigating it.

[babine]

Hi,

I got the same issue in one of our client.
Yesterday we had like ~20 users with the "SOAP" error, this morning ~ 40.

Looking forward a solution thank.

[kavaa]

Its not only Veeam that has this issue, other backup services as well. Not going to put names here, but seen it.
Also its random per tenant, most of our tenants that we backup work fine, some don't. Also within that tenant some mailboxes succeed some fail.

[FLHXS]

partner reported exactly the same issue at some of his customers which I am experiencing since yesterday in my home lab. Errors seem to decrease over time meaning backup yesterday evening 15 failed objects, today same time 11 failed objects ?!
Funny thing is that v7BETA seems to be unaffected and works as expected without any issue !

[jetcosys]

I have the same issue and will monitor the KB. Interestingly, I have 15 organizations and only 2 have this issue. One only has one mailbox failing (out of 16) and the other has six (out of 47). Strange indeed!

[lars@hamer]

Piling in to report I've two for two O365 tenants with these errors.

Eagerly awaiting the explanation and fix so the service we're paying for is restored.

Thank you very much.

[mlumsden76]

I'm seeing this in about 10% of the tenants we are backing up.

[electricd7]

We are having it too. Started with a couple accounts and now up to 27.

[mgoss2448]

Same problem here also, up to 160 accounts, Case # 05798184.

[ghgard]

Hanging at 10 failures out of 47 mailboxes. At least it isnt getting worse

[Mike Resseler]

FYI, we have received information from customers that it went away with some of those (not yet all), so we are hoping that it is being gradually solved automatically (well, I guess you know that someone is fixing it).

We continue to monitor, and to push MSFT support

[ghgard]

No improvement yet, still sitting at 10 failed mailboxes.

[tineidae]

For us it startet on 12/29/22 with around 58 mailboxes having this issue, last night it was around 14 mailboxes.

[jetcosys]

Started at 10 failures (of 152 mailboxes) and now down to 5 failures.

[karsten123]

luckily zero errors out of over 300 mailboxes

[Gostev]

The issue is a part of a complex early-December change that is still rolling out across all M365 servers, thus very different experiences. However, today Microsoft has identified and fixed an oversight in that commit that was causing the issue in question, so eventually the error should clear out for all.

[Regnor]

Looks good; For one environment, the failing mailboxes decreased over the last days and today all mailboxes backed up successfully.

[jetcosys]

Back to all mailboxes successfully backed up here too.

[iju]

Same here. No errors anymore.

[pputt]

Hello, i since 2 months i got the same problem with 1 single Mailbox and I don't know how to fix the issue. I get the same error message as @lazyspec. Can someone help me pls?

[Mike Resseler]

Hi Paul,

The problem with this error is that it can mean a lot of different things. Please open a support case for it and post the case ID here. Most likely the above described problem is not what you are experiencing as this was an MSFT backend issue from quite some time ago