Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Server & Application Monitor (SAM) > Connection failed to url. The underlying connection was closed: Could not establish trust relationship for the SSL-TLS secure channel

Connection failed to url. The underlying connection was closed: Could not establish trust relationship for the SSL-TLS secure channel

Updated April 20, 2017

Overview

The following error is encountered when using the OWA Form Login monitor:

The "Exchange 2010 OWA Form Login (PowerShell)" Application fails with the following error: "Connection failed to URL.  The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."

Environment

All SAM versions

Cause 

The System.Net.ServicePointManager.ServerCertificateValidationCallback object is disabled in the PowerShell script. 

Resolution

Modify the Windows PowerShell monitor script within the "Exchange 2010 OWA Form Login (PowerShell)" application to enable the System.Net.ServicePointManager.ServerCertificateValidationCallback object from:

#This command set the static property in .NET that causes the error in HTTPS probes.
#[System.Net.ServicePointManager]:ServerCertificateValidationCallback = {$true}

to

#This command set the static property in .NET that causes the error in HTTPS probes.
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}

 

Note: A problem in the .NET implementation may cause HTTPS monitors to fail with the following error when the OWA script is used with other HTTPS monitors:

Unexpected error occurred. The underlying connection was closed: An unexpected error occurred on a send.

To prevent this, switch all HTTPS processes to 64-bit mode and keep the OWA PowerShell script running in 32-bit mode:

1. Go to Settings > SAM Settings > Manage Application Monitors.

2. Select the application that contains the HTTPS component and click Properties.

3. Open the Advanced section and set the Platform to run polling job on to x64.

4. Click Submit.

 

 

Last modified
00:24, 20 Apr 2017

Tags

Classifications

Public