none
autodiscover.xml failed 0x800c8203

    Question

  • Autodiscover is not working on our Exchange 2010 Server, which has broken OOF. Here is the results of the autodiscover test.

    Attempting Url https://myserver.com/autodiscover/autodiscover.xml found through SCP

    Autodiscover to https://myserver.com/autodiscover/autodiscover.xml starting

    Autodiscover to https://myserver.com/autodiscover/autodiscover.xml FAILED (0x800C8203)

    Autodiscover to https://myserver.com/autodiscover/autodiscover.xml starting

    Autodiscover to https://myserver.com/autodiscover/autodiscover.xml FAILED (0x800C8203)

    Autodiscover to https://autodiscover.myserver.com/autodiscover/autodiscover.xml/ starting

    Autodiscover internet timeout against URL https://autodiscover.bgcmanatee.org/autodiscover/autodiscover.xml

    Autodiscover internet timeout against URL https://autodiscover.bgcmanatee.org/autodiscover/autodiscover.xml

    Autodiscover to https://autodiscover.myserver.com/autodiscover/autodiscover.xml FAILED (0x800C8203)

    Local Autodiscover for mysite.com starting

    Local Autodiscover for mysite.com FAILED (0x8004010F)

    Redirect check to http://autodiscover.mysite.com/autodiscover/autodiscover.xml starting

    Redirect check to http://autodiscover.mysite.com/autodiscover/autodiscover.xml FAILED (0x8004010F)

    Srv Record lookup for mysite.com starting

    Srv Record lookup for mysite.org FAILED (0x8007251D)

    The clients are outlook 2007, this was migrated from Exchange 2003. Any help you can give would be greatly appreciated.

    Tuesday, October 19, 2010 3:35 PM

All replies

  • Unless example.com resolves to your Exchange server (unlikely and not recommended) the first errors are to be expected.

    The only ones I am interested in is the autodiscover.example.com URLs. They are giving a 8004010F error, which is cannot find.

    That would tend to point to the URL resolving to the wrong place, the wrong web site, something like that.
    Do you have a valid SSL certificate on the server, with the required URLs in it?

    Has anything been changed about the server configuration, such as an additional site, IP address etc?

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources
    Tuesday, October 19, 2010 11:38 PM
  • Hi,

    Does the Autodiscover work for the native Exchange 2010 users not migrated users?

    Please run test-outlookwebservices |fl command in EMS, then post the results here.

    Thanks

    Allen


    Allen Song
    Wednesday, October 20, 2010 7:41 AM
  • Yes there is a valid certificate, and the only thing on the exchange server is exchange 2010 and forefront protection for exchange. Autodiscover does not work for native users. Here is the results of the test-outlookwebservices |fl command

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1019
    Type       : Information
    Message    : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://bg
                 cmanatee.org/autodiscover/autodiscover.xml.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/autodiscover/autodiscover.xml received the error Unable to connect
                 to the remote server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/autodiscover/autodiscover.xml received the error No connection coul
                 d be made because the target machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1023
    Type       : Error
    Message    : The Autodiscover service couldn't be contacted.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1113
    Type       : Error
    Message    : When contacting https://BCGMEXCH1.BGCManatee.local:443/autodiscover/autodiscover.xml received the error Th
                 e remote server returned an error: (401) Unauthorized.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1123
    Type       : Error
    Message    : The Autodiscover service couldn't be contacted.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/ews/exchange.asmx received the error Unable to connect to the remot
                 e server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/ews/exchange.asmx received the error No connection could be made be
                 cause the target machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1025
    Type       : Error
    Message    : [EXCH] Error contacting the AS service at https://bgcmanatee.org/ews/exchange.asmx. Elapsed time was 108 m
                 illiseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/ews/exchange.asmx received the error Unable to connect to the remot
                 e server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/ews/exchange.asmx received the error No connection could be made be
                 cause the target machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1027
    Type       : Error
    Message    : [EXCH] Error contacting the UM service at https://bgcmanatee.org/ews/exchange.asmx. Elapsed time was 15 mi
                 lliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/EWS/Exchange.asmx received the error Unable to connect to the remot
                 e server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/EWS/Exchange.asmx received the error No connection could be made be
                 cause the target machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1025
    Type       : Error
    Message    : [EXPR] Error contacting the AS service at https://bgcmanatee.org/EWS/Exchange.asmx. Elapsed time was 30 mi
                 lliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/EWS/Exchange.asmx received the error Unable to connect to the remot
                 e server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/EWS/Exchange.asmx received the error No connection could be made be
                 cause the target machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1027
    Type       : Error
    Message    : [EXPR] Error contacting the UM service at https://bgcmanatee.org/EWS/Exchange.asmx. Elapsed time was 15 mi
                 lliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1124
    Type       : Success
    Message    : [Server] Successfully contacted the AS service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th
                 e elapsed time was 385 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1126
    Type       : Success
    Message    : [Server] Successfully contacted the UM service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th
                 e elapsed time was 281 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/rpc received the error Unable to connect to the remote server

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/rpc received the error No connection could be made because the targ
                 et machine actively refused it 67.79.167.210:443

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1029
    Type       : Error
    Message    : [EXPR] Error contacting the RPC/HTTP service at https://bgcmanatee.org/rpc. Elapsed time was 30 millisecon
                 ds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1128
    Type       : Success
    Message    : [EXPR] Successfully contacted the RPC/HTTP service at https://bcgmexch1.bgcmanatee.local/rpc. The elapsed
                 time was 937 milliseconds.

    Thursday, October 21, 2010 2:16 PM
  • Ok after looking over that myself, i realized that our dns server was returning the wrong ip for bgcmanatee.org. After correcting that, i now get this when i run test-outlookwebservices |fl

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1019
    Type       : Information
    Message    : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://bg
                 cmanatee.org/autodiscover/autodiscover.xml.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1004
    Type       : Error
    Message    : The certificate for the URL https://bgcmanatee.org/autodiscover/autodiscover.xml is incorrect. For SSL to
                 work, the certificate needs to have a subject of bgcmanatee.org, instead the subject found is BCGMEXCH1. C
                 onsider correcting service discovery, or installing a correct SSL certificate.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1013
    Type       : Error
    Message    : When contacting https://bgcmanatee.org/autodiscover/autodiscover.xml received the error The remote server
                 returned an error: (401) Unauthorized.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1023
    Type       : Error
    Message    : The Autodiscover service couldn't be contacted.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1113
    Type       : Error
    Message    : When contacting https://BCGMEXCH1.BGCManatee.local:443/autodiscover/autodiscover.xml received the error Th
                 e remote server returned an error: (401) Unauthorized.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1123
    Type       : Error
    Message    : The Autodiscover service couldn't be contacted.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1024
    Type       : Success
    Message    : [EXCH] Successfully contacted the AS service at https://bgcmanatee.org/ews/exchange.asmx. The elapsed time
                  was 249 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1026
    Type       : Success
    Message    : [EXCH] Successfully contacted the UM service at https://bgcmanatee.org/ews/exchange.asmx. The elapsed time
                  was 31 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1024
    Type       : Success
    Message    : [EXPR] Successfully contacted the AS service at https://bgcmanatee.org/EWS/Exchange.asmx. The elapsed time
                  was 265 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1026
    Type       : Success
    Message    : [EXPR] Successfully contacted the UM service at https://bgcmanatee.org/EWS/Exchange.asmx. The elapsed time
                  was 93 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1124
    Type       : Success
    Message    : [Server] Successfully contacted the AS service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th
                 e elapsed time was 46 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1126
    Type       : Success
    Message    : [Server] Successfully contacted the UM service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th
                 e elapsed time was 46 milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1028
    Type       : Success
    Message    : [EXPR] Successfully contacted the RPC/HTTP service at https://bgcmanatee.org/rpc. The elapsed time was 109
                  milliseconds.

    RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407
    Id         : 1128
    Type       : Success
    Message    : [EXPR] Successfully contacted the RPC/HTTP service at https://bcgmexch1.bgcmanatee.local/rpc. The elapsed
                 time was 0 milliseconds.

    • Edited by acornett Thursday, October 21, 2010 2:47 PM Wrong copy paste
    Thursday, October 21, 2010 2:46 PM
  • Like a former president once said "trust but verify". The correct certificate is now installed. The outcome of the test-exchangewebservices is now: RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://bg cmanatee.org/autodiscover/autodiscover.xml. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1004 Type : Error Message : The certificate for the URL https://bgcmanatee.org/autodiscover/autodiscover.xml is incorrect. For SSL to work, the certificate needs to have a subject of bgcmanatee.org, instead the subject found is BCGMEXCH1. C onsider correcting service discovery, or installing a correct SSL certificate. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1013 Type : Error Message : When contacting https://bgcmanatee.org/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1023 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1113 Type : Error Message : When contacting https://BCGMEXCH1.BGCManatee.local:443/autodiscover/autodiscover.xml received the error Th e remote server returned an error: (401) Unauthorized. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1123 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1024 Type : Success Message : [EXCH] Successfully contacted the AS service at https://bgcmanatee.org/ews/exchange.asmx. The elapsed time was 249 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://bgcmanatee.org/ews/exchange.asmx. The elapsed time was 31 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1024 Type : Success Message : [EXPR] Successfully contacted the AS service at https://bgcmanatee.org/EWS/Exchange.asmx. The elapsed time was 265 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1026 Type : Success Message : [EXPR] Successfully contacted the UM service at https://bgcmanatee.org/EWS/Exchange.asmx. The elapsed time was 93 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1124 Type : Success Message : [Server] Successfully contacted the AS service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th e elapsed time was 46 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://bcgmexch1.bgcmanatee.local/ews/exchange.asmx. Th e elapsed time was 46 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1028 Type : Success Message : [EXPR] Successfully contacted the RPC/HTTP service at https://bgcmanatee.org/rpc. The elapsed time was 109 milliseconds. RunspaceId : fce66f39-9c9e-4e4f-8576-a182a0fff407 Id : 1128 Type : Success Message : [EXPR] Successfully contacted the RPC/HTTP service at https://bcgmexch1.bgcmanatee.local/rpc. The elapsed time was 0 milliseconds.
    Thursday, October 21, 2010 2:53 PM
  • Got it! Correcting the dns entry and changing the certificate was the answer. Is there any way to get microsofts' routing and remote access server to redirect requests to an external domain back to an internally hosted site?
    Thursday, October 21, 2010 3:13 PM
  • You don't use RRAS, you use split DNS, so the external URL resolves to an internal IP address.

    http://www.amset.info/netadmin/split-dns.asp

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources
    Thursday, October 21, 2010 11:15 PM
  • Whre did you chagne the certificate at, I have checked my DNS and all is correct I even have the autodisocer@mydomain.com entry added.

    msiptak

    Thursday, December 6, 2012 2:16 PM