Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion Services do not start after a reboot when SQL is installed on the Orion server

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

Created by Erica Gill, last modified by MindTouch on Jun 23, 2016

Views: 1,993 Votes: 1 Revisions: 3

Overview

This article addresses the issue where Orion Services do not start after a reboot when they are installed on the same server as the Orion database.

Environment

Orion 2015.x and earlier

Cause 

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

Resolution

Set the SolarWinds services Startup type to Automatic (Delayed Start) using the Windows Services MMC. See the Step-by-Step Guide to the Microsft Management Console.

 

 

Last modified

Tags

Classifications

Public