Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > 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: 126 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
23:18, 22 Jun 2016

Tags

Classifications

Public