SolarWinds Services do not start after a reboot when SQL is installed on the SolarWinds Platform server

This article addresses the issue where SolarWinds Services do not start after a reboot when they are installed on the same server as SQL server for the SolarWinds Platform Database.

You may experience issues of services starting and running but the web console not working properly. If the SolarWinds services try to start before or at the same time as SQL server it is possible that the services will not be able to open a connection to the database causing them to not start correctly. The service may show as running in service manager even though they are not working properly due to no Database Connection.

When SQL is installed on the same server as the SolarWinds Platform, the SQL service and SQL instance may take some time to start up. If the SolarWinds Services start before the SQL instance is servicing, connections may be unable to open and may fail to start up.

Set all SolarWinds services Startup type to: "Automatic (Delayed Start)" using the Windows Services MMC. 
See the following screenshot for an example:

Please make sure that you update all the SolarWinds services to Automatic Delayed Start for best results.

You can do this quickly with PowerShell: 

Get-Service -DisplayName "Solar*" | ForEach-Object {
    sc.exe config $_.Name start= delayed-auto
}