locked
Outlook Web App connectivity (External) transcation warnings RRS feed

  • Question

  • Hi, 

    We have just installed the Exchange 2010 management pack into our SCOM Test server (Windows 2008 R2 Standard/SCOM 2007 R2).  We have noticed we are getting alerts repeating for "Outlook Web App connectivity (External) transcation warnings".  It is using account which seems ok and not locked out.  It looks like it is trying to test the OWA login and failing. We have rerun the PS script to recreate the account and also reset the password in AD after that didnt work.

     > One or more of the Outlook Web App connectivity tests had warnings. Detailed information: </ d >

      < d > ------------------------------------- </ d >

      < d > Target: Server.domain.com|Site </ d >

      < d />

      < d > Error: The test couldn't sign in to Outlook Web App due to an authentication failure. </ d >

      < d > URL: https://owa.domain.com/owa/ </ d >

      < d > Mailbox: Site </ d >

      < d > User: extest_1e05e23742bc4 </ d >

      < d />

      < d > Details: </ d >

      < d />

      < d > [22:48:07.933] : The TrustAnySSLCertificate flag was specified, so any certificate will be trusted. </ d >

      < d > [22:48:07.933] : Sending the HTTP GET logon request without credentials for authentication type verification. </ d >

      < d > [22:48:08.167] : The HTTP request succeeded with result code 200 (OK). </ d >

      < d > [22:48:08.167] : The sign-in page is from ISA Server, not Outlook Web App. </ d >

      < d > [22:48:08.167] : The server reported that it supports authentication method FBA. </ d >

      < d > [22:48:08.167] : This virtual directory URL type is External or Unknown, so the authentication type won't be checked. </ d >

      < d > [22:48:08.167] : Trying to sign in with method 'Fba'. </ d >

      < d > [22:48:08.167] : Sending HTTP request for logon page 'https://owa.site.com/CookieAuth.dll?Logon'. </ d >

      < d > [22:48:08.183] : The HTTP request succeeded with result code 200 (OK). </ d >

      < d />

      < d > [22:48:08.401] : The test couldn't sign in to Outlook Web App due to an authentication failure. </ d >

      < d > URL: https://owa.site.com/owa/ </ d >

      < d > Mailbox: Site </ d >

      < d > User: extest_1e05e23742bc4 </ d >

      < d />

      < d > [22:48:08.401] : Test failed for URL 'https://owa.domain.com/owa/'. </ d >

      < d > Authentication Method: FBA </ d >

      < d > Mailbox Server: server.domain.com </ d >

      < d > Client Access Server Name: casserver.domain.com </ d >

      < d > Scenario: Logon </ d >

      < d > Scenario Description: Sign in to Outlook Web App and verify the response page. </ d >

      < d > User Name: extest_1e05e45742bc4 </ d >

      < d > Performance Counter Name: Logon Latency </ d >

      < d > Result: Skipped </ d >

      < d > Site: Site </ d >

      < d > Latency: -00:00:00.0010000 </ d >

      < d > Secure Access: True </ d >

      < d > ConnectionType: Plaintext </ d >

      < d > Port: 0 </ d >

      < d > Latency (ms): -1 </ d >

      < d > Virtual Directory Name: owa (Default Web Site) </ d >

      < d > URL: https://owa.domain.com/owa/ </ d >

      < d > URL Type: External </ d >

      < d > Error: </ d >

      < d > The test couldn't sign in to Outlook Web App due to an authentication failure. </ d >

      < d > URL: https://owa.domain.com/owa/ </ d >

      < d > Mailbox: site </ d >

      < d > User: extest_1e05e23742bc4 </ d >

    Any ideas appreciated


    • Edited by Nee Gee Friday, January 13, 2012 1:32 PM
    Friday, January 13, 2012 1:18 PM

All replies

  •  

    Hi,

     

    Please enable Basic Authentication for OWA and see how it works:

     

    Setting Up Standard Authentication Methods for Outlook Web App

    http://technet.microsoft.com/en-us/library/bb125207.aspx

     

    Meanwhile, please test the connection with the following methods:

     

    1.    Run Microsoft Remote Connectivity Analyzer:

     

    Microsoft Remote Connectivity Analyzer

    https://www.testexchangeconnectivity.com/

     

    2.    Run the Test-OwaConnectivity command and see if the same issue appears:

     

    Test-OwaConnectivity

    http://technet.microsoft.com/en-us/library/aa997682.aspx

     

    Hope this helps.

     

    Thanks.

    Nicholas Li

    TechNet Community Support


    • Edited by Nicholas Li Monday, January 16, 2012 7:29 AM
    Monday, January 16, 2012 7:29 AM
  • Hi,

    Thanks for you reply.  If I enable Basic Authentication for OWA how will that affect our security and the experience for the end user with OWA?

    Also when we try to login to OWA with that account and the password we specified when creating this in powershell it fails and thats what the above seems to indicate.  We can reset the password for the account to the one that we specified in the powershell and log in to OWA.  Is there any way to find out what password it thinks it should be without reseting it in AD?

    Many Thanks

    Monday, January 16, 2012 11:59 AM