Hi everyone,

I'm having an issue with ActiveSync in my new Exchange 2013 environment. I have two mailbox servers and two CAS servers. When I run the ActiveSync test on the Remote Connectivity Analyzer, all of the autodiscover pieces work, but the actual ActiveSync FolderSync command fails with the below error: 

Exception details:
Message: The request was aborted: The request was canceled.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()
Elapsed Time: 156 ms.

I then attempted to run the Test-ActiveSyncConnectivity cmdlet, but that also fails with the below error:

RunspaceId                  : 616f4a97-8771-4198-bf15-46b97f510748
LocalSite                   : Default-First-Site-Name
SecureAccess                : True
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 0
ConnectionType              : Plaintext
ClientAccessServerShortName : <Mailbox server>
LocalSiteShortName          : Default-First-Site-Name
ClientAccessServer          : <Mailbox server FQDN>
Scenario                    : Options
ScenarioDescription         : Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
PerformanceCounterName      : DirectPush Latency
Result                      : Failure
Error                       : The OPTIONS command returned HTTP 200, but the Exchange ActiveSync header
                              (MS-Server-ActiveSync) wasn't returned. The request likely did not reach a Client Access
                              server, either because

                               - A proxy server intervened (check the headers below for any that may have been
                              returned by a proxy)

                               -The virtual directory could not be reached:
                              https://<Mailbox server FQDN>/Microsoft-Server-ActiveSync

                               - The virtual directory does not point to a Client Access server:
                              https://<Mailbox server FQDN>/Microsoft-Server-ActiveSync

                              HTTP response headers:

                              Allow: OPTIONS, TRACE, GET, HEAD, POST
                              Public: OPTIONS, TRACE, GET, HEAD, POST
                              Content-Length: 0
                              Date: Sat, 11 Apr 2015 18:24:56 GMT
                              Server: Microsoft-IIS/8.5
                              X-Powered-By: ASP.NET


UserName                    : extest_3ee46948de9e4
StartTime                   : 4/11/2015 2:24:57 PM
Latency                     : -00:00:01
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True
ObjectState                 : New

I believe the issue is with the test looking at the mailbox server where the test account is located, and not a CAS server. I'm not sure why the test thinks the mailbox server is a CAS server, but this seems like it would certainly cause what I'm seeing. The ActiveSync directory doesn't exist on the mailbox servers since the CAS servers are in place. 

Any ideas on this? I'm a bit stumped why ActiveSync seems to not understand there are dedicated CAS servers. Autodiscover works fine as well as Outlook connectivity using MAPI/HTTP. Only ActiveSync seems to be nonfunctional. 

Thanks!

-MRCUR

Exception details: Message: The request was aborted: The request was canceled. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() Elapsed Time: 156 ms.

Exception details: Message: The request was aborted: The request was canceled. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() Elapsed Time: 156 ms.

Exception details: Message: The request was aborted: The request was canceled. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() Elapsed Time: 156 ms.

In 2013, the CAS only proxies the connection, so yes it will look to the Mailbox Server because that is where the actual connection and processing takes place.

Thanks Andy. Is there any way to use the test-activesyncconnectivity cmdlet when the MBX & CAS roles are separated? So far I haven't been able to successfully use the command.