Network Management

Configuration Wizard Failed: Connection to Businesslayer service did not succeed.

This article covers where the configuration wizard shows an error that businesslayer service connection did not succeed due to timezone problem.

First published date

10/10/2018 2:48 PM

Last published date

6/29/2021 3:34 AM

Overview

The following error occurs:
 

Website configuration failed:

Connection to the SolarWinds BusinessLayer Service did not succeed. 
Last error: There was no endpoint listening at net.tcp://hostname: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.


Sample Image:

image.png


-OR-
 

Website configuration failed:

Connection to the SolarWinds BusinessLayer Service did not succeed. Last error: 
Exception of type 'SolarWinds.ApiProxyFactory.TransientApiProxyException' was thrown.

 

Sample Image:
 

image.png

 

Product section

Network Performance Monitor

Cause

Cause 1: During the Configuration Wizard made a call to the Primary Polling Engine Business Layer while the Module Engine on the Primary Poller was in a Stopped State
 

Cause 2: The Additional Polling Engine and the Main Polling Engine timezone are not in sync

Cause 3: Main Polling Engine and SQL Server timezone are not in sync

Resolution

Resolution 1:

1. Restart the Orion Module Engine on the Primary Poller:

a. Log into the Solarwinds Server.
b. Open Orion Service Manager.
c. Click Start Everything.
 
2. Confirm that the service is running in services.msc. Sometimes it can be stopped in this window while appearing to be active in Orion Service Manager
3. If the service is started them verify the times on both servers match. 
 

Resolution 2:

  • Make sure the Additional Polling Engine timezone matches with the Main Polling Engine; if not make the change then rerun the Configuration Wizard on the APE.

Resolution 3:

  • Make sure Main Polling Engine and SQL Server timezone are the same; if not make the change then rerun the Configuration Wizard on the MPE.