Configuration Wizard problems explained

11/29/2018 10:39 PM

3/7/2023 5:26 PM

The issues listed in this article have been encountered while completing the Configuration Wizard. When available, a resolution or workaround is provided. If the problem you are having is not addressed in this article, please submit a technical support ticket.

Orion Platform

Configuration Wizard fails

Note: Configuration Wizard logs, which may provide more information about the issues below, can be found at C:\ProgramData\SolarWinds\Logs\Orion.

Configuration Wizard Hangs 

Issue: The Configuration Wizard seems to be hanging without completing.

Resolution: There are some reasons that the Configuration Wizard might appear to be hanging during configuration:

• Frequently, the Configuration Wizard is merely completing a lengthy update of the Syslog and traps tables in the Orion database. The length of time required for this update depends on several factors, including the size of the Syslog and traps tables themselves and the capacity and performance of the SQL Server hosting your Orion database. For more information about maintaining the size of your Syslog and traps tables, see Tips and tricks for managing traps and Syslog in Orion NPM. 
• If you cannot trace the issue to a large Syslog or traps table, it may be helpful to confirm that the IPv4 Large Send Offload option is disabled for all network cards (NICs) on both your Orion server and your SQL Server. 

Cannot delete a SQL user 

Issue: The Configuration Wizard is unable to delete a specific SQL user.

Resolution: This issue is resolved using the SQL Server account to create a new database user account for Orion NPM.

Error 500 

Issue: The Configuration Wizard is displaying an.Error 500

Resolution: This error may be seen when Windows Server Update Services (WSUS) and Orion NPM are installed and enabled on the same server. For more information, see Error upgrading NPM during Configuration Wizard.

Website configuration failed: IIS does not support ASP.NET 2.0 

Issue: Website configuration failed: IIS does not support ASP.NET 2.0; the IIS installation may be corrupt, or you may not have permission to modify IIS configuration settings.

Resolution: This error occurs when the ASP.NET IIS Registration Tool (aspnet_regiis.exe) is not able to completely associate ASP.NET with IIS. Symantec applications with Symantec Enterprise Protection (SEP) Application and Device Control enabled have been known to block from initializing.
To correct this issue:

1. If Symantec Enterprise Protection (SEP) is installed on your Orion Server, disable the SEP Application and Device Control. For more information about a similar operation, see "How to: Disable the SysPlant / SysGuard drivers on SPA clients without manually editing the registry" at www.symantec.com.
2. If SEP is not installed or the solution above does not work, complete the following steps:
   1. Open a command prompt on your Orion server.
   2. Run,c:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i where c:\Windows\ is the default .NET install directory.
   3. Run the Configuration Wizard (Start > All Programs > SolarWinds Orion > Configuration and Auto-Discovery  > Configuration Wizard) again.

Information Service on the primary Orion server  not running or ERROR InfoServiceProxy 

Issue: When running the Configuration Wizard on an Additional Polling Engine, either of the following errors occurs:

1. The Information Service on the primary Orion server is not running. Please start this service before continuing.
2. ERROR InfoServiceProxy - An error occured opening a connection to the orion communication service.
System.ServiceModel.EndpointNotFoundException: No DNS entries exist for host orion. --->
System.Net.Sockets.SocketException: No such host is known
   at System.Net.Dns.GetAddrInfo(String name)
   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
   at System.ServiceModel.Channels.DnsCache.Resolve(String hostName)

Resolution: This error indicates that your additional polling engine cannot connect to the primary Orion server.
To address this condition:

1. Confirm that the Windows firewall is not blocking communications to and from the Additional Polling Engine and your primary Orion server. For more information about open ports required by Orion products, see SolarWinds Port Requirements.
2. If the Windows firewall was blocking required ports, confirm that the blocked ports are open, and then rerun the Configuration Wizard.
3. If the error persists, from the additional polling engine, ping both your primary Orion server's hostname and IP address.
4. If your primary Orion server does not respond to your requests, confirm that you have network connectivity between your Additional Polling Engine and your primary Orion server.
5. If your primary Orion server does respond to your ping requests, confirm that the name and IP address of your primary Orion server is present in the host's file on your Additional Polling Engine, as indicated in the following steps:
   1. Navigate to the hosts file on your Additional Polling Engine.
      Note: The default location is Volume:\Windows\System32\drivers\etc
   2. Open the hosts file in a text editor.
   3. Add the IP address and hostname of your primary Orion server, as indicated in the comments within the hosts file.
6. If the error persists after confirming that the Windows firewall is open on all required ports and that your primary Orion server's IP address and hostname are included in the host's file of your Additional Polling Engine, submit a technical support ticket.

Unable to start SWIS ('System.FormatException') 

Issue: While completing the Configuration Wizard, I see the following error:
Unable to start SWIS ('System.FormatException')
This issue is caused by corruption in the performance counter library values in your Orion server's registry.
Resolution: To fix this issue, follow the steps provided in the Microsoft Support article, "How to rebuild Performance Counter Library values manually."
 

ERROR ConfigurationProgressScene 

Issue: The Configuration Wizard generates the following error:
ERROR ConfigurationProgressScene - Exception while configuring plugin Orion Core Services component Orion Information Service. System.Security.Cryptography.CryptographicException: Access is denied.
Resolution:

Would you please follow the steps mentioned in the KB post 

ERROR ConfigurationProgressScene - Exception while configuring Orion Core Services component Orion Information Service plugin. System.Security.Cryptography.CryptographicException: Access is denied . 

if you still have the issue. To correct this error, submit a technical support ticket requesting a license reset. You will need to provide diagnostics to confirm that this is indeed your issue.

Website Configuration Failed - remote server returned an error (403) forbidden. 

Issue: After the configuration wizard, you get the following error:
Website Configuration Failed - Web request for /Orion/Login.aspx failed - The remote server returned an error: (403) forbidden.
Resolution:   This is expected behavior if you are running HTTPS - as a final step, the configuration wizard tries to log in to the website via HTTP/Port 80. The web console will function as normal when the correct protocol is specified.

See Configuration Wizard error: Web Request for /Orion/Login.aspx failed .
 

Database configuration failed: Error while executing script- The current transaction cannot be committed and cannot support operations that write to the log file. Rollback the transaction.

Issue: database setting needs to be corrected
Resolution:   From SSMS - run this - select @@options - uncheck  XACT_ABORT