locked
Exchange 2010 - iPhones/iPads - ActiveSync error 1008 RRS feed

  • Question

  • We have recently migrated to Exchange 2010 sp1 from Exchange 2003.  Since the migration we have issues with multiple IOS devices (iPhone/iPads) and ActiveSync.  The issue we are seeing device side is mail will remain stuck in the outbox or the device will fail to connect to the server properly to retrieve mail.  This is only experienced on a few of our total IOS devices and not all of them.  The server side shows a generic error 1008 with the following context:

     

    Log Name:      Application
    Source:        MSExchange ActiveSync
    Date:          6/29/2011 9:28:50 AM
    Event ID:      1008
    Task Category: Requests
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      cai-mail-s01.commandalkon.local
    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.
    Exception level: 0
    Exception stack trace:    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size)
       at System.Web.HttpRequest.GetEntireRawContent()
       at System.Web.HttpRequest.get_InputStream()
       at Microsoft.Exchange.AirSync.AirSyncRequest.get_InputStream()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows below:
    Exception type: System.Runtime.InteropServices.COMException
    Exception message: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)
    Exception level: 1
    Exception stack trace:
    --- Exception end ---.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ActiveSync" />
        <EventID Qualifiers="32772">1008</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-29T14:28:50.000000000Z" />
        <EventRecordID>59353</EventRecordID>
        <Channel>Application</Channel>
        <Computer>cai-mail-s01.commandalkon.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>/Microsoft-Server-ActiveSync/default.eas?User=xxxxx&amp;DeviceId=Appl70111HXKA4S&amp;DeviceType=iPhone&amp;Cmd=SendMail</Data>
        <Data>--- Exception start ---
    Exception type: System.Web.HttpException
    Exception message: An error occurred while communicating with the remote host. The error code is 0x800703E3.
    Exception level: 0
    Exception stack trace:    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size)
       at System.Web.HttpRequest.GetEntireRawContent()
       at System.Web.HttpRequest.get_InputStream()
       at Microsoft.Exchange.AirSync.AirSyncRequest.get_InputStream()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows below:
    Exception type: System.Runtime.InteropServices.COMException
    Exception message: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)
    Exception level: 1
    Exception stack trace:
    --- Exception end ---</Data>
      </EventData>
    </Event>

     

    The error server side seems to follow the device side issue of email being very slow to send or never actually sending at all.  We have tried restoring a few of these devices to factory settings by reloading the IOS but no effect from that. 

    Also the exchange testing utilities shows everything green and shows no external issues with activesync using this users account.  We have also checked to make sure inheritable permissions are checked and they are for all users.

     

    Please help !!

    Wednesday, June 29, 2011 2:58 PM

Answers

  • We actually seem to have found the solution on accident.  During the move to the new exchange server we had put it behind a new firewall that had SYN Cookies enabled.  Disabling those seems to have fixed the problem entirely.

     

    • Marked as answer by chadeldridge Wednesday, August 10, 2011 1:08 PM
    Wednesday, August 10, 2011 1:08 PM
  • Have you removed the ActiveSync partnership from the account? Wiping the device isn't enough, and the error points to a problem there.
    I would suggest removing the partnership through OWA and then setting it up fresh. Particularly if that hasn't happened since the mailbox came across from 2003.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    • Proposed as answer by James Xiong Wednesday, July 6, 2011 5:50 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Wednesday, June 29, 2011 7:24 PM
  • Hi,

     

    From the problem description, I understand that you are experiencing flood of Event ID 1008 on your CAS server. Just like the detailed information in the Event Viewer, It’s the warning code of the relationship between the client and the server. No user action is required; Exchange will re-create a partnership with the mobile device.

     

    This Warning event indicates that an exception occurred during the Microsoft Exchange ActiveSync synchronization process. The event description includes details about the root cause of the problem. The following are possible causes of this event:

     

    ·         The partnership configuration for this device was created by using computer that is running an earlier version of Microsoft Exchange. The partnership cannot be used. This problem may occur after you upgrade a computer to Exchange Server 2010. Exchange will update the partnership on the Exchange server. After the partnership is updated, all the data configured for synchronization in the partnership will be resynchronized.

    ·         The partnership configuration for this device is damaged. Exchange will update the partnership on the Exchange server. After the partnership is updated, all of the data configured for synchronization in the partnership will be resynchronized.

    ·         A user has accessed the same item from multiple computers or mobile devices. For example, this may occur if a user tries to reply to a message on their mobile device after that device has been deleted on the user's desktop computer that runs Microsoft Outlook 2010. This will be corrected the next time that the user synchronizes their device.

     

    To resolve this warning, do one or more of the following:

     

    ·         If this error was caused by an outdated partnership or a damaged partnership, no user action is required. Exchange will re-create a partnership with the mobile device.

    ·         Make sure that the user has an Exchange mailbox and that the user has been enabled for Exchange ActiveSync. For more information, see Enable or Disable Exchange ActiveSync for a Mailbox User.

    ·         Wait for Active Directory replication to occur.

     

    For more detailed information, please refer to the link below:

     

    Title: An exception occurred and was handled by Exchange ActiveSync

    URL: http://technet.microsoft.com/en-us/library/ff360693(EXCHG.140).aspx

     

    Thx,

    James


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by James Xiong Wednesday, July 6, 2011 5:50 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Thursday, June 30, 2011 8:22 AM
  • I never found a solution so, I ended up backing up the users EMAIL (pst) then, I deleted and readded the user and everything was working again!
    • Proposed as answer by James Xiong Friday, August 5, 2011 5:57 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Monday, July 25, 2011 12:19 AM

All replies

  • Have you removed the ActiveSync partnership from the account? Wiping the device isn't enough, and the error points to a problem there.
    I would suggest removing the partnership through OWA and then setting it up fresh. Particularly if that hasn't happened since the mailbox came across from 2003.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    • Proposed as answer by James Xiong Wednesday, July 6, 2011 5:50 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Wednesday, June 29, 2011 7:24 PM
  • Hi,

     

    From the problem description, I understand that you are experiencing flood of Event ID 1008 on your CAS server. Just like the detailed information in the Event Viewer, It’s the warning code of the relationship between the client and the server. No user action is required; Exchange will re-create a partnership with the mobile device.

     

    This Warning event indicates that an exception occurred during the Microsoft Exchange ActiveSync synchronization process. The event description includes details about the root cause of the problem. The following are possible causes of this event:

     

    ·         The partnership configuration for this device was created by using computer that is running an earlier version of Microsoft Exchange. The partnership cannot be used. This problem may occur after you upgrade a computer to Exchange Server 2010. Exchange will update the partnership on the Exchange server. After the partnership is updated, all the data configured for synchronization in the partnership will be resynchronized.

    ·         The partnership configuration for this device is damaged. Exchange will update the partnership on the Exchange server. After the partnership is updated, all of the data configured for synchronization in the partnership will be resynchronized.

    ·         A user has accessed the same item from multiple computers or mobile devices. For example, this may occur if a user tries to reply to a message on their mobile device after that device has been deleted on the user's desktop computer that runs Microsoft Outlook 2010. This will be corrected the next time that the user synchronizes their device.

     

    To resolve this warning, do one or more of the following:

     

    ·         If this error was caused by an outdated partnership or a damaged partnership, no user action is required. Exchange will re-create a partnership with the mobile device.

    ·         Make sure that the user has an Exchange mailbox and that the user has been enabled for Exchange ActiveSync. For more information, see Enable or Disable Exchange ActiveSync for a Mailbox User.

    ·         Wait for Active Directory replication to occur.

     

    For more detailed information, please refer to the link below:

     

    Title: An exception occurred and was handled by Exchange ActiveSync

    URL: http://technet.microsoft.com/en-us/library/ff360693(EXCHG.140).aspx

     

    Thx,

    James


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by James Xiong Wednesday, July 6, 2011 5:50 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Thursday, June 30, 2011 8:22 AM
  • @Sembee

    I do notice several identical iphones listed on a few of the accounts having this issue.  I have removed them and then readded the mail accounts to a few of the effected units.  However the problem still persists.  Mail sticks in the Outbox and spins forever.  Once the mail is deleted from the outbox then normal incoming messages resume to the device, but until the outbound either sends or is deleted the device is stuck in a sending loop.

     

    @James

    I had read all those items already however the issue does not self correct itself and even after deleting the devices associated with the user and trying again the issue still occurs.  I am not overly worried about the 1008 errors as long as the iphones show normal activity but they are not.  Sending mail is a serious problem resulting in stuck messages on a lot of devices.  I have also tried to remove and re-enable active sync from the user and that has no effect either. 

     

    Any other thoughts??

    Thursday, June 30, 2011 12:40 PM
  • I never found a solution so, I ended up backing up the users EMAIL (pst) then, I deleted and readded the user and everything was working again!
    • Proposed as answer by James Xiong Friday, August 5, 2011 5:57 AM
    • Marked as answer by James Xiong Tuesday, August 9, 2011 9:36 AM
    Monday, July 25, 2011 12:19 AM
  • We actually seem to have found the solution on accident.  During the move to the new exchange server we had put it behind a new firewall that had SYN Cookies enabled.  Disabling those seems to have fixed the problem entirely.

     

    • Marked as answer by chadeldridge Wednesday, August 10, 2011 1:08 PM
    Wednesday, August 10, 2011 1:08 PM
  • You have to enable inherit permissions under security Tab in AD user account viewing by advanced features. 
    Tuesday, November 15, 2011 3:48 PM
  • You have to enable inherit permissions under security Tab in AD user account viewing by advanced features. 

    It wotks for me
    Wednesday, July 17, 2013 12:05 PM
  • This did the trick for me as well.
    Thursday, January 30, 2014 5:14 PM