Open Specifications Developer Center > Open Specifications Forums > Using the Exchange Server Protocols > How to handle the occasional satus that Exchange server 2007 always return 'MoreAvailable'
Ask a questionAsk a question
 

Proposed AnswerHow to handle the occasional satus that Exchange server 2007 always return 'MoreAvailable'

  • Friday, October 30, 2009 6:31 AMLeoLoveEAS Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I meet one issue about server response 'MoreAvailable" from Exchange Server 2007.

    In daily use of syncing of exchange server 2007, E2K7 server occasionally returns 'MoreAvailable' to EAS client. But there are nothing sync'd to device in this Sync command and next Sync command.

    Due to this, some issues are met:
    1, EAS device falls into a dead loop because of 'MoreAvailable'.
    2, Server will always return 'MoreAvailable', but doesn't return real data to device. It will lead that new email can not be synced timely.But sometimes, server can recover after while.

    Who can help me to resolve above problem? Or is it just server issue, will be update in later release?

All Replies

  • Friday, October 30, 2009 3:16 PMHongwei Sun-MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Hi,

        Thanks for your post, however this is not the correct forum to get your question answered. This forum is for supporting Microsoft Open Protocol Documentation.

       Please re-post your question at the following forum and they should be able to assist you:

        http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/threads


    Thanks!

    Hongwei Sun -MSFT
  • Thursday, November 05, 2009 4:04 AMBHAssoc Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    No, the poster is in the right place.

    He's asking about a problem with ActiveSync (EAS 12.0, at the least) in which a Sync command returns <MoreAvailable/> in a looping situation (i.e. indicating more available, but there never is).   This prevents proper push behavior in the EAS client.

    Could somebody please take a look at this?

    Thanks.

    Marc

    p.s. Dominic, are you here?
  • Wednesday, November 11, 2009 8:58 PMDominic Salemno MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Marc,

    Another engineer has taken ownership of your issue. This engineer will be following up with you very shortly in regards to this issue.

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team
  • Wednesday, November 11, 2009 11:15 PMMark Miller_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi BHAssoc/LeoLoveEAS,

    I am filing a document bug for this behavior.  A behavior note will be added for [MS-ASCMD] to clarify that the server will send multiple <MoreAvailable/> responses without any changes when it encounters out of schema properties.  The current documentation implies you only see non-empty <MoreAvailable/> responses.

    Regards,
    Mark Miller
    Escalation Engineer
    US-CSS DSC PROTOCOL TEAM

     

  • Wednesday, November 11, 2009 11:21 PMBHAssoc Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi, Mark.

    Can you explain this further?  What can we do to prevent looping when we see this behavior?  I suspect that most EAS clients will send the sync key and ask for changes when <MoreAvailable>1</MoreAvailable> is seen in a sync response.

    Thanks,

    Marc
  • Monday, November 16, 2009 8:33 PMBHAssoc Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Ping!

    Marc
  • Thursday, November 19, 2009 6:14 PMMark Miller_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Marc,

    I haven't forgotten about you.  I am working on an answer for you and will hopefully have one shortly.

    Regards,
    Mark Miller
    Escalation Engineer
    US-CSS DSC PROTOCOL TEAM