What are the followups for these common status codes?

Question

Hi,

I have an application that uses ActiveSync to synchronize data. I would like to ask what the expected behaviors when the client receives the following common status statuses when sending a command request to server. The document only briefly explains what an error status mean and does not mention what the client is supposed to do.
https://msdn.microsoft.com/en-us/library/ee218647(v=exchg.80).aspx

• 110, server error, The server encountered an unknown error, the device SHOULD NOT retry later.
  What does "SHOULD NOT retry later" really mean? To retry after a long period of time? Or should not retry forever?
  
• 114, MailboxServerOffline, The mail server is offline.
  Why would this happen? What should client app do when encountering this? Just waiting till the server goes online again? Anyways to know how long it takes?
  
• 115, SendQuotaExceeded, The request would exceed the send quota.
  What is the "send quota"? Is it configurable by IT admins?
  
• 123, UserHasNoMailbox, A mailbox could not be found for the user.
  Again, Why would this happen? The mailbox is deleted by someone? Should user contact IT admins for this?
  
• 125, UserPrincipalCouldNotBeFound, The user was not found in the directory service.
  Should the client app wipe the user account when encountering this error?

I would greatly appreciate any help.

Thanks.

Answer 1

Hi sleung496

Thank you for your question.  An engineer from the protocols team will contact you soon.

---

Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

Answer 2

Hello sleung496

I'm researching this for you and will get back.

Thanks.

---

Tarun Chopra | Escalation Engineer | Open Specifications Support Team

Answer 3

Hello sleung496:

Please find details on status codes below except 110 code. I'm still working on to get more information on code 110.

MailboxServerOffline: The response should be used for temporary conditions and the Retry-After HTTP header should contain the estimated time for the recovery of the service. Client should retry after the time specified in retry-after header.

SendQuota is mailbox size at which users associated with mailboxes in this mailbox database can no longer send messages. IT admin can set this size, refer following article for details -
https://technet.microsoft.com/en-us/library/aa997097(v=exchg.80).aspx

UserHasNoMailbox error could be due to multiple reasons. I'll list some:
1. The user does not appear to have a mailbox
2. Permission or licensee on that account has been altered.
Account admin should be contacted to resolve the issue. Refer following related threads -
https://support.microsoft.com/en-us/help/2620052/a-user-cannot-access-a-mailbox-by-using-outlook-web-app-in-office-365
https://serverfault.com/questions/755768/when-user-doesnt-have-a-mailbox-on-office-365-portal-but-has-one-in-exchange

UserPrincipalCouldNotBeFound means that user account is not found in Active Directory. Since the account doesn't exist, client app won't be able to delete it either.

Thanks

Answer 4

Updating thread on status code 110:

This status code means that server has encountered an unknown error and client should not retry as the retry-after header will be empty in this case. The processing on client is equivalent to HTTP 500 status code - http://www.w3.org/Protocols/HTTP/HTRESP.html

   

---

Tarun Chopra | Escalation Engineer | Open Specifications Support Team

Answer 5

Thanks for your help, Tarun!