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.
--- End of inner exception stack trace ---
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
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 editing it and only make registry changes according to our instructions. Failure to follow these instructions can introduce errors into the application or, in some situations, cause operating system issues.
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.