Maintain control of your Microsoft Office 365 email data
Post Reply
Robvil
Expert
Posts: 113
Liked: 8 times
Joined: Oct 03, 2016 12:41 pm
Full Name: Robert
Contact:

SOAP header Action was not understood

Post by Robvil » Aug 05, 2017 7:36 pm 2 people like this post

Hi,

Case 02271744

Starting from today many of my mailboxes gives this error:

05-08-2017 21:29:02 15 (10172) Error: SOAP header Action was not understood.
05-08-2017 21:29:02 15 (10172) Stack:
05-08-2017 21:29:02 15 (10172) at System.Web.Services.Protocols.SoapHeaderHandling.SetHeaderMembers(SoapHeaderCollection headers, Object target, SoapHeaderMapping[] mappings, SoapHeaderDirection direction, Boolean client)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at EWServices.ExchangeServiceBinding.GetFolder(GetFolderType GetFolder1)
at Veeam.Ews.ExMailbox.GetFolder(GetFolderType gf)
at Veeam.Ews.ExError.<>c__DisplayClass6_0`1.<Catch>b__0()
at Veeam.Ews.ExError.Catch(Action action, String format, Object[] args)
05-08-2017 21:29:02 15 (10172) Mailbox processing failed: mail@domain.com
05-08-2017 21:29:10 19 (9032) Trying to resume processing...
05-08-2017 21:29:10 19 (9032) Error: Failed to get folder properties
05-08-2017 21:29:10 19 (9032) Stack:
05-08-2017 21:29:10 19 (9032) at Veeam.Ews.ExError.Throw(SoapException soap, String format, Object[] args)
at Veeam.Ews.ExError.Catch(Action action, String format, Object[] args)
at Veeam.Ews.ExError.Catch[T](Func`1 func, String format, Object[] args)
at Veeam.Ews.ExMailbox.GetFolder(BaseFolderIdType id, IReadOnlyDictionary`2 requestProps)
at Veeam.Archiver.Source.MailboxContextExtension.<>c__DisplayClass0_0.<GetSpecialFolder>b__0()
at Veeam.Archiver.Source.FolderRetry.<>c__DisplayClass14_0`1.<Process>b__0()
at Veeam.Archiver.Source.FolderRetry.Process(Action action)
05-08-2017 21:29:10 19 (9032) Error: SOAP header Action was not understood.
05-08-2017 21:29:10 19 (9032) Stack:
05-08-2017 21:29:10 19 (9032) at System.Web.Services.Protocols.SoapHeaderHandling.SetHeaderMembers(SoapHeaderCollection headers, Object target, SoapHeaderMapping[] mappings, SoapHeaderDirection direction, Boolean client)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at EWServices.ExchangeServiceBinding.GetFolder(GetFolderType GetFolder1)
at Veeam.Ews.ExMailbox.GetFolder(GetFolderType gf)
at Veeam.Ews.ExError.<>c__DisplayClass6_0`1.<Catch>b__0()
at Veeam.Ews.ExError.Catch(Action action, String format, Object[] args)
05-08-2017 21:29:10 19 (9032) Warning: Exchange Web Services request failed
05-08-2017 21:29:10 19 (9032) Retry count: 5
05-08-2017 21:29:10 19 (9032) No more retries left

Could this be related to the new Office 365 login portal page?

Robert

heggers
Lurker
Posts: 2
Liked: never
Joined: Apr 08, 2013 1:38 pm
Contact:

Re: SOAP header Action was not understood

Post by heggers » Aug 06, 2017 2:15 pm

I'm seeing this also. Looking for resolution.

bdp
Lurker
Posts: 1
Liked: never
Joined: Feb 19, 2017 10:43 pm
Contact:

Re: SOAP header Action was not understood

Post by bdp » Aug 06, 2017 10:57 pm

also same issue in recent days. Case #02271912

I'm finding:
  • a similar but changing number of fails on each attempt (around 160-170 of our ~260 mailboxes)
  • varying number of mailboxes actually enumerated on each job run
  • no obvious pattern to servers of affected mailboxes (all server prefixes are found in success & fail lists)
  • more than 60% of our mailboxes are throwing this error
  • no correlation to user creation or licensing option
  • no correlation to rollout of 50Gb->100Gb mailbox upgrades
I don't know if there's a better way, but I've copied the list of mailboxes & errors into a textfile, used cut & grep to produce two lists of UPNs, then run each against Get-Mailbox to find the location.

Code: Select all

# example input
6/08/2017 9:28:15 PM :: Processing mailbox: happyuser@example.com
6/08/2017 9:28:15 PM :: Processing mailbox saduser@example.com failed with error: Failed to get folder properties. SOAP header Action was not understood.

Code: Select all

# copy output into text file (bash), then produce user lists
$ cut -f7,8 -d' ' O365_out.txt | grep -v failed > o365_succeeded.list.txt
$ cut -f7,8 -d' ' O365_out.txt | grep failed | cut -d' ' -f1  > o365_failed.list.txt

Code: Select all

# powershell (fixed CRLF & added "upn" as 1st line in each file)
> $failed = Import-Csv o365_failed.list.txt
> $succeeded = Import-Csv o365_succeeded.list.txt
> $failed | ForEach-Object { Get-Mailbox -identity $_.upn | Select-Object * } | Out-GridView
> $succeeded | ForEach-Object { Get-Mailbox -identity $_.upn | Select-Object * } | Out-GridView
(Maybe this will help somebody, or somebody can help me with a more streamlined or concise powershell-only re-write?)

compconsult
Service Provider
Posts: 8
Liked: 1 time
Joined: Jun 22, 2017 2:35 am
Full Name: CCP Support Team
Contact:

Re: SOAP header Action was not understood

Post by compconsult » Aug 07, 2017 1:05 am

We saw this show up on the 5th as well.

It doesn't seem to be consistent on the same mailboxes - Just random.

davecoughlan
Lurker
Posts: 1
Liked: never
Joined: Aug 06, 2017 10:34 pm
Full Name: Dave Coughlan
Contact:

Re: SOAP header Action was not understood

Post by davecoughlan » Aug 07, 2017 5:17 am

Same issue here, appears to be getting worse with each backup. Logging a support ticket now

hiltls
Lurker
Posts: 1
Liked: never
Joined: Aug 20, 2009 3:03 pm
Full Name: S. Hiltl
Contact:

Re: SOAP header Action was not understood

Post by hiltls » Aug 07, 2017 8:34 am

Got this error also since yesterday! Any solution?

Robvil
Expert
Posts: 113
Liked: 8 times
Joined: Oct 03, 2016 12:41 pm
Full Name: Robert
Contact:

Re: SOAP header Action was not understood

Post by Robvil » Aug 07, 2017 8:37 am

I´m waiting for support to get backup to me after sending them my logs.

Dat_Guardian
Lurker
Posts: 1
Liked: never
Joined: Aug 07, 2017 11:35 am
Contact:

Re: SOAP header Action was not understood

Post by Dat_Guardian » Aug 07, 2017 11:48 am

I got the same error with my room mailboxes and group maiboxes. The normal user mailboxes work like before

Mike Resseler
Veeam Software
Posts: 4988
Liked: 525 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: SOAP header Action was not understood

Post by Mike Resseler » Aug 07, 2017 7:48 pm

Hi All,

If this is VBO 1.0, please log a support case. If this is VBO 1.5, please let me know through a PM or post it here that it is 1.5

In the meantime, I will escalate this as it seems to be suddenly appearing and with many users, which most probably means that MSFT has changed something and did not make us aware of it

Thanks
Mike

Mike Resseler
Veeam Software
Posts: 4988
Liked: 525 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: SOAP header Action was not understood

Post by Mike Resseler » Aug 07, 2017 7:50 pm

PS: To all people where I just had to approve the post... Welcome to the forums! This was the first time only (defense against bots) so feel free to post and contribute as much as you like!

Cheers
Mike

Mike Resseler
Veeam Software
Posts: 4988
Liked: 525 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: SOAP header Action was not understood

Post by Mike Resseler » Aug 07, 2017 8:04 pm

OK. Our QC engineers have already responded back (which is pretty quickly considering time of the day for them :-)). They have discovered it also this weekend and the investigation is already going on. Nevertheless, please continue to create support calls. This can only help the investigation and please your case # and follow-up here

Thanks
Mike

JonJR
Novice
Posts: 4
Liked: never
Joined: Mar 21, 2017 11:25 pm
Full Name: Jon Rhoades
Contact:

Re: SOAP header Action was not understood

Post by JonJR » Aug 08, 2017 12:44 am

We've had this problem with v1 & logged with support.

I thought I'd take the opportunity to try using the Beta 1.5, and whilst it is still running its first big backup, it actually works and doesn't SOAP error the same way that v1 does. YMMV & NFI

Kostya
Veeam Software
Posts: 104
Liked: 28 times
Joined: Jun 18, 2012 9:38 am
Full Name: Kostya Yasyuk
Contact:

Re: SOAP header Action was not understood

Post by Kostya » Aug 08, 2017 9:54 am

Hi all, let me ask: does anyone still have these errors? It seems like different DEV and QC labs was affected this weekend by the same error, but we cannot reproduce it anymore, neither in 1.0, nor 1.5. If someone still have it, please let us know, so we ca review your logs. Thanks.

JonJR
Novice
Posts: 4
Liked: never
Joined: Mar 21, 2017 11:25 pm
Full Name: Jon Rhoades
Contact:

Re: SOAP header Action was not understood

Post by JonJR » Aug 08, 2017 10:27 pm

Kostya wrote:Hi all, let me ask: does anyone still have these errors?.
The v1 O365 backups are now working perfectly, we've now had 2 successful backups. I guess it was a Microsoft issue!

Cheers Jon

Mike Resseler
Veeam Software
Posts: 4988
Liked: 525 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: SOAP header Action was not understood

Post by Mike Resseler » Aug 09, 2017 5:33 am

Jon,

Thanks for coming back to us. Please keep us informed when this appears again and please let support know if you have a ticket.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 2 guests