Exchange 2013 coexistence with 2010

Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:

  • Autodiscover would fail for 2010 users but fine for 2013 users:
    HTTP Response Headers:
    request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
    X-CasErrorCode: ServerNotFound
    Persistent-Auth: true
    X-FEServer: CPC8000-CAS01
    Content-Length: 0
    Cache-Control: private
    Date: Sun, 01 Jun 2014 01:22:50 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 153 ms

and

Created a new user on 2010 and login to OWA does this:

Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException

I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:

  • Checked AD Replication and it was fine
  • Exchange 2013 was at SP1
  • Exchange 2010 was at SP3 Rollup 6
  • Exchange 2010 was a single server with CAS/HUB/Mailbox
  • Exchange 2010 was not using a CAS Array
  • Exchange 2013 had two mailbox servers in a DAG and one CAS server
  • I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
  • https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
  • I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added

Would really love some input to see what I did wrong. Thank you!

June 1st, 2014 10:44am

Hi,

To narrow down the cause , I'd like to confirm the following information and recommend the following troubleshooting:

1. The internal URLs for OWA in your Exchange 2010 server.

2. The detail error in the connectivity test of Autodiscover by ExRCA.

3. Check if there is any related error in event log.

Thanks

Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2014 11:49am

Thanks for responding!

The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all. 

Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server

The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:

  • HTTP Response Headers:
    request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
    X-CasErrorCode: ServerNotFound
    Persistent-Auth: true
    X-FEServer: CPC8000-CAS01
    Content-Length: 0
    Cache-Control: private
    Date: Sun, 01 Jun 2014 01:22:50 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 153 ms

June 3rd, 2014 2:30pm

Did you ever resolve this issue?  Can you recall what the problem was.

I'm getting the same issue on a 2010/2013 coexistence.  Proxy on OWA not working and error is servernotfound

Thanks in advance.

Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 5:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics