expected XML node type was Element, but the actual type is EndElement

Mail
1

[Exchange Web Services] Sending email failed due to the following error: The expected XML node type was Element, but the actual type is EndElement.

Getting this error infrequently when trying to send an email with an exchange account. I am able to temporarily fix this by removing and re-adding the account to emclient, but it ends up happening again after some time. Once I get the error NOTHING will leave the outbox.

I can send email fine in the web client that is available so I know it’s not my email provider.

I am running emclient version 10.1.5131 (69d0414) on windows 10

Anyone have any suggestions?

2

Have the same problem. Out of the blue eM Client cannot send emails anymore.

This used to happen with v8.1.x. So I upgraded to v9… nothing changes. v10… same behavior.

@jstombaugh Do you have to remove the mail account and re-add it, or does it work also when adding the same account again?

3

I am able to temporarily fix this by removing and re-adding the account to emclient, but it ends up happening again after some time

I am running emclient version 10.1.5131 (69d0414) on windows 10

As removing and readding the account “only temporarily fixes it”, then if you installed eM Client originally from the website, try upgrading to the latest V10.4.5298 via the release history page if you haven’t already and see if that fixes it.

Also If the email body or headers contain eg: special symbols (like $ ) or characters that are not XML-compliant, the parser will fail. So try sending “a plain-text test email” to confirm if the content is causing this issue.

If upgrading to the latest version still makes no difference “and even plain text messages won’t send”, then could be possible something running resident in the background interfering.

So you are running any eg: optionally installed firewall / security programs or optionally installed antivirus programs or vpns “other than what comes default with your OS”, then try completely disabling those to test in case of interference.

If you have nothing optionally installed like the above or you do but disabling those makes no difference and you have the latest Windows 10 OS updates, then suggest next if you have a current active paid Pro, Personal or Business version go to the VIP support page and login and lodge a support ticket to be investigated.