I recently started a migration from Exchange 2003 to Exchange 2010 SP3. Exchange 2010 is running on Windows Server 2012. Everything is working as usual except Exchange 2010 users cannot see Exchange 2003 users' FREE\BUSY info. Exchange
2010 users also cannot download the OAB. I ran Test-OutlookWebServices and here are the results:
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object ishttps://FS
EX2010.mydomain.com/Autodiscover/Autodiscover.xml.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://FSEX2010.mydomain.com/Autodiscover/Autodiscover.xml received the error The underly
ing connection was closed: An unexpected error occurred on a send.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://FSEX2010.mydomain.com/Autodiscover/Autodiscover.xml received the error Unable to r
ead data from the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://FSEX2010.mydomain.com/Autodiscover/Autodiscover.xml received the error An existing
connection was forcibly closed by the remote host
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1023
Type : Error
Message : The Autodiscover service couldn't be contacted.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error The underlying connecti
on was closed: An unexpected error occurred on a send.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error Unable to read data fro
m the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error An existing connection
was forcibly closed by the remote host
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at
https://fsex2010.mydomain.com/EWS/Exchange.asmx. Elapsed time wa
s 2 milliseconds.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error The underlying connecti
on was closed: An unexpected error occurred on a send.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error Unable to read data fro
m the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/EWS/Exchange.asmx received the error An existing connection
was forcibly closed by the remote host
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1027
Type : Error
Message : [EXCH] Error contacting the UM service at
https://fsex2010.mydomain.com/EWS/Exchange.asmx. Elapsed time wa
s 1 milliseconds.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://exchange.mydomain.com/ews/exchange.asmx received the error The request failed with
HTTP status 404: Not Found.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at
https://exchange.mydomain.com/ews/exchange.asmx. Elapsed time wa
s 145 milliseconds.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1013
Type : Error
Message : When contacting
https://exchange.mydomain.com/ews/exchange.asmx received the error The remote server retur
ned an error: (404) Not Found.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1027
Type : Error
Message : [EXPR] Error contacting the UM service at
https://exchange.mydomain.com/ews/exchange.asmx. Elapsed time wa
s 1 milliseconds.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error The underlying connecti
on was closed: An unexpected error occurred on a send.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error Unable to read data fro
m the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error An existing connection
was forcibly closed by the remote host
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1125
Type : Error
Message : [Server] Error contacting the AS service at
https://fsex2010.mydomain.com/ews/exchange.asmx. Elapsed time
was 2 milliseconds.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error The underlying connecti
on was closed: An unexpected error occurred on a send.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error Unable to read data fro
m the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1113
Type : Error
Message : When contacting
https://fsex2010.mydomain.com/ews/exchange.asmx received the error An existing connection
was forcibly closed by the remote host
RunspaceId : 54773cde-dedc-4593-b02a-b818991cae98
Id : 1127
Type : Error
Message : [Server] Error contacting the UM service at
https://fsex2010.mydomain.com/ews/exchange.asmx. Elapsed time
was 2 milliseconds.
Additional info:
The 2010 server is using a Wildcard cert (*.mydomain.com)
The external name used by the Exchange users is exchange.mydomain.com. This name still resolves to the 2003 on the internal DNS, so I expect the 404 errors onhttps://exchange.mydomain.com queries.
I've done dozens of 2003 to 2010 migrations, never had a problem with web services. This is the first Exchange 2010 installation to use Server 2012, but I have done a proof of concept lab with Server 2012 and there were no problems.
I have searched on the specific errors "existing connection was forcibly closed" and "unexpected error on send" and the resolutions offered come down to two things:
Is AutoDiscover configured properly? - Yes, I believe so. Clients can connect to the server without a problem.
Here is the autodiscover virtual directory config:
[PS] C:\Windows\system32>get-autodiscovervirtualdirectory | fl
RunspaceId : 2ec15265-7b43-44c5-8cfd-1a649aedd1d7
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://FSEX2010.mydomain.com/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : FSEX2010
InternalUrl :https://fsex2010.mydomain.com/autodiscover/autodiscover.xml
ExternalUrl :
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=FSEX2010,CN=Servers,CN=Exc
hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=MyCompany Con
struction Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyCompany,DC=b
iz
Identity : FSEX2010\Autodiscover (Default Web Site)
Guid : 61cfd957-c0a0-42b5-bb7e-c41d3255331f
ObjectCategory : mydomain.com/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 6/15/2013 7:24:23 AM
WhenCreated : 6/11/2013 9:33:29 AM
WhenChangedUTC : 6/15/2013 11:24:23 AM
WhenCreatedUTC : 6/11/2013 1:33:29 PM
OrganizationId :
OriginatingServer : fsmail.mydomain.com
IsValid : True
The second resolution is to patch dotNet Framework 1.1.
OWA works, clients can get to their Outlook profile using autodiscover. Clients cannot access the availability service nor can they download the OAB.
At this point I'm hoping someone can point out the simple thing I've overlooked.
Comments and suggestions welcome.