Network Management

Additional web server fails to load node details

This article describes how to resolve an issue with accessing the node details page using the additional web server.

First published date

10/23/2018 8:51 PM

Last published date

10/23/2018 8:51 PM

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

Product section

Network Performance Monitor

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.