Autodiscover fails

[teqmod]

Working on a server 2012/Exchange 2010SP3 system. This is an upgrade from Exchange 2003 and in place. We have the server installed and 5 test users on the system and the users are able to connect and send/receive mail without issue. The problem is that some users are being prompted for credentials. Investigating this led to seeing errors with the AutoDiscover as follows:

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is

https://internal.company.int/autodiscover/autodiscover.xml.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1013
Type : Error
Message : When contacting

https://internal.company.int/autodiscover/autodiscover.xml

received the error The remote server returned an error: (500) Internal Server Error.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1023
Type : Error
Message : The Autodiscover service couldn't be contacted.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1013
Type : Error
Message : When contacting

https://internal.company.int/EWS/Exchange.asmx

received the error Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at

https://internal.company.int/EWS/Exchange.asmx.

Elapsed time was 469 milliseconds.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1026
Type : Success
Message : [EXCH] Successfully contacted the UM service at

https://internal.company.int/EWS/Exchange.asmx.

The elapsed time was 187 milliseconds.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1013
Type : Error
Message : When contacting

https://mail.external.com/ews/exchange.asmx

received the error The remote name could not be resolved: 'mail.external.com'

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at

https://mail.external.com/ews/exchange.asmx.

Elapsed time was 0 milliseconds.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1013
Type : Error
Message : When contacting

https://mail.external.com/ews/exchange.asmx

received the error The remote name could not be resolved: 'mail.external.com'

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1027
Type : Error
Message : [EXPR] Error contacting the UM service at

https://mail.external.com/ews/exchange.asmx.

Elapsed time was 0 milliseconds.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1113
Type : Error
Message : When contacting

https://internal.company.int/ews/exchange.asmx

received the error Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1125
Type : Error
Message : [Server] Error contacting the AS service at

https://internal.company.int/ews/exchange.asmx.

Elapsed time was 31 milliseconds.

RunspaceId : 97cca46c-ca1d-48a1-84bc-9e4ccd9f5bee
Id : 1126
Type : Success
Message : [Server] Successfully contacted the UM service at

https://internal.company.int/ews/exchange.asmx.

The elapsed time was 31 milliseconds.

This server is not externally facing at this time. OWA works properly. I have tried deleting and recreating hte Autodiscover Virtual Directory with no success. Has anyone seen any issues like this?

 

[teqmod]

One thing I have done is turned off the Windows firewall which has made it so I can now browse to email.mydomain.int/Autodiscover/autodiscover.xml. This is what I receive when browsing through IE
<?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="

http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

- <Response>
- <Error Time="16:04:13.4551718" Id="1227593931">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData />
</Error>
</Response>
</Autodiscover>

From what I read a "600" error is good but I am still receiving 500 errors through Outlook when testing the connection to the Exchange server

 

[ShackDaddy]

Did you install any local antivirus on the server before installing Exchange? That commonly screws things up with IIS availability. If you did, just uninstall it and reinstall it, and that often resolves the issues.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[Ali147gta]

When you say 500 errors through Exchange is that Outlook or OWA ?

iMachiavellian - think dissident

 

[teqmod]

Issue resolved.

The 500 errors were coming when testing the Autodiscover in Outlook. (CTRL Right click on the Outlook icon in the task bar)

Issue was this:
A seperate site using host headers had been set up. The certificate was never applied to the default site just the sites with Host Headers. I removed these sites and added the certificate to the default. I read that OWA does not play well with multiple sites and there actually was an error in the event log that showed up after removing the firewall that pointed me to this. Following removing the additional sites AutoDiscover worked and OOF worked through Outlook but not through OWA. At this point I had to remove the ECP Virtual directory and recreate it. After recreation OOF worked in OWA as well.