locked
Protocol Error using Exchange server 2007 with SP1 RRS feed

  • Question

  • Hi,

     

    Am facing an error "Protocol error"  while sending the initial Sync command for Exchange server 2007 with SP1. Here i have used the headers as

     https://e2k7.wds.vzw.com:443/Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&User=remotest08&DeviceId=953482700&DeviceType=gzoneC741

    Content-Type: application/vnd.ms-sync.wbxml
    MS-ASProtocolVersion: 12.1
    User-Agent: Remoba-gzoneC741/4.0.01.01
    Authorization: Basic YXRsYW50aWNccmVtb3Rlc3QwODpyZW0wJHluYw==
    X-MS-PolicyKey: 3240803815 

    <?xml version="1.0" encoding="utf-8"?>

    <Sync xmlns="AirSync:">

      <Collections>

        <Collection>

          <Class>Email</Class>

          <SyncKey>0</SyncKey>

          <CollectionId>5</CollectionId>

          <DeletesAsMoves/>

        </Collection>

      </Collections>

    </Sync>

     

    For the above request am getting Protocol Error for 2007 with SP1. If i use 12.0 then the am getting an issue 403 error for FolderSync command.

     

    Please check and let me know what could be the error in client protocol.

     

    Thanks,

    Sirisha

    Monday, March 29, 2010 6:51 AM

Answers

  • Sirisha,

    Based on the information provided, I cannot sufficiently proceed to answer your question. I do not see anything particular wrong with the Sync you pasted, however, I will need to see the full sync and the actual response from the server to determine the issue. I may need to see some packets that occured previous to the sync to understand what went wrong.

    However, if you review MS-ASHTTP, you will see the following in Section 2.2.2.1.1 Status Line : "403 Forbidden -- The user is not enabled for ActiveSync synchronization. For details about how to troubleshoot this error, see section 2.2.2.1.1.2."

    Now, jumping down to the aforementioned section in the note, you will see this:

    2.2.2.1.1.2   Troubleshooting Tip

    The client SHOULD send an Autodiscover command request to the server if any of the following
    HTTP errors are encountered:

    • 401
    • 403
    • 500

    If the user's mailbox has moved, if the client is trying to connect to a server that cannot access the
    user’s mailbox, or if there is a more efficient server to use to reach the user’s mailbox, then the
    server MUST respond to any command request with error code 451 and include the URL of a
    preferred server in the exception message. The device MUST redirect all future requests to the 
    preferred server by using the URL that was provided. For all other status codes (401, 403, 500), or
    if the URL is not specified with the 451 status code, then the full Autodiscover command process is
    followed, as specified in [MS-ASCMD].
    The HTTP OPTIONS command is the first command that is sent to the preferred server.

    Is this information sufficient?

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team

    Monday, March 29, 2010 7:13 PM

All replies

  • Hi Sirisha,

    Thanks for your question regarding Exchange Active Sync and the 403 error.  One the Open Specifications Documentation team will be in touch with you shortly.

    Tom Jebo

    Microsoft Open Specifications Documentation Support

    Monday, March 29, 2010 12:20 PM
  • Hey Sirisha,

    I am the engineer who has taken ownership of your issue. I am currently investigating this and will update you as things progress.

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team

    Monday, March 29, 2010 3:29 PM
  • Greetings Sirisha,

    Could you send me a network trace regarding the behavior you are experiencing to dochelp (at) winse.microsoft.com ?

    Thank you.

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team
    Monday, March 29, 2010 3:33 PM
  • I am sorry, i can't trace the network. Since the Exchange account belongs to a client. Only one thing am not understand.....the same protocol works perfectly fine with 2007 and 2003 a/c. This issue i am facing is with 2007 SP1. also i tested this account with different platform BREW it's working fine, but when i am checking with Android am facing this issue. Please help me.

    Thanks,

    Sirisha

     

    Monday, March 29, 2010 6:15 PM
  • Sirisha,

    Based on the information provided, I cannot sufficiently proceed to answer your question. I do not see anything particular wrong with the Sync you pasted, however, I will need to see the full sync and the actual response from the server to determine the issue. I may need to see some packets that occured previous to the sync to understand what went wrong.

    However, if you review MS-ASHTTP, you will see the following in Section 2.2.2.1.1 Status Line : "403 Forbidden -- The user is not enabled for ActiveSync synchronization. For details about how to troubleshoot this error, see section 2.2.2.1.1.2."

    Now, jumping down to the aforementioned section in the note, you will see this:

    2.2.2.1.1.2   Troubleshooting Tip

    The client SHOULD send an Autodiscover command request to the server if any of the following
    HTTP errors are encountered:

    • 401
    • 403
    • 500

    If the user's mailbox has moved, if the client is trying to connect to a server that cannot access the
    user’s mailbox, or if there is a more efficient server to use to reach the user’s mailbox, then the
    server MUST respond to any command request with error code 451 and include the URL of a
    preferred server in the exception message. The device MUST redirect all future requests to the 
    preferred server by using the URL that was provided. For all other status codes (401, 403, 500), or
    if the URL is not specified with the 451 status code, then the full Autodiscover command process is
    followed, as specified in [MS-ASCMD].
    The HTTP OPTIONS command is the first command that is sent to the preferred server.

    Is this information sufficient?

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team

    Monday, March 29, 2010 7:13 PM