Maintain control of your Microsoft Office 365 email data
Polina
Veeam Software
Posts: 783
Liked: 108 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: SOAP header Action was not understood

Post by Polina » Aug 06, 2019 5:13 pm

Clive,

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

cesadan01
Novice
Posts: 5
Liked: never
Joined: Jun 04, 2019 7:15 am
Full Name: Daniele Cesario
Contact:

Re: SOAP header Action was not understood

Post by cesadan01 » Aug 07, 2019 9:24 am

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
Veeam Software
Posts: 783
Liked: 108 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: SOAP header Action was not understood

Post by Polina » Aug 07, 2019 9:38 am

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
Novice
Posts: 5
Liked: never
Joined: Jun 04, 2019 7:15 am
Full Name: Daniele Cesario
Contact:

Re: SOAP header Action was not understood

Post by cesadan01 » Aug 07, 2019 9:40 am

Hi Polina,

thanks, my case ID is 03701864.

Daniele.

aich365
Service Provider
Posts: 88
Liked: 2 times
Joined: Aug 10, 2016 11:10 am
Full Name: Clive Harris
Contact:

Re: SOAP header Action was not understood

Post by aich365 » Aug 07, 2019 10:44 am

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

I have deployed this and will see what happens

Thanks

joestern
Lurker
Posts: 2
Liked: 4 times
Joined: Aug 07, 2014 2:28 pm
Full Name: Joe Stern
Contact:

Re: SOAP header Action was not understood

Post by joestern » Aug 07, 2019 3:40 pm 1 person likes this post

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
Lurker
Posts: 1
Liked: 1 time
Joined: Aug 07, 2019 2:40 pm
Full Name: Jay Penney
Contact:

Re: SOAP header Action was not understood

Post by Crenor » Aug 07, 2019 3:45 pm 1 person likes this post

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
Service Provider
Posts: 83
Liked: 14 times
Joined: Mar 16, 2015 4:00 pm
Full Name: David Rubin
Contact:

Re: SOAP header Action was not understood

Post by RubinCompServ » Aug 07, 2019 6:20 pm

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
Veeam Software
Posts: 783
Liked: 108 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: SOAP header Action was not understood

Post by Polina » Aug 08, 2019 10:21 am

@Jay and All,

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

sanch
Novice
Posts: 7
Liked: never
Joined: Mar 26, 2019 7:52 am
Contact:

Re: SOAP header Action was not understood

Post by sanch » Aug 08, 2019 1:30 pm

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

Polina
Veeam Software
Posts: 783
Liked: 108 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: SOAP header Action was not understood

Post by Polina » Aug 08, 2019 2:44 pm

Hi sanch,

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

jcassar
Lurker
Posts: 1
Liked: never
Joined: Aug 09, 2019 1:56 am
Full Name: Jessie Cassar

Re: SOAP header Action was not understood

Post by jcassar » Aug 09, 2019 2:00 am

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

Polina
Veeam Software
Posts: 783
Liked: 108 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: SOAP header Action was not understood

Post by Polina » Aug 12, 2019 5:30 pm 1 person likes this post

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!

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests