AquaMail Forum

English - Android => Bug reports => Topic started by: S on March 06, 2014, 05:56:51 am

Title: EWS Error: Client Access server version doesn't match the Mailbox [Resolved]
Post by: S on March 06, 2014, 05:56:51 am

Good day,

I purchased AquaMail to access my work Exchange server (EWS), but am receiving the following error. Anyone know how I might rectify this? Please assist if so. Thank you.

The error from the AqualMail debug log is below:

<m:ResponseMessages><m:GetFolderResponseMessage ResponseClass="Error"><m:MessageText>An internal server error occurred. The operation failed.</m:MessageText><m:ResponseCode>ErrorInternalServerError</m:ResponseCode><m:DescriptiveLinkKey>0</m:DescriptiveLinkKey><m:MessageXml><t:Value Name="InnerErrorMessageText">The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.</t:Value><t:Value Name="InnerErrorResponseCode">ErrorWrongServerVersion</t:Value><t:Value Name="InnerErrorDescriptiveLinkKey">0</t:Value><t:Value Name="AutodiscoverSmtpAddress">[name]@[company].com</t:Value></m:MessageXml><m:Folders/></m:GetFolderResponseMessage></m:ResponseMessages></m:GetFolderResponse>"

* 09/03/2014 Edit: Marked as resolved.

Title: Re: EWS Error: Client Access server version doesn't match the Mailbox server version
Post by: Kostya Vasilyev on March 09, 2014, 01:42:28 am

@S - thank you.

This can happen when the EWS server that serves your @corp.com account is not corp.com, but rather some other server. For example, "ews.mail.corp.com" or something like it.

The IT dept should know what it is.... Or you can try the version below, it tries to perform autodiscovery of the actual EWS server (although it's not quite as comprehensive as that of Outlook...)

http://www.aqua-mail.com/download/AquaMail-market-1.3.22.5.apk

Title: Re: EWS Error: Client Access server version doesn't match the Mailbox server version
Post by: S on March 09, 2014, 10:32:32 pm

The new apk produced the same on-screen error (but I didn't check the raw log). However, I did try a few other servers directly as you suggested and that worked. Thank you for the assistance.