Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Additional web server fails to load node details

Additional web server fails to load node details

Updated January 11, 2017

Overview

When trying to view node details from an additional web server, you may receive one of the following errors:
Error 1:  
Error message "Could not connect to net.tcp://server:0/orion/npm/businesslayer. The connection attempt lasted for a time span of 00:00:00. TCP error code 10049: The requested address is not valid in its context IPADDRESS:0."
 

Error 2 (Found in the SolarWinds Information Service V3 log):

ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - (null) (null)  An error occured opening a connection to the orion communication service.
System.ServiceModel.EndpointNotFoundException: No DNS entries exist for host HOSTNAME. ---> System.Net.Sockets.SocketException: No such host is known

Environment

  • All NPM versions
  • Orion

Cause 

Cause 1:  

The additional web server may show up in the Engines table on the database as a primary polling engine with a port of NULL.  

 

Cause 2:  

The Additional Web Server (AWS) is unable to communicate with the main Orion server by Fully Qualified Domain Name (FQDN).  

Resolution

For Error 1:  

Delete the Additional Web Server (AWS) entry from the Engines table on the Orion database.

 

For Error 2:  

Ensure that the Additional Web Server (AWS) can contact the main Orion server using FQDN.  If necessary, manually add a record for the Fully Qualified Domain Name (FQDN) of the main Orion server to the local hosts file on the AWS.  

 

Last modified
14:01, 13 Apr 2017

Tags

Classifications

Public