Hello Sir,

Could some one help me on the below issue. As we are getting exchange alert from the SCOM Sever more frequently. No error id's in SCOM server as well as in exchange server. The OWA links are opening fine with out any issues for the external users, but still getting alert from SCOM.

In SCOM Server the "CLIENT ACEESS" has RED X.(ERROR)

Please assist us how to fix the below error.

Date and Time: 20/02/2015 15:02:32
Log Name: Script-generated data
Source: MSExchange Monitoring OWAConnectivity External
Event Number: 1001
Level: 1
Logging Computer: NGss.xxx.local
User: 
 Description:
One or more of the Outlook Web App connectivity tests failed. Detailed information: ------------------------------------- Target: NGss.xx.local|BGRP Error: The test received an unexpected response to an Outlook Web App request. URL:  https://owa.exx.xxx.com/owa// Details: [15:02:11.758] : The TrustAnySSLCertificate flag was specified, so any certificate will be trusted. [15:02:11.758] : Sending the HTTP GET logon request without credentials for authentication type verification. [15:02:32.758] : The test received an unexpected response to an Outlook Web App request. URL: / Authentication Method: Mailbox Server: sss.xxx.local Client Access Server Name: sss.xxx.local Scenario: Logon Scenario Description: Sign in to Outlook Web App and verify the response page. User Name: extest_730bfbcde7a04 Performance Counter Name: Logon Latency Result: Failure Site: BGRP Latency: -00:00:00.0010000 Secure Access: True ConnectionType: Plaintext Port: 0 Latency (ms): -1 Virtual Directory Name: owa (Default Web Site) URL: https://owa.exx.xxx.com/owa/ URL Type: External Error: The test received an unexpected response to an Outlook Web App request. URL: / ------------------------------------- Diagnostic command: "Test-OwaConnectivity -TestType:External -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:$true"

Event Data:

Date and Time: 20/02/2015 15:02:32
Property Name Property Value
Message One or more of the Outlook Web App connectivity tests failed. Detailed information: ------------------------------------- Target: sss.xxx.local|BGRP Error: The test received an unexpected response to an Outlook Web App request. URL: https://owa.ss.xxx.com/owa/ Details: [15:02:11.758] : The TrustAnySSLCertificate flag was specified, so any certificate will be trusted. [15:02:11.758] : Sending the HTTP GET logon request without credentials for authentication type verification. [15:02:32.758] : The test received an unexpected response to an Outlook Web App request. URL: https://owa.ss.xxx.com/owa/ Authentication Method: Mailbox Server: sss.xxx.local Client Access Server Name: sss.xxx.local Scenario: Logon Scenario Description: Sign in to Outlook Web App and verify the response page. User Name: extest_730bfbcde7a04 Performance Counter Name: Logon Latency Result: Failure Site: BGRP Latency: -00:00:00.0010000 Secure Access: True ConnectionType: Plaintext Port: 0 Latency (ms): -1 Virtual Directory Name: owa (Default Web Site) URL: https://owa.ss.xxx.com/owa/ URL Type: External Error: The test received an unexpected response to an Outlook Web App request. URL: https://owa.ss.xxx.com/owa/ ------------------------------------- Diagnostic command: "Test-OwaConnectivity -TestType:External -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:$true"
EventNumber 1001
EventType 1
EventSource MSExchange Monitoring OWAConnectivity External
EventInstanceName 
LoggingComputer sss.xxx.local

Thanks in Advance

Regards,
Sanjeev Kumar N

Hi,

This cmdlet runs against a Mailbox server by using a specific mailbox. Make sure that this mailbox has been created by running the new-TestCasConnectivityUser.ps1 script.

Please go through the link below for more details:

Outlook Web App connectivity (Internal) transaction failures

https://technet.microsoft.com/en-us/library/ff360043(v=exchg.140).aspx

Regards,

Yan Li

Hi Sanjeev,

Seems that there is some issue in the SSL Certificate / issue where some one can get in to your web site due to some security issue which SCOM has detected.

So may be an update / patch installation in the exchange server may fix this vulnarability. So suggest you to check with your exchange Administrator once about this issue.