Our website has been crashing on the node details page consistently every 9-12 hours. We receive this error:
There was an error communicating with the Orion server
There was no endpoint listening at net.tcp://<localhost>: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.
Help me fix this
- 1. Confirm that the SolarWinds Information Service is running.
- On your local SolarWinds server, click Start > Administrative Tools > Services.
- Right-click SolarWinds Information Service V3, and then click Start.
- 2. Confirm that the SolarWinds Orion Module Engine service is running.
- On your local SolarWinds server, click Start > Administrative Tools > Services.
- Right-click SolarWinds Orion Module Engine, and then click Start.
- 3. Examine the specific details of the error for environmental hints to help resolve your issue.
- 4. Refresh the web console browser.
- 5. If still unresolved, click the troubleshooting help links below.
- 6. After completing any changes, repeat the same task that generated this error.
Save error report locally Return to home
For more troubleshooting help, see the SolarWinds Knowledge Base , or contact support
After a month of troubleshooting with support, we are running out of ideas as to what the root cause is and they are suggesting a fresh install of all Orion products on a new server may be in store. I am asking what all I should be worried about in this process. Some things are not stored on the database and need to be accounted beforehand. We are running NPM, NTA, NCM, VNQM, SAM, SRM, and DPA integration on the latest versions. Here is what I have thought about so far:
1. Maintenance window schedules
2. Custom reports
3. SNMP Trap and syslog rules
4. Application specific settings
