Network Management

Desktop Alert Notification Tool is unable to connect to the server

The Desktop Notification Tool (DNT) is unable to connect to the server and the following error appears: The exception has been thrown by the target of an invocation. DNT is a client used by the Play a sound alert action.

First published date

11/2/2018 9:23 AM

Last published date

2/26/2025 2:53 AM

Overview

The Desktop Alert Notification Tool is unable to connect to the server and the following error appears: 
The exception has been thrown by the target of an invocation. 

 

When this problem occurs, the Orion Server - Windows System event log displays an error message pertaining to the untrusted certificate. A log example is provided below:

 

Schannel,(0),DOIT-PVOSW01.NMADS.lcl,"The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate.

3/30/2015 3:55:16 PM",Schannel,(0),DOIT-PVOSW01.NMADS.lcl,"A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 48. The Windows SChannel error state is 552.

 

The DNT fails with the following message:

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> The remote certificate is invalid according to the validation procedure.
 

Product section

Network Performance Monitor

Cause

This issue occurs when you use a self-signed certificate on the Orion website that the Desktop Notification Tool does not trust.

Resolution

  1. Using the MMC Snap-In on the server hosting your Orion Web Console, export your Orion Web Console server's SSL certificate to .pfx.
    This is the certificate bound to your Solarwinds NetPerfMon site in IIS, self-signed or otherwise.
    Choose ".pfx" format with all extended properties chosen. See How to view certificates in the MMC Snap-in 

  2. Import the Orion Web Console's certificate to the Trusted Root Certification Authorities certificate store on your client computer.
    1. Copy the exported ".pfx" file to your client computer(s). 
    2. On your client computer(s), start a new MMC by launching "MMC.exe" and then navigate to File Add/Remove Snap-In, and then click Add. 
    3. Choose Certificates and click Add.
    4. Choose Computer account and then click Next.   
    5. Choose "Local Computer" for what the Snap-In will manage and click Finish. Click Ok again to exit the Add or Remove Snap-Ins window.
    6. Right-click the "Certificates" folder under "Trusted Root Certificates Authorities" and choose "Import".
The certificate was added to trusted certificates, so the issue stops occurring. 


 

If the above solution does not work, verify which port is running IIS and try to connect to the address:

hostname:port


 The Desktop Notification Tool is the client used by the Play a sound alert action.