locked
Exchange 2010 Test-OwaConnectivity RRS feed

  • Question

  • Hello everybody,

    I'm having an issue successfully completing Test-OwaConnectivity which fails with error code:

    "The test received an unexpected response to an Outlook Web App request."

    Just for info, Exchange, OWA, etc. works perfectly without issues but that script fails. Why it is important? SCOM.

    This is multiple CAS servers setup in array. So, somehow error below is logical as even HTTPS traffic from CAS member to virtual address doesn't work. What bugs me is how to monitor all services (OWA, ECP, Autodiscover...) in this kind of environment?

    As I couldn't find any related articles, please advise of a solution where I could complete that PS without issues and without impact on security.

    Below is info from Test-OwaConnectivity

    ClientAccessServer MailboxServer URL                     Scenario Result  Latency Error
                                                                               (ms)
    ------------------ ------------- ---                     -------- ------  ------- -----
    ***********....     ***********... https://***********... Logon    Failure         The te...
    RunspaceId          : 6b1aa306-9454-4528-8498-92391cdd630d
    Events              : {Source: MSExchange Monitoring OWAConnectivity Internal
                          Id: 1011
                          Type: Success
                          Message: The Client Access server configuration check succeeded., Source: MSExchange Monitoring O
                          WAConnectivity Internal
                          Id: 1007
                          Type: Success
                          Message: Credentials were successfully loaded for all test mailboxes in the local site., Source:
                          MSExchange Monitoring OWAConnectivity Internal
                          Id: 1006
                          Type: Success
                          Message: There were no errors loading credentials for the test mailboxes that exist on mailbox se
                          rvers in the local site., Source: MSExchange Monitoring OWAConnectivity Internal
                          Id: 1001
                          Type: Error
                          Message: One or more of the Outlook Web App connectivity tests failed. Detailed information:
                          -------------------------------------
                          Target: *******************
                          Error: The test received an unexpected response to an Outlook Web App request.
                          URL: *********************
                          Details:
                          [13:54:33.330] : This URL type is Internal, so any certificate will be trusted.
                          [13:54:33.330] : Sending the HTTP GET logon request without credentials for authentication type v
                          erification.
                          [13:54:54.392] : The test received an unexpected response to an Outlook Web App request.
                          URL: *******************
                          Authentication Method:
                          Mailbox Server: *******************
                          Client Access Server Name: *******************
                          Scenario: Logon
                          Scenario Description: Sign in to Outlook Web App and verify the response page.
                          User Name: extest_b7ea62529b104
                          Performance Counter Name: Logon Latency
                          Result: Failure
                          Site: *******************
                          Latency: -00:00:00.0010000
                          Secure Access: True
                          ConnectionType: Plaintext
                          Port: 0
                          Latency (ms): -1
                          Virtual Directory Name: owa (Default Web Site)
                          URL: *******************
                          URL Type: Internal
                          Error:
                          The test received an unexpected response to an Outlook Web App request.
                          URL: *******************

    Thanks in advance!

    Regards,

    Ivan

    Tuesday, November 3, 2015 10:24 AM

All replies

  • Hi Ivan,

    I notice that there is no issue with your OWA internal access. Only the issue is reported in your Test-OwaConnectivity results.

    Please run the following command to check your OWA virtual directory settings:

    Get-OWAVirtualDirectory | FL Identity,*Auth*,*URL*

    In Event Viewer, review the Application log on your CAS server for events that may be associated with this alert.

    Regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Winnie Liang
    TechNet Community Support

    • Proposed as answer by Prem P Rana Wednesday, November 4, 2015 4:45 PM
    • Unproposed as answer by Unknown00652 Thursday, November 5, 2015 5:54 AM
    Wednesday, November 4, 2015 8:31 AM
    Moderator
  • Hello Winnie,

    Still no luck...

    Here is an output from one of the CAS servers (all servers gave the same output, OWA directories configured correctly):

    Identity                      : ************\owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    ExternalAuthenticationMethods : {Fba}
    Url                           : {}
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://************/OWA
    ExternalUrl                   : https://************/OWA

    Application log did not produce any errors, however there was an error in System log for every CAS member after running mentioned command.:

    DistributedCOM - EventID 10009

    "DCOM was unable to communicate with the computer ************ using any of the configured protocols."

    Regards,

    Ivan

    Thursday, November 5, 2015 5:49 AM