Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Error starting service manager

Error starting service manager

Updated January 17, 2017


Upon opening Orion Service Manager, you may receive the Error starting service manager message. After the message is received, the Orion Service Manager opens but is missing a few expected components.


The following error is found in the OrionServiceManager.log:

DEBUG IISConfiguratorFactory - IIS version from registry: '0.0'
ERROR Form1 - System.TypeInitializationException: The type initializer for 'SolarWinds.ConfigurationWizard.Common.IISHelper' threw an exception. ---> System.NotSupportedException: IIS version 0.0 is not supported yet.
 at SolarWinds.ConfigurationWizard.IIS7.IISConfiguratorFactory.GetInstance()
 at SolarWinds.ConfigurationWizard.Common.IISHelper..cctor()
 --- End of inner exception stack trace ---
 at SolarWinds.ConfigurationWizard.Common.IISHelper.IsIISInstalledAndRunning()
 at OrionServiceManager.Form1.Form1_Load(Object sender, EventArgs e)


When checking the Windows Registry, you will find that the following key contains no subkeys:



Products running on Orion Platform 2017.1 and earlier, including additional polling engines, such as

  • NPM 12.1 and earlier
  • SAM 6.4 and earlier


The registry is missing a key value pair in IIS for MajorVersion.  This is most likely due to non-Solarwinds environmental issues.


IIS is not a required component on an Additional Polling Engine. 



SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

  1. Log in to the Orion server as an administrator.
  2. Open the registry editor, and navigate to HKLM\Software\Microsoft\InetStp.
  3. Create a new DWORD value called MajorVersion, and enter the major version number of your IIS install as the value data.
  4. If your OS is 64-bit, you must also create the same key in HKLM\Software\Wow6432Node\Microsoft\InetStp.
  5. Create a new DWORD value called MajorVersion, and enter the major version number of your IIS install as the value data.

You can run to Orion Service Manager without error.


If you experience this issue on an additional polling engine, you can also install IIS as a workaround. If you are concerned about having IIS installed due to security or performance reasons, you may then try to uninstall the IIS component and the needed registry entries should remain.


Please see the below resource for more information on how to install IIS:

© 2017 Microsoft



Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified