Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > Exchange Server Forums > Clients > Autodiscover doesn't work sometimes

Answered Autodiscover doesn't work sometimes

    •  
      Thursday, August 18, 2011 11:39 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

      We have some problems with our autodiscover. This problem appears only on one server (Windows Server 2008 R2 SP1). Sometimes, the autodiscover works and sometimes it doesn't. We can see this through the automatic e-mailconfiguration test in Outlook 2007. We are getting the following results:

      Autodiscover to https://autodsicover.domain.com/autodiscover/autodiscover.xml failed (0x8007273D).

      I've checked what the error 0x8007273D means:

      C:\>err 0x8007273d
      # as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x273d
      # for hex 0x273d / decimal 10045 :
        WSAEOPNOTSUPP                                                 winerror.h
      # The attempted operation is not supported for the type of
      # object referenced.
        WSAEOPNOTSUPP                                                 winsock2.h
      # 2 matches found for "0x8007273d"

      Because of this all we are unable to configure the Out of Office and we are unable to download the offline address book. We are using Exchange 2007 and Outlook 2007. On other systems there are none of these kind of problems.

      Does anyone know what this is and how we can solve this problem?

      Remco

       

       

       

       

    Answers

    • Monday, August 22, 2011 7:04 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

       

      Some questions:

       

      1. How many CAS server do you have? Do you use CAS array?

      2. Do you use the https://autodsicover.domain.com/autodiscover/autodiscover.xml as the SCP record?

       

      Since the issue is only on one server, as a workaround, you can set the autodiscover on the problematic client to NULL.

       

      Set-ClientAccessServer –id ServerName –AutodiscoverServiceInternalUri $Null

       

      If you would like to troubleshoot this issue, please manually access the autodiscover url via IE and see if there any detailed error message.

       

      You can also check the IIS log to know the IIS error code about this autodiscover service.

       

      Thanks,

      Simon

       

       

    All Replies

    • Thursday, August 18, 2011 2:30 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      This issue could be because of corruption in winsock due to third party utility. Do we use any proxy in Internet Explorer. If yes, try to disable proxy in IE and try to run Test email autoconfiguration. Run EXTRA trace with below components selected while running test-emailautoconfiguration. ADProvider MSExchangeAutodiscover Upload the .etl files. Note : If you have multiple CAS servers then edit the host file of teh client machine to point it to any one of the CAS server where were were running the EXTRA. Example 10.10.10.10 Virtual name of the load balancer.
       
    • Friday, August 19, 2011 6:58 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      We are not using any proxy servers. Winsock is a good possibility. How can we fix the winsock?
       
    • Monday, August 22, 2011 7:04 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

       

      Some questions:

       

      1. How many CAS server do you have? Do you use CAS array?

      2. Do you use the https://autodsicover.domain.com/autodiscover/autodiscover.xml as the SCP record?

       

      Since the issue is only on one server, as a workaround, you can set the autodiscover on the problematic client to NULL.

       

      Set-ClientAccessServer –id ServerName –AutodiscoverServiceInternalUri $Null

       

      If you would like to troubleshoot this issue, please manually access the autodiscover url via IE and see if there any detailed error message.

       

      You can also check the IIS log to know the IIS error code about this autodiscover service.

       

      Thanks,

      Simon