Microsoft Developer Network > 포럼 홈 > Using the Exchange Server Protocols > Question re: ActiveSync "Sync" command and status 3 error...
질문하기질문하기
 

답변됨Question re: ActiveSync "Sync" command and status 3 error...

  • 2009년 6월 30일 화요일 오전 12:36BHAssoc 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    Here's what I'm doing:

    1) Send a Sync command for Inbox with syncKey = 0 (first sync)
    2) Receive syncKey = 1 (as expected)
    3) Send Sync command with syncKey = 1
    4) Receive new syncKey = 2 (as expected) and start processing Emails.

    Now, I interrupt my executing code at this point - i.e. before I finish with the first window of Emails (say, simulating a connection error).   When I try to sync next, I basically go back to #2, sending syncKey = 1 (which is the last one I've gotten successfully, i.e. I never finished receiving the result from the first window full of data).    The result is a status of 3, which indicates that I have to throw away any data I've received and start over with step 1.

    Is this correct?   If so, it would seem that a connection error after having received thousands of messages would cause me to have to get them all over again.   Or am I missing something?

    Any help would be greatly appreciated.

    -BHAssoc

답변

  • 2009년 7월 20일 월요일 오후 2:51Mark Miller_DSCMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨

    Hello BHAssoc,

    Support for Exchange Server Protocols fall under the
    Interoperability Principles.  Interoperability Principles covers client protocols to interoperate with Exchange Server 2007 and greater.   The version of Exchange ActiveSync (EAS) that are supported by this forum are 12.0 and greater.

     

    If you require additional support for earlier versions of EAS, such as 2.5 that ships with Exchange 2003, this is handled as a paid service engagement with Microsoft Partner Advantage Services (MSPA).

    Regards,
    Mark Miller
    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

모든 응답

  • 2009년 6월 30일 화요일 오후 2:16Hongwei Sun-MSFTMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    BHAssoc,

       Thanks for your question.  One of out team member will work on your question and get back to you soon.

    Thanks!
    Hongwei Sun -MSFT
  • 2009년 7월 6일 월요일 오후 4:15BHAssoc 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    Thanks; what sort of timeframe should I expect (it's been about a week now)?

    -BHA
  • 2009년 7월 7일 화요일 오후 2:36Tom Jebo_DSCMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    BHAssoc,

    I've taken ownership of your case and will try to get you a response in the next couple of days.  Thanks for your patience!


    Regards, Tom Jebo Senior Support Escalation Engineer Microsoft DS Protocol Team
  • 2009년 7월 7일 화요일 오후 3:52BHAssoc 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    Great, thanks!

    BHA
  • 2009년 7월 13일 월요일 오후 8:28Mark Miller_DSCMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     

    Hello BHAssoc,

     

    You should be able to use SyncKey = current, or SyncKey = current – 1, but you can't use SyncKey = current - 2.

     

    Consider this pattern:

     

    1) Sync Inbox - SyncKey = 0 - Returns Synckey of 1 and no items.

    2) Sync Inbox - SyncKey = 1 - Returns Synckey of 2 and n number of items.

    3) Sync Inbox - SyncKey = 1 - Returns Synckey of 2 and n number of items.

     

    If you are encountering something different that what is described above please send sync logs and I will investigate further.

     

    Regards,
    Mark Miller
    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

  • 2009년 7월 15일 수요일 오전 4:25BHAssoc 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    Hi, Mark.

    I don't think this is what I'm seeing, at least with EAS 2.5.   Could you tell me what kind of logs you'd like, so I can ask my server admin to get them for you?

    Thanks!

    Marc
  • 2009년 7월 20일 월요일 오후 2:51Mark Miller_DSCMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨

    Hello BHAssoc,

    Support for Exchange Server Protocols fall under the
    Interoperability Principles.  Interoperability Principles covers client protocols to interoperate with Exchange Server 2007 and greater.   The version of Exchange ActiveSync (EAS) that are supported by this forum are 12.0 and greater.

     

    If you require additional support for earlier versions of EAS, such as 2.5 that ships with Exchange 2003, this is handled as a paid service engagement with Microsoft Partner Advantage Services (MSPA).

    Regards,
    Mark Miller
    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM