Upgrading 10.1.3 to 10.3.1 Web Console Error

Question

After upgrading to version 10.3.1 I received the following message on the "Finish" configuration wizard window.

There was no endpoint listening at net.tcp://xxx-xxx:17777/orion/core/businesslayer that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

I searched this site but found that this seems to be more of a general issue and that I should submit a ticket through support.  But after looking through some windows logs there were a few events that stuck out..

Error starting plugin Orion

Access to Message Queuing system is denied.

Application: SolarWinds.BusinessLayerHost.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ServiceModel.EndpointNotFoundException

Faulting application name: SolarWinds.BusinessLayerHost.exe, version: 2012.1.12.2305, time stamp: 0x500d30a6

I started with removing and adding message queuing and then rebooted the server.  The web console came up with all my existing configurations.  Haven't run through all of it but things seem to be fine.  Maybe I did something wrong during the update or perhaps there is something that needs to be patched.  Just wanted to pass this info on for anyone getting this error.

zizi · Answer

We've seen some issues with Message Queuing (MSMQ) in the past. Many Orion services are depending on MSMQ, which mean they need to be able to communicate with MSMQ service to work properly. As Orion Module Engine was unable to use MSMQ, it wasn't fully initialized and most likely just got stuck in a start-up phase. That's why Orion Website was unable to connect to it, and you've got that "There was no endpoint listening" error. We were unable to find out, what's causing the issue with MSMQ , but we've noticed that remove/add of the Message Queuing feature fixes the issue. So far, it looks more like an environmental problem with MSMQ installation then a defect in Orion, but we will keep investigating. Please let us know if you run into similar problem again. Thanks!

PavelSrot · Answer

Sometime can happen from any unexpected reason that not all Orion services started after rebooting Windows or upgrade. If you encounter with this issue I would suggest launch Orion Service Manager application (Start -> SolarWinds Orion -> Advanced Features) and try to click on Start Everything or sometimes is needed to first Shutdown Everything and concequently try to Start services again via button Start Everything.