Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Engineers ToolSet (ETS) > ETS - Knowledgebase Articles > Enable HTTPS for Engineer's Toolset on the Web when unable to discover interfaces, volumes, and other components

Enable HTTPS for Engineer's Toolset on the Web when unable to discover interfaces, volumes, and other components

Updated September 13th, 2017


Engineer's Toolset on the Web is installed on a server with HTTPS enabled. It is not discovering interfaces, volumes, and other components. 


The following error can occur when running Configuration wizard a second time.

"Exception while configuring plugin Orion Toolset component Toolset Website Cannot create a file when that file already exists"

Step 5 is relevant with this error. 


Engineer's Toolset on the Web 11 


The default installation does not connect to an HTTPS website, and bindings are not set to all unassigned in IIS.


Follow these steps to enable HTTPS functionality for Engineer's Toolset on the Web:

  1. In the Orion database's websites table, confirm that the SSLEnabled value is 1 (enabled).  If SSLEnabled value is 0, use the following query to update the value to 1
    UPDATE dbo.Websites
    SET SSLEnabled=1
    WHERE WebsiteID=1
  2. In C:\inetpub\SolarWinds\Orion\Toolset, rename the file web.config to web_http.config.
  3. In C:\inetpub\SolarWinds\Orion\Toolset, rename the file Web_SSL.config to web.config
  4. In C:\Program Files (x86)\SolarWinds\Orion\Toolset (Toolset default installed location), rename SolarWinds.Toolset.BusinessLayer.dll.config to SolarWinds.Toolset.BusinessLayer.dll_http.config.
  5. In C:\Program Files (x86)\SolarWinds\Orion\Toolset (Toolset default installed location), rename  SolarWinds.Toolset.BusinessLayer.dll_SSL.config to SolarWinds.Toolset.BusinessLayer.dll.config.

    Do not leave a copy of the SolarWinds.Toolset.BusinessLayer.dll_SSL files in the directory or in any of the program files directory.

  6. Move the D:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll_http.config to desktop
  7. Enable WCF HTTP Activation in IIS in the Control Panel on the SolarWinds server as described below:
    1. Control Panel>Turn Windows features on or off> next> In features, select .Net Framewark Features>Expand WCF Services>Select HTTP Activation>Install
  8. Restart all Orion services using Orion Service Manager.
Last modified