locked
Exchange 2013 CU6 coexistence with Exchange 2007 RU13. ActiveSync don't work. HTTP Error 500 RRS feed

  • Question

  • Hi all.

    In our organization we plan to migrate from Exchange 2007 to Exchange 2013. Exchange 2007 updated to Update Rollup 13.

    Exchange 2013 with CU5 worked normally with Exchange 2007 and users from Exchange 2007 can connect to your mailboxes successfully.

    After updating Exchange 2013 to CU6 users from Exchange 2007 cannot connect to your mailboxes via ActiveSync. All other services work normally.

    Testing Exchange ActiveSync connectivity from web site https://testconnectivity.microsoft.com return error:
    Testing of the OPTIONS command failed.
    An HTTP 500 response was returned from IIS7.

    In IIS log file (on Exchange 2013 server) I see HTTP error 500.

    In IIS log file (on Exchange 2007 server) I see this error:
    2014-09-03 08:43:17 W3SVC1 <Exchange2007_IP> RPC_IN_DATA /rpc/rpcproxy.dll - 443 - <Exchange2013_IP> HttpProxy.ClientAccessServer2010Ping 500 0 0

    When I try to synchronize mobile device
    - mobile device return an error 85010014
    - in Windows Application log on Exchange 2013 server I see event ID 4999:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-03T08:15:56.000000000Z" />
    <EventRecordID>463807</EventRecordID>
    <Channel>Application</Channel>
    <Computer><Exchange_2013_HostName></Computer>
    <Security />
    </System>
    <EventData>
    <Data>20832</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>15.00.0995.029</Data>
    <Data>w3wp#MSExchangeSyncAppPool</Data>
    <Data>M.Exchange.AirSyncHandler</Data>
    <Data>M.E.A.Handler.LegacyUserAllowedToSync</Data>
    <Data>System.InvalidCastException</Data>
    <Data>9619</Data>
    <Data>15.00.0995.026</Data>
    <Data>False</Data>
    <Data>False</Data>
    <Data>w3wp#MSExchangeSyncAppPool</Data>
    <Data />
    </EventData>
    </Event>

    Pls, help to fix this.

     Michael.
    Wednesday, September 3, 2014 8:56 AM

Answers

  • Update (9/5/2014): An Interim Update (IU or Hotfix) is now available for this issue from Microsoft Support (1-800-Microsoft). You have to call and request it as we track these fixes in case of any regressions in future.

    The KB article is now available for this issue.

    You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to E2013 CU6
    http://support.microsoft.com/kb/2997847

    ===========================================

    This is a known issue with Exchange 2013 CU6 at this moment. Microsoft is aware of this issue, and working to investigate it for a root cause & a possible fix. At this time, no ETA is available. I will provide an update here when its available.

    Issue:
    In an E2013 with E2007 co-existence environment, when users with mailboxes on E2007 try to access their mailboxes using Exchange ActiveSync (EAS) going thru E2013 CAS, they are not able to do so after you install E2013 CU6 on E2013 CAS. You will see Event ID 4999 in App Log on E2013 CAS, as mentioned above by Michael. Upon analyzing an ETL trace, we see that an exception is thrown by EAS App Pool on E2013 CAS.

    Workaround:
    A possible workaround could be to bypass the E2013 CAS for such access requests and route them thru an E2007 CAS, which works without any issue. Namespace & other changes may be required to implement this workaround depending on the setup.


    Sr. Program Manager, Product Quality, Exchange Client Access Server




    • Proposed as answer by Amy.Wang Thursday, September 4, 2014 7:18 AM
    • Marked as answer by Michael Dudko Thursday, September 4, 2014 1:09 PM
    • Edited by Amir Haque [MSFT] Tuesday, September 9, 2014 4:22 AM kb available
    Wednesday, September 3, 2014 2:58 PM

All replies

  • Please check this 
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx

    You may have to configure new A record for Exchange 2007 and configure the new name/URLs in exchange 2007 so exchange2013 will do the rest. i.e. proxing and redirection.  
    Autodiscover should be pointed to Exchange2013, ( your user interface will be CAS2013)

    Please check this as well. 
    http://vanhybrid.com/2012/10/09/exchange-2013-interoperability-with-legacy-exchange-versions/


    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.



    • Edited by MAS- Wednesday, September 3, 2014 11:54 AM
    Wednesday, September 3, 2014 11:47 AM
  • Given that the report says that Exchange 2013 CU5 was able to proxy the EAS connections to Exchange 2007 mailboxes and Exchange 2013 CU6 fails, I think that the environment in question probably has its connectivity sorted out and the issue might be with the new cumulative update.

    TR

    Wednesday, September 3, 2014 2:44 PM
  • Update (9/5/2014): An Interim Update (IU or Hotfix) is now available for this issue from Microsoft Support (1-800-Microsoft). You have to call and request it as we track these fixes in case of any regressions in future.

    The KB article is now available for this issue.

    You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to E2013 CU6
    http://support.microsoft.com/kb/2997847

    ===========================================

    This is a known issue with Exchange 2013 CU6 at this moment. Microsoft is aware of this issue, and working to investigate it for a root cause & a possible fix. At this time, no ETA is available. I will provide an update here when its available.

    Issue:
    In an E2013 with E2007 co-existence environment, when users with mailboxes on E2007 try to access their mailboxes using Exchange ActiveSync (EAS) going thru E2013 CAS, they are not able to do so after you install E2013 CU6 on E2013 CAS. You will see Event ID 4999 in App Log on E2013 CAS, as mentioned above by Michael. Upon analyzing an ETL trace, we see that an exception is thrown by EAS App Pool on E2013 CAS.

    Workaround:
    A possible workaround could be to bypass the E2013 CAS for such access requests and route them thru an E2007 CAS, which works without any issue. Namespace & other changes may be required to implement this workaround depending on the setup.


    Sr. Program Manager, Product Quality, Exchange Client Access Server




    • Proposed as answer by Amy.Wang Thursday, September 4, 2014 7:18 AM
    • Marked as answer by Michael Dudko Thursday, September 4, 2014 1:09 PM
    • Edited by Amir Haque [MSFT] Tuesday, September 9, 2014 4:22 AM kb available
    Wednesday, September 3, 2014 2:58 PM
  • Thanks, Amir!

    I also opened ticket in Microsoft support and they gave me the same answer.


    Wednesday, September 3, 2014 3:01 PM
  • hello together, 

    i was running in the same problem at this moment. Same Exchange Versions like mentioned in this thread. We ware doing the Cutover in this moment and i do not want to roll back...

    having the HTTP Error 500. 

    Can you please give us some more information about the possible workarround ?

    Workaround:A possible workaround could be to bypass the E2013 CAS for such access requests and route them thru an E2007 CAS, which works without any issue. Namespace & other changes may be required to implement this workaround depending on the setup.

    do you mean an redirect and to configure the external url of the exchange 2007 servers External URL (like legacy.domain.org) ?

    actually the external url on exchange 2007 is $NULL on the activesync urls... but i'm not 100% sure if such a redirect on activesync does not break the connection on some device types...

    what is your recommendartion ?


    thanks for help, 

    Best,

    Martin

    Friday, September 5, 2014 4:04 PM
  • Martin, a hotfix is now available for this issue, please call Microsoft Support to get that. They can also help you with the implementation of the workaround, if you're interested. Steps may differ depending on your setup, that's why I can't go into details here.

    Sr. Program Manager, Product Quality, Exchange Client Access Server

    Friday, September 5, 2014 5:46 PM
  • What is the hotfix kb #?

    Friday, September 5, 2014 6:15 PM
  • hi i already have a open ticket but microsoft is now "searching" for this hotfix... dont know how long this will take :/

    do you have an KB# ?

    Best, 

    Martin

    Friday, September 5, 2014 6:17 PM
  • another 12 hours later i'm still waiting for this hotfix in an -business critical case- :(

    any tipps how to get this are appreciated :)

    another question about the "workarround": how can it be managed an configured to service both: exchange 2013 and 2007 activesync without using the "bug proxy" for activesync ?


    best, 

    martin

    Saturday, September 6, 2014 6:58 AM
  • Have an answer from Microsoft Partner Support - wait for hotfix with KB2997847.

    Saturday, September 6, 2014 8:58 AM
  • thanks for feedback! 

    Microsoft told me in that moment that the KB Article could be an internal articel KB2997847 / Support cannot read it. 

    apparently the hotfix has to make available from the development. and they are not working on the weekend... they told me to wait till monday :(

    Again one Question about the workarround: 

    Do you think it is possible to Set the ExternalURL (Activesyncvirtualdirectory) for Exchange 2007 again and exchange 2013 will redirect the requests from mobile devices and users from exchange 2007 to this url ?

    I heard often that it depands on the 3rd party vendor if they have implemented this redirect correctly and the active sync configration on the devices could break... 

    The first is ActiveSync. ActiveSync clients do not handle redirection very well, and when prompted to redirect will, in many cases, simply break. Therefore we’ll want to ensure that Exchange 2013 proxies the request to ActiveSync and the client is not made aware of the change.
    
    We’ll accomplish this very simply by setting the External URL to be blank, and filling in the Internal URL with the legacy name. Exchange 2013 will recognize this is set, and act accordingly:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part14.html 

    any experiences with that ?

    any tipps for workarround ?

    thanks, 

    best, 

    martin



    • Edited by -M-T- Saturday, September 6, 2014 10:12 AM change
    Saturday, September 6, 2014 10:06 AM
  • Hello Amir Haque,

    could you please send me this hotfix ? i need it urgently and microsoft is not able to provide this on weekend ?

    you can reach me on:

    martinthiem - at - gmail - dot -   com 

    thanks, best

    martin

    Saturday, September 6, 2014 10:17 AM
  • i received the hotfix in this moment called "Exchange2013-KB2997209_2997847-x64-en.msp" 

    it fixes two issues: KB2997209 and KB2997847

    Best, 

    Martin

    Monday, September 8, 2014 9:42 AM
  • Amir, I started a case with web based support 114090811779407 I was given a workspace so that I can download the file Combined CU6 FIU-en.zip but when I use DTM and login there are no files available.

    I e-mailed back the contact and received and automated response saying his work schedule is Sunday to Thursday is there anyway I can get this file before he gets back?

    Monte

    Friday, September 12, 2014 4:09 PM
  • just drop me an email where i should send it

    martinthiem - at - gmail - dot -   com 

    its about 33MB. 

    Best, 

    Martin

    Friday, September 12, 2014 4:15 PM
  • Hello togehter, 

    if anyone is using the Interim Update (Hotfix) "Exchange2013-KB2997209_2997847-x64-en.msp" please be aware of the following bug in this hotfix: 

    NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you run into related issues:

    • -Backup the contents of “15.0.995.31” folder to a different folder/directory
    • -Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …


      Best, 

      Martin


    Friday, September 12, 2014 4:24 PM
  • Monte, I see contact info for his manager in the emails that he has sent to you, please contact him. I am sorry but I am unable to fix the hotfix site access issue for you as I don't have access to it. Alternatively, you can call back in at 1-800-Microsoft and talk to an available engineer to get the fix. HTH.

    Sr. Program Manager, Product Quality, Exchange Client Access Server

    Friday, September 12, 2014 6:21 PM