SOAP header Action was not understood

[Polina]

Clive,

It should already be available, please contact your support engineer.

[cesadan01]

Hi Polina,


I'm having the same problem when I add an organization in VBO.
I get the error SOAP header Action was not understood.
I did not understand if there is a solution to the problem.

Thanks

Best regards.

Daniele

[Polina]

Hi Daniele,

Please create a support call to get the fix. Also, take a minute to post your case ID in this thread for transparency.

Thanks!

[cesadan01]

Hi Polina,

thanks, my case ID is 03701864.

Daniele.

[aich365]

I have received an updated EWS dll from Support
Veeam.Ews.dll

I have deployed this and will see what happens

Thanks

[joestern]

I had this same issue; I contacted support and they sent me a link to the replacement DLL. After swapping it in, I was able to complete the EWS sign-in process using legacy authentication.

[Crenor]

The fix from support works and is very quick. It is not a proper fix though so it will be interesting to see how long it takes to put it into a patch.

[RubinCompServ]

This is happening for us also. I've just opened case #03703005. Giving a mailbox to my service account makes a good workaround, but not a great solution.

[Polina]

@Jay and All,

The patch was delivered to support, please work together with your support engineers to apply it.

[sanch]

Same problem for me when adding a new organization in VBO with basic authentication.
Case ID: 03704423

[Polina]

Hi sanch,

Noticed; thanks for letting us know. Please apply the suggested fix to resolve the issue.

[jcassar]

Same problem here after upgrading from version 2 to version 3:
Case ID: 03705501

[Polina]

The root cause on the Office 365 side seems to be resolved now as well and VBO works as expected.
In case you still see the 'SOAP header' error in VBO environment, please contact Veeam Support for a private fix.

Thanks!