ActiveSync Fails to Deliver E-Mail to iPhones after Database Repair – Event ID 1008

Posted: April 10, 2012 in Exchange 2010, SBS 2011
Tags: , , , ,

The Remaining Problem to Be Solved

In my previous  post, I discussed the loss of a .vhd file for SBS 2011 and how I managed to retrieve an older copy and mount that.  However, I was not able to mount the Exchange mailbox and public folder databases.  I solved that problem by running eseutil.exe with the /p option and they mounted as expected.

What started to happen were critical and error events to the application log.  While most appeared to be transient and would likely cure themselves – they did – one did not.  Event ID 1008.  Here is an excerpt from the description:

Description:
An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization.

URL=/Microsoft-Server-ActiveSync/default.eas?User=xxxxxx&DeviceId=Appl70111HXKA4S&DeviceType=iPhone&Cmd=SendMail
— Exception start —
Exception type: System.Web.HttpException
Exception message: An error occurred while communicating with the remote host. The error code is 0x800703E3.

Note in particular the line beginning with “URL=/”.  The user name of the mailbox owner appears and it is their phone that is not syncing properly.  In my particular case, the users could send email from their phones but not receive .  Of course in this instance, only two users were effected: the owners of the company!

What Didn’t Work

The first thing I had them do was to delete the Exchange email account from their iPhones and re-add it.  It was a real test to see if they could accomplish this on their own.  Happy to say they did, sad to say it re-added the account and folders but still didn’t allow the phones to receive email.

Time for harsher measures, so I opened Exchange Management Console and expanded the Recipient Configuration and select Mailbox.  Then I selected one of the users and from the Actions pane on the right, I selected Manage Mobile Phone.  The following wizard appeared:

EMC Recipient Mobile Phone

The wizard background didn’t appear pink, but you get the point.

Notice that the radio button “Remove mobile phone partnership” is selected.  I completed the wizard by clicking on the Remove button, and felt very pleased.  I allowed for about an hour to pass to have Exchange and ActiveSync re-establish the partnerships.  After three hours, I figured that trick was not going to happen.

What Did Work

The trick that did work was pretty straight forward.  Here’s what I did:

  1. Open EMC and expand Organization Configuration.
  2. In the right hand action pane, select New Mailbox Database.
  3. Complete the wizard to create a new mailbox database and mount it.
  4. In EMC, expand Recipient Configuration and select Mailbox.
  5. Select the user(s) whose phones are not syncing.
  6. In the right hand action pane, select New Local Move Request.
  7. Complete the wizard to move the mailboxes to the new database created in the previous steps.
  8. In the EMC navigation pane on the left, click on Move Request and follow the progress of the mailbox move(s).  NOTE: you can double-click on a mailbox and the properties will display the size of the mailbox and the percent complete.  It does not refresh so close it and re-display as needed.

Just as soon as the move(s) were complete, email flow to the phones was re-established.

Will ActiveSync Still Work if You Move Them Back?

I don’t have an answer for that yet. But I will have an occasion to try this by the end of this month.  Stay tuned.

 

Advertisements
Comments
  1. Chris says:

    Was Thinking about doing something this for the same issue when i came across this post, i can confirm that moving the mailbox worked for me, and also that when moving it back again to the original Mailbox database it continued to work.

    Thanks for confirming my thoughts, had previously tried some of the things that you had listed as Didn’t work with the same outcomes, also had tried ticking the inherit permissions tickbox under the security -> Advanced in AD like a lot of posts suggest but this made no difference all good suggestions but they just didn’t work in this scenario.

  2. Glad it worked out for you and happy to learn when my posts have helped others

  3. jjdurrant says:

    Thanks a lot man! Was going crazy trying to figure this one out.. moving mailbox worked great!

  4. Glad I was able to help!

  5. Matt Jones says:

    Has anyone tested to see if moving them back to the old database causes any issues?

  6. Brian says:

    Just wanted to drop a line of thanks to you. We had our Vsphere host do a dirty shutdown (power loss to VM host) and when it came back up we had to do a Database repair. About 6 or 7 devices wouldn’t receive email. I was able to fix most by deleting their activesync device connections, but one stubborn one refused to work.

    Creating a new DB02 and moving him worked like a charm. Thanks!

  7. Easier option.
    In powershell run the command: get-activesyncdevice -mailbox

    Find the identity of the phone you want to remove then run the command:

    remove-activesyncdevice -identity

    I found that the users that i could not manage the mobile device for in the gui had recently been moved OU in AD and the gui was trying to remove the device from the old location where powershell was referencing the correct location.

    Doing it manually this way saves the wait moving to another database

  8. Thanks for that. It is easier. Glad you sorted through all the Powershell commands!

  9. Sean says:

    I have been here two or three times now and you have hit the nail on the head on all occasions. Thanks for saving me hours of headache with your thorough knowledge and research/experimentation. This appears to be the only fix for a corrupt EAS device partnership (other than recreating the mailbox).

  10. I appreciate both the fact that you found this helpful and for your kind comments. Keep coming back! Albeit for less of SBS and more of Beyond.

  11. John says:

    Had the same issue with a Win backup .vhd and came across your post. Thanks for the post. Great info & well written.

  12. Thanks glad to have been helpful

  13. Matt Hadlock says:

    Thanks for the info, I had to rebuild a database and I had users with active sync errors. Creating a new database and moving mailboxes to it worked like a champ.

  14. Glad this was of help to you.

  15. James says:

    This worked for me too! Thank you! I also moved the MBox back to the original DB and it worked like a charm. Happy days.

  16. Glad my post helped you!

  17. Patrick de Vos says:

    Hello,

    Recently we had to repair the mailbox database of a exchange 2010 server. And after that iphones and ipads didn’t activesync anymore. The same symptoms as described in this post.

    I really want to know if someone did the move of the corrupted mailboxes to a temporary database and moved the mailboxes back to the original mailbox database.

    And of course: after te move back to the original mailbox, did activesync work?

  18. Patrick

    That is exactly the scenario I faced prior to writing the blog post, and yes it did work. I hope it works for you as well.

  19. I had the same problem after the repair however I have a user who has a Blackberry Passport and An Apple Ipad, The Ipad kept working and the blackberry did’nt. Also several users where having problems with ipads and Iphones. Except those new users, you just create them from scratch and everything works fine.

    Thanks A Lot Larry!

  20. Glad this helped you

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s