none
Exchange 2013 Autodiscover broken RRS feed

  • Question

  • I am trying to fix autodiscover on a 2013 Exchange server.  As far as I know it has never worked but is recently causing problem with new PCs being installed.  I have recreated the autodiscover virtual directory already but did not help any.

    In event viewer I see 

    Log Name:     Application
    Source:       MSExchange Front End HTTP Proxy
    Event ID:     1003
    Task Category: Core
    Level:       Error
    Keywords:     Classic
    User:         N/A
    Computer:     exchange.domain.local
    Description:
    [Autodiscover] An internal server error occurred. The unhandled exception was: System.NullReferenceException: Object reference not set to an instance of an object.
      at System.Object.GetType()
      at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
      at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
      at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass8.<Run>b__7()
      at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

    and when I run Test-OutlookWebServices I get
    Test-OutlookWebServices : Autodiscover response:
    System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
      at System.Net.HttpWebRequest.GetResponse()
      at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
      at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

    I have run out of hair to pull out, please help.
    Thanks

    Tuesday, September 10, 2019 6:44 PM

Answers

  • Hi,

    Please check the authentication settings of Autodiscover from IIS. IIS Manager > Default Web Site > Autodiscover > Authentication. Here is the default settings in my environment:

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by David-Mac Thursday, October 3, 2019 1:03 PM
    Tuesday, October 1, 2019 9:53 AM
    Moderator

All replies

  • Hi,

    What's the detailed version of your Exchange 2013? You can use the following command to check the build number:

    Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion

    Can you describe with more information of the issue about newly installed PCs? 

    If the Autodiscover service doesn't work, what errors do you get when create new Outlook profile with Autodiscover?

    You can use the Test E-mail Autoconfiguration in Outlook:

    1.  Locate the Outlook icon in the notification area, hold the CTRL key, right click the icon, and then click Test E-mail AutoConfiguration.

    2.  Enter the user's email address, only choose Use AutoDiscover. View the result on the Log tab.

    Use the following command to check your Autodiscover internal url, and make sure related DNS records are setting correctly:

    Get-ClientAccessService|fl name,*uri*

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 11, 2019 5:42 AM
    Moderator
  • Exchange 2013 Std Version 15.0 (Build 712.24)
    When trying to configure Outlook it just says it cant find a secure connection then fails that too and says it cant find the server.
    The command Get-ClientAccessService says unrecognized command but Get-ClientAccessServer returns: AutoDiscoverServiceInternalUri : https://mail.domainname.com/Autodiscover/Autodiscover.xml
    The Outlook Autodiscover test results:
    Attempting URL https://mail.domainname.com/Autodiscvoer/Autodiscover.xml found through SCP
    Autodiscover to https://mail.domainname.com/Autodiscvoer/Autodiscover.xml starting
    GetLastError=0; httpStatus=500
    Autodiscover to https://mail.domainname.com/Autodiscvoer/Autodiscover.xml failed (0x800C820F)
    Autodiscover to https://domainname.com/Autodiscvoer/Autodiscover.xml starting
    GetLastError=2147954407; httpStatus=0
    Autodiscover to https://domainname.com/Autodiscvoer/Autodiscover.xml failed (0x80004005)
    Autodiscover to https://autodiscover.domainname.com/Autodiscvoer/Autodiscover.xml starting
    GetLastError=0; httpStatus=500
    Autodiscover to https://autodiscover.domainname.com/Autodiscvoer/Autodiscover.xml Failed (0x800C820F)
    Local autodiscover for domainname.com starting
    Local autodiscover for domainname.com Failed (0x8004010F)
    Redirect Check to https://autodiscover.domainname.com/Autodiscvoer/Autodiscover.xml starting
    Redirect Check to https://autodiscover.domainname.com/Autodiscvoer/Autodiscover.xml Failed (0x800C820D)
    Srv Record lookup for domainname.com Starting
    Srv Record lookup for domainname.com Failed (0x8004010F)
    Whew......
    The httpStatus=500 seems to be a recurring thing.
    If I run on the exchange server itself Test-OutlookWebServices -identity: username@domainname.com -MailboxCredential (Get-Credential) -verbose I get the following:
    VERBOSE: [13:50:28.956 GMT] Test-OutlookWebServices : Runspace context: Executing user:
    domainname.local/Users/Administrator, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [13:50:28.972 GMT] Test-OutlookWebServices : Active Directory session settings for 'Test-OutlookWebServices'
    are: View Entire Forest: 'False', Default Scope: 'domainname.local', Configuration Domain Controller:
    'DC2016.domainname.local', Preferred Global Catalog: 'DC2016.domainname.local', Preferred Domain
    Controllers: '{ DC2016.domainname.local }'
    VERBOSE: [13:50:28.972 GMT] Test-OutlookWebServices : Beginning processing Test-OutlookWebServices
    VERBOSE: [13:50:28.972 GMT] Test-OutlookWebServices : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [13:50:28.988 GMT] Test-OutlookWebServices : Source server: Exchange.domainname.local
    VERBOSE: [13:50:28.988 GMT] Test-OutlookWebServices : Source site:
    domainname.local/Configuration/Sites/Default-First-Site-Name
    VERBOSE: [13:50:29.769 GMT] Test-OutlookWebServices : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Client access monitoring user: domainname.local/domainname
    Users/UserName
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Client access monitoring user primary SMTP address:
    username@domainname.com
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Client access monitoring organization:
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Found Service Connection Point 'exchange\exchange' by site
    'Default-First-Site-Name' with URL 'https://mail.domainname.com/Autodiscover/Autodiscover.xml'.
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Found Autodiscover URL
    'https://mail.domainname.com/Autodiscover/Autodiscover.xml' by email address 'username@domainname.com'.
    VERBOSE: Testing Outlook Web Services.
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Resolved current organization: .
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Autodiscover connecting to
    'https://mail.domainname.com/Autodiscover/Autodiscover.xml'.
    VERBOSE: [13:50:29.816 GMT] Test-OutlookWebServices : Test account: username Password: ******
    VERBOSE: [13:50:29.863 GMT] Test-OutlookWebServices : Autodiscover request:
    User-Agent: exchange/Test-OutlookWebServices/username@domainname.com
    Content-Type: text/xml; charset=utf-8
    Host: mail.domainname.com
    Content-Length: 464
    Expect: 100-continue
    Connection: Keep-Alive
    VERBOSE: [13:50:29.863 GMT] Test-OutlookWebServices : Autodiscover request:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
      <Request>
        <EMailAddress>username@domainname.com</EMailAddress>

    <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableRe
    sponseSchema>
      </Request>
    </Autodiscover>
    VERBOSE: [13:50:29.863 GMT] Test-OutlookWebServices : Autodiscover response:
    X-FEServer: exchange
    Content-Length: 5788
    Cache-Control: private
    Content-Type: text/html; charset=utf-8
    Date: Wed, 11 Sep 2019 13:50:28 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    VERBOSE: [13:50:29.863 GMT] Test-OutlookWebServices : Autodiscover response:
    System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

    Source                              ServiceEndpoint                     Scenario                       Result  Latency
                                                                                                                      (MS)
    ------                              ---------------                     --------                       ------  -------
    exchange.domainname.local      mail.domainname.com              Autodiscover: Outlook Provider Failure      32
    exchange.domainname.local                                          Exchange Web Services          Skipped       0
    exchange.domainname.local                                          Availability Service           Skipped       0
    exchange.domainname.local                                          Offline Address Book           Skipped       0
    VERBOSE: [13:50:29.863 GMT] Test-OutlookWebServices : Admin Audit Log: Entered Handler:OnComplete.
    VERBOSE: [13:50:29.878 GMT] Test-OutlookWebServices : Ending processing Test-OutlookWebServices

    Wednesday, September 11, 2019 2:41 PM
  • Hi,

    Since you set to use https://mail.domainname.com/Autodiscover/Autodiscover.xml, did you create the A record and configure the mail.domainname.com to point to the right IP address?

    Try to access https://mail.domainname.com/Autodiscover/Autodiscover.xml from your Exchange server browser, enter the credential and check to see if you will get 600 error as expected.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 13, 2019 9:33 AM
    Moderator
  • I must have fat fingered that. I have switched it back to https://autodiscover.domainname.com/Autodiscover/Autodiscover.xml  I have restarted IIS and Exchange transport service.   When I test it I get 404.0 not found. IN the error it says Physical Path  C:\inetpub\wwwroot\Autodiscover\Autodiscover.xml but in IIS when I look at the advanced settings for the Autodiscover site it shows D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover which does exist.  Exchange is installed on D.
    Friday, September 13, 2019 4:01 PM
  • Also. Autodiscover.domainname.com does resolve properly and is created in DNS. It did give me a login screen and let me log in then gave the 404.

    Thanks

    Friday, September 13, 2019 4:22 PM
  • I noticed the Autodiscover Backend IIS site was missing.  I have searched but did not find a good article on how to recreate the backend, just the normal front end site.  So I tried to manually create it in IIS but have my doubts if it is 100% correct.  When I got to the autodiscover website I now get this:

    <?xml version="1.0" encoding="UTF-8"?>
    -<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="2350424199" Time="08:05:24.9886224"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

    Monday, September 16, 2019 1:25 PM
  • Hi David,

    Do you mean the autodiscover url can give 600 error as expected at present?

    What's the result of using Test E-mail Autoconfiguration again? Does the Autodiscover work after recreate backend directory?

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 18, 2019 11:19 AM
    Moderator
  • Current autodiscover url result:
    <?xml version="1.0" encoding="UTF-8"?>
    -<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="2350424199" Time="11:14:39.3266500"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

    Test-OutlookWebServices -identity: username@domain.com -MailboxCredential (Get-Credential) -verbose 
    VERBOSE: [16:12:31.576 GMT] Test-OutlookWebServices : Runspace context: Executing user:
    domain.local/Users/Administrator, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [16:12:31.592 GMT] Test-OutlookWebServices : Initializing Active Directory server settings for the remote
    Windows PowerShell session.
    VERBOSE: [16:12:31.592 GMT] Test-OutlookWebServices : Active Directory session settings for 'Test-OutlookWebServices'
    are: View Entire Forest: 'False', Default Scope: 'domain.local', Configuration Domain Controller:
    'DomainController.domain.local', Preferred Global Catalog: 'DomainController.domain.local', Preferred Domain
    Controllers: '{ DomainController.domain.local }'
    VERBOSE: [16:12:31.592 GMT] Test-OutlookWebServices : Beginning processing Test-OutlookWebServices
    VERBOSE: [16:12:31.592 GMT] Test-OutlookWebServices : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [16:12:32.686 GMT] Test-OutlookWebServices : Source server: ExchangeSvr.domain.local
    VERBOSE: [16:12:32.701 GMT] Test-OutlookWebServices : Source site:
    domain.local/Configuration/Sites/Default-First-Site-Name
    VERBOSE: [16:12:32.717 GMT] Test-OutlookWebServices : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [16:12:32.873 GMT] Test-OutlookWebServices : Client access monitoring user: domain.local/domain
    Users/username
    VERBOSE: [16:12:32.873 GMT] Test-OutlookWebServices : Client access monitoring user primary SMTP address:
    username@domain.com
    VERBOSE: [16:12:32.873 GMT] Test-OutlookWebServices : Client access monitoring organization:
    VERBOSE: [16:12:32.982 GMT] Test-OutlookWebServices : Found Service Connection Point 'ExchangeSvr\ExchangeSvr' by site
    'Default-First-Site-Name' with URL 'https://autodiscover.domain.com/Autodiscover/Autodiscover.xml'.
    VERBOSE: [16:12:32.982 GMT] Test-OutlookWebServices : Found Autodiscover URL
    'https://autodiscover.domain.com/Autodiscover/Autodiscover.xml' by email address 'username@domain.com'.
    VERBOSE: Testing Outlook Web Services.
    VERBOSE: [16:12:32.998 GMT] Test-OutlookWebServices : Resolved current organization: .
    VERBOSE: [16:12:33.029 GMT] Test-OutlookWebServices : Autodiscover connecting to
    'https://autodiscover.domain.com/Autodiscover/Autodiscover.xml'.
    VERBOSE: [16:12:33.029 GMT] Test-OutlookWebServices : Test account: username Password: ******
    VERBOSE: [16:12:33.107 GMT] Test-OutlookWebServices : Autodiscover request:
    User-Agent: ExchangeSvr/Test-OutlookWebServices/username@domain.com
    Content-Type: text/xml; charset=utf-8
    Host: autodiscover.domain.com
    Content-Length: 464
    Expect: 100-continue
    Connection: Keep-Alive
    VERBOSE: [16:12:33.123 GMT] Test-OutlookWebServices : Autodiscover request:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
      <Request>
        <EMailAddress>username@domain.com</EMailAddress>

    <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableRe
    sponseSchema>
      </Request>
    </Autodiscover>
    VERBOSE: [16:12:33.123 GMT] Test-OutlookWebServices : Autodiscover response:
    X-FEServer: ExchangeSvr
    Content-Length: 5788
    Cache-Control: private
    Content-Type: text/html; charset=utf-8
    Date: Wed, 18 Sep 2019 16:12:33 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    VERBOSE: [16:12:33.139 GMT] Test-OutlookWebServices : Autodiscover response:
    System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

    Source                              ServiceEndpoint                     Scenario                       Result  Latency
    ------                              ---------------                     --------                       ------  -------
    ExchangeSvr.domain.local      autodiscover.domain.com      Autodiscover: Outlook Provider Failure      36
    ExchangeSvr.domain.local                                          Exchange Web Services          Skipped       0
    ExchangeSvr.domain.local                                          Availability Service           Skipped       0
    ExchangeSvr.domain.local                                          Offline Address Book           Skipped       0
    VERBOSE: [16:12:33.170 GMT] Test-OutlookWebServices : Admin Audit Log: Entered Handler:OnComplete.
    VERBOSE: [16:12:33.185 GMT] Test-OutlookWebServices : Ending processing Test-OutlookWebServices

    Autodiscover is still broken for outlook clients
    Wednesday, September 18, 2019 4:23 PM
  • Hi David,

    You should check the autodiscover with Test E-mail Autoconfiguration on PC inside the domain. Test-OutlookWebServices cmdlet is used in Exchange 2010.

    You can create a new Outlook profile with Autodiscover, and post the screenshot if you get any error alerts. Please don't forget to cover your personal information as well.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 20, 2019 9:14 AM
    Moderator
  • 

    Friday, September 20, 2019 1:56 PM
  • did you already were able to recreate the backend autodiscover?

    New-AutodiscoverVD

    Lock at the Role switch (Mailbox for backend)


    Please remember to mark the replies as answers if they helped.

    Friday, September 20, 2019 2:24 PM
  • If I do New-AutoDiscoverVirtualDirectory -Role Mailbox it says already exists.   If I need to remove it I am not sure how to only remove the backend autodiscover to just re-add that one without removing the front end too.  some directions would be great.

    Thanks


    • Edited by David-Mac Friday, September 20, 2019 2:41 PM typo
    Friday, September 20, 2019 2:40 PM
  • I found the -ShowMailboxVirtualDirectories switch but it still only show the (Default Web Site) and not the Backend.

    Thanks

    Friday, September 20, 2019 2:51 PM
  • Hi,

    Please check the SCP from ADSI Edit.

    Go to Configuration > CN=Configuration,DC=domain,DC=com > CN=Services > CN=Microsoft Exchange > CN=org_name > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers > CN=CAS_server > CN=Protocols > CN=Autodiscover.

    Right click the SCP, choose Properties and check the serviceBindingInformation attribute. Make sure the serviceBindingInformation is set to use the AutoDiscoverServiceInternalUri, which you can get by Get-ClientAccessServer cmdlet.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 25, 2019 10:43 AM
    Moderator
  • Thank you so much for the reply.  The SCP does match.

    Any other ideas would be greatly appreciated.

    Wednesday, September 25, 2019 1:16 PM
  • Please try to create a Outlook profile with autodiscover to reproduce this issue. Then check the IIS log for details information. The default path is C:\inetpub\logs\LogFiles\W3SVC1.

    Please also check Event Viewer for some related event IDs.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 27, 2019 10:41 AM
    Moderator
  • Outlook just gives the generic error: "we are having trouble connecting to your account.  Verify the settings below and make changes if necessary."

    On the exchange 2013 server I see these:

    Log Name:      Application
    Source:        MSExchange Front End HTTP Proxy
    Date:          9/27/2019 9:20:28 AM
    Event ID:      1003
    Task Category: Core
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ExchangeServer.domain.local
    Description:
    [Autodiscover] An internal server error occurred. The unhandled exception was: System.NullReferenceException: Object reference not set to an instance of an object.
       at System.Object.GetType()
       at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
       at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
       at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass8.<Run>b__7()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Date:          9/27/2019 9:20:28 AM
    Event ID:      1309
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      ExchangeServer.domain.local
    Description:
    Event code: 3005 
    Event message: An unhandled exception has occurred. 
    Event time: 9/27/2019 9:20:28 AM 
    Event time (UTC): 9/27/2019 2:20:28 PM 
    Event ID: 2779d63d5c6341ec88d1abc09ae8137e 
    Event sequence: 49247 
    Event occurrence: 31807 
    Event detail code: 0 
     
    Application information: 
        Application domain: /LM/W3SVC/1/ROOT/Autodiscover-1-132134864967434937 
        Trust level: Full 
        Application Virtual Path: /Autodiscover 
        Application Path: D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover\ 
        Machine name: MDEXCH2013 
     
    Process information: 
        Process ID: 4428 
        Process name: w3wp.exe 
        Account name: NT AUTHORITY\SYSTEM 
     
    Exception information: 
        Exception type: NullReferenceException 
        Exception message: Object reference not set to an instance of an object.
       at System.Object.GetType()
       at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
       at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
       at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass8.<Run>b__7()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at Microsoft.Exchange.HttpProxy.ProxyModule.OnPostAuthorizeInternal(HttpApplication httpApplication)
       at Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClassb.<OnPostAuthorizeRequest>b__a()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
     
    Request information: 
        Request URL: https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml 
        Request path: /Autodiscover/Autodiscover.xml 
        User host address: 192.168.1.112 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: NT AUTHORITY\SYSTEM 
     
    Thread information: 
        Thread ID: 26 
        Thread account name: NT AUTHORITY\SYSTEM 
        Is impersonating: False 
        Stack trace:    at System.Object.GetType()
       at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
       at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
       at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass8.<Run>b__7()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at Microsoft.Exchange.HttpProxy.ProxyModule.OnPostAuthorizeInternal(HttpApplication httpApplication)
       at Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClassb.<OnPostAuthorizeRequest>b__a()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Custom event details: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 4.0.30319.0" />
        <EventID Qualifiers="32768">1309</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-09-27T14:20:28.000000000Z" />
        <EventRecordID>29849562</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ExchangeServer.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3005</Data>
        <Data>An unhandled exception has occurred.</Data>
        <Data>9/27/2019 9:20:28 AM</Data>
        <Data>9/27/2019 2:20:28 PM</Data>
        <Data>2779d63d5c6341ec88d1abc09ae8137e</Data>
        <Data>49247</Data>
        <Data>31807</Data>
        <Data>0</Data>
        <Data>/LM/W3SVC/1/ROOT/Autodiscover-1-132134864967434937</Data>
        <Data>Full</Data>
        <Data>/Autodiscover</Data>
        <Data>D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover\</Data>
        <Data>ExchangeServer</Data>
        <Data>
        </Data>
        <Data>4428</Data>
        <Data>w3wp.exe</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>NullReferenceException</Data>
        <Data>Object reference not set to an instance of an object.
       at System.Object.GetType()
       at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
       at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
       at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.&lt;&gt;c__DisplayClass8.&lt;Run&gt;b__7()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at Microsoft.Exchange.HttpProxy.ProxyModule.OnPostAuthorizeInternal(HttpApplication httpApplication)
       at Microsoft.Exchange.HttpProxy.ProxyModule.&lt;&gt;c__DisplayClassb.&lt;OnPostAuthorizeRequest&gt;b__a()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)

    </Data>
        <Data>https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml</Data>
        <Data>/Autodiscover/Autodiscover.xml</Data>
        <Data>192.168.1.112</Data>
        <Data>
        </Data>
        <Data>False</Data>
        <Data>
        </Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>26</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>False</Data>
        <Data>   at System.Object.GetType()
       at Microsoft.Exchange.HttpProxy.DatacenterRedirectStrategy.CheckLiveIdBasicPartialAuthResult(HttpContext httpContext)
       at Microsoft.Exchange.HttpProxy.AutodiscoverProxyRequestHandler.OnInitializingHandler()
       at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.&lt;&gt;c__DisplayClass8.&lt;Run&gt;b__7()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at Microsoft.Exchange.HttpProxy.ProxyModule.OnPostAuthorizeInternal(HttpApplication httpApplication)
       at Microsoft.Exchange.HttpProxy.ProxyModule.&lt;&gt;c__DisplayClassb.&lt;OnPostAuthorizeRequest&gt;b__a()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)
    </Data>
      </EventData>
    </Event>

    IIS log:
    2019-09-27 14:46:48 192.168.1.23 POST /autodiscover/autodiscover.xml &cafeReqId=d05fd199-90cc-432c-9bbc-fc36fa90fa0f; 443 username@domain.com 192.168.1.112 Outlook/15.0+(15.0.4535.1000;+MSI;+x64) - 401 1 1326 15
    I see the 401 that means login failed but I have double checkec and verified in OWA and the username and password are correct.
    Thanks so much for any help!!

    Friday, September 27, 2019 2:55 PM
  • Hi,

    Please check the authentication settings of Autodiscover from IIS. IIS Manager > Default Web Site > Autodiscover > Authentication. Here is the default settings in my environment:

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by David-Mac Thursday, October 3, 2019 1:03 PM
    Tuesday, October 1, 2019 9:53 AM
    Moderator
  • thank you so much for posting that!!!  To match yours I had to disable Digest and Forms.  I want to reboot the server for a final test but it seems to have fixed it.  In all the times I have run "Get- "commands I don't think I have seem the Forms Authentication setting for the IIS site???  Ill post an update once I have rebooted to verify.

    Thanks so very much !!!

    Tuesday, October 1, 2019 2:22 PM
  • I rebooted the server and autodiscover is still working.  Thanks so very much!!
    Thursday, October 3, 2019 1:04 PM