Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > ERROR: There was an error communicating with the Orion server

ERROR: There was an error communicating with the Orion server

Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 1,786 Votes: 1 Revisions: 9

Overview

The article explains a possible resolution to fixing an error that happens when using the 'Additional Web Console' address to access Orion:

 

There was an error communicating with the Orion server

OrionWeb.log Related Error:

ERROR SolarWinds.VIM.Web.VimProfile - Unable to load VIM user properties from database.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://nocmgmt-pr01:17777/orion/vim/businesslayer that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

 

Environment

All Additional Web Poller

Cause 

This may be caused by an incorrect address in the websites.

Resolution

  1. Open the Database Manager on the Orion server. Refer to Adding a Server.
  2. Query the websites table. Run the following in the command line:
    SELECT * FROM [dbo].[Websites])
  3. Check if ServerName and IPAddress match AWE.
  4. Remove all excess entries that are not functioning.
  5. Verify that the server name resolves via an NSLOOKUP command from the Main Orion server and the AWE. Refer to Nslookup
     

Possible key to resolution:

Check the Engines  table for two primary engines by running the following query in database manager: 

SELECT * FROM [dbo].[AllEngines] or SELECT * FROM [dbo].[Engines]

How to use Database Manager

 

   1.  Remove duplicate Engine entries. For example,query Delete FROM [dbo].[AllEngines] Where EngineID ='3'

   2.  Restart all Orion services using the Orion Service Manager

Last modified

Tags

Classifications

Public