GFI Software Aurea SMB Solutions


Home » GFI User Forums » Kerio Connect » Error: An element node 'soap:Header'
Error: An element node 'soap:Header' [message #144512] Thu, 29 November 2018 13:07 Go to next message
ehans is currently offline  ehans
Messages: 3
Registered: November 2018
Hi,

I received the following error message through em client:

"_An Error Occurred_ - Synchronizing folder XXX/Inbox/ failed due to the following error: An element node 'soap:Header' of the type Element was expected, but node 'Body' of type Element was found."

And then I don't receive my new Emails.

I get the same message on two different computers in relation to the same account. We run a Kerio Connect server. I have not shared any folders.

What could be the problem?
Re: Error: An element node 'soap:Header' [message #144517 is a reply to message #144512] Thu, 29 November 2018 17:02 Go to previous messageGo to next message
Maerad is currently offline  Maerad
Messages: 275
Registered: August 2013
Not enough information, how is emclient connected?
Maybe do a reindex of your user to clear any DB errors.
Re: Error: An element node 'soap:Header' [message #144523 is a reply to message #144517] Thu, 29 November 2018 23:19 Go to previous messageGo to next message
ehans is currently offline  ehans
Messages: 3
Registered: November 2018
Hi,

It connects with Exchange Web Services.

Log from em client:

23:12:20 xxx@xxx.com[Exchange Web Services] Synchronizing folder 'xxx<_at_>xxx.com/Inbox/'
23:12:21 xxx<_at_>xxx.com[Exchange Web Services] Synchronizing folder list
23:12:21 xxx@xxx.com[Exchange Web Services] Synchronizing folder 'xxx<_at_>xxx.com/Inbox/'
23:12:21 MailClient.Storage.Application.OperationException: Synchronizing folder 'xxx<_at_>xxx.com/Inbox/' failed due to the following error: An element node 'soap:Header' of the type Element was expected, but node 'Body' of type Element was found. ---> Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializatio nException: An element node 'soap:Header' of the type Element was expected, but node 'Body' of type Element was found.
23:12:21 at Microsoft.Exchange.WebServices.Data.EwsXmlReader.InternalRea dElement(XmlNamespace xmlNamespace, String localName, XmlNodeType nodeType)
23:12:21 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadS oapHeader(EwsServiceXmlReader reader)
23:12:21 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadR esponse(EwsServiceXmlReader ewsXmlReader)
23:12:21 at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase .ReadResponseXml(Stream responseStream)
23:12:21 at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase .ReadResponse(IEwsHttpWebResponse response)
23:12:21 at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequ est`1.Execute()
23:12:21 at Microsoft.Exchange.WebServices.Data.ExchangeService.Internal LoadPropertiesForItems(IEnumerable`1 items, PropertySet propertySet, ServiceErrorHandling errorHandling)
23:12:21 at Microsoft.Exchange.WebServices.Data.ExchangeService.LoadProp ertiesForItems(IEnumerable`1 items, PropertySet propertySet)
23:12:21 at MailClient.Protocols.Exchange.ExchangeItemSynchronizer`2.<ChangesToItems >d__18.MoveNext()
23:12:21 at System.Linq.Enumerable.<SelectManyYield>d__20`3.MoveNext()
23:12:21 at System.Linq.Enumerable.<SelectYield>d__15`2.MoveNext()
23:12:21 at MailClient.Protocols.Common.ItemSynchronizeContext`2.StoreIt ems(SynchronizationType synchronizationType, IEnumerable`1 newItems)
23:12:21 at MailClient.Protocols.Common.MailItemSynchronizeContext.Store Items(SynchronizationType synchronizationType, IEnumerable`1 newItems)
23:12:21 at MailClient.Protocols.Common.ItemSynchronizeContext`2.Synchro nize[T](SynchronizationType synchronizationType, IEnumerable`1 items, Func`2 getUniqueId, Func`3 hasChanged, Func`2 isDeleted, Func`2 convertItems, Action`2 updateItem)
23:12:21 at MailClient.Protocols.Exchange.ExchangeItemSynchronizer`2.Syn chronize(IItemSynchronizeContext`1 synchronizeContext, Folder folder, CancellationToken cancellationToken)
23:12:21 at MailClient.Protocols.Common.ItemSynchronizer`2.<>c__DisplayClass32_0. <EnqueueSynchronize>b__1(WorkerStatus status, CancellationToken cancellationToken)
23:12:21 at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute (WorkerStatus status)
23:12:21 --- End of inner exception stack trace ---
23:12:21 at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute (WorkerStatus status)
23:12:21 at MailClient.Commands.Command.Process(WorkerStatus status)
Re: Error: An element node 'soap:Header' [message #144541 is a reply to message #144523] Mon, 03 December 2018 21:53 Go to previous messageGo to next message
ehans is currently offline  ehans
Messages: 3
Registered: November 2018
Nothing on this?
Re: Error: An element node 'soap:Header' [message #145513 is a reply to message #144541] Wed, 10 April 2019 16:19 Go to previous messageGo to next message
rieco is currently offline  rieco
Messages: 1
Registered: June 2012
Any new news on this Topic? We have the excat same problem on our Server. Also on newest Release 9.2.9!

We use EM client on Macos Mojave.

Would be very nice if someone of the community could help, because IMAP does not have some nice features like EWS.

Kind regards,
Michael Schön
Re: Error: An element node 'soap:Header' [message #145514 is a reply to message #145513] Wed, 10 April 2019 18:22 Go to previous messageGo to next message
ian.bugeja is currently offline  ian.bugeja
Messages: 270
Registered: March 2017
Location: Malta
We are investigating this issue. There is no workaround so far to connect emClient via EWS.

Ian Bugeja
GFI Software
Re: Error: An element node 'soap:Header' [message #145518 is a reply to message #145514] Wed, 10 April 2019 22:19 Go to previous messageGo to next message
RustyB is currently offline  RustyB
Messages: 53
Registered: April 2010
Quote:
We are investigating this issue. There is no workaround so far to connect emClient via EWS.
The Beta release for 9.2.9 noted "Added EWS support for EM Client and MailBird", but the official release made no mention of it. I asked a couple of times on these forums if the idea was scrapped or just left out of the release notes but never got an answer. I guess this confirms that it was left out of the release. I wish I was cool enough to get my questions answered on these forums.
Re: Error: An element node 'soap:Header' [message #146336 is a reply to message #144512] Thu, 01 August 2019 17:34 Go to previous messageGo to next message
FEichelsdoerfer is currently offline  FEichelsdoerfer
Messages: 30
Registered: June 2015
Location: Germany
Hi, we had the same problem with EM Client. New client wanted to test Kerio, Outlook is no option, Kerio client is poor in formatting Mails, thought EM Client would be the key to Kerio, but than this error occures...

Any news on this topic?
Re: Error: An element node 'soap:Header' [message #146395 is a reply to message #146336] Thu, 08 August 2019 20:28 Go to previous message
RustyB is currently offline  RustyB
Messages: 53
Registered: April 2010
I tried it out today in the new version 9.2.10 and I can confirm that I still get this error Sad
Previous Topic: Outlook 2016 Mac, Kerio Connect 9.2.8, Large Attachments
Next Topic: SSL Error CRL
Goto Forum:
  


Current Time: Sun Sep 22 07:53:54 CEST 2019

Total time taken to generate the page: 0.02603 seconds