Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Solarwinds Cortex Service will not start

Solarwinds Cortex Service will not start

Created by Kevin Twomey, last modified by Steve.Hawkins on Dec 04, 2017

Views: 48 Votes: 0 Revisions: 3

Updated December 4, 2017

Overview

In NPM 12.2, the SolarWinds Cortex Service will not start.

The SolarWinds Cortex Service is a new feature in Core 2017.3 and higher.

Environment

  • Core 2017.3 or higher
  • NPM 12.2 or higher

Cause 

The four Cortex file groups are missing in the Orion database. No files are assigned to the "CORTEX_DOCUMENTS" file group.

For example, if the Orion database is installed on the D drive, the following should be visible:

'D:\DATA\SolarWindsOrion.mdf'

'D:\LOG\SolarWindsOrion_LOG.ldf'

'D:\DATA\SolarWindsOrion_Cortex_documents1.ndf'

'D:\DATA\SolarWindsOrion_Cortex_documents2.ndf'

'D:\DATA\SolarWindsOrion_Cortex_documents3.ndf'

'D:\DATA\SolarWindsOrion_Cortex_documents4.ndf'

Additionally, the following error message displays in the Cortex.log file:

2017-11-20 09:52:07,270 [5] FATAL SolarWinds.Cortex.Hosting.SubsystemManager - Error starting Cortex subsystems.
System.AggregateException: One or more errors occurred. ---> System.Data.SqlClient.SqlException: The filegroup "CORTEX_DOCUMENTS" has no files assigned to it.
Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added. Line 4

Resolution

Recreate the CORETEX file groups. Run the configuration wizard on the Main Poller first. If this does not help, run SQL to create the file groups.

The following example shows a database named SolarWindsOrion installed on a D drive on the SQL server.

 

ALTER DATABASE [SolarWindsOrion] ADD FILEGROUP [CORTEX_DOCUMENTS];

ALTER DATABASE [SolarWindsOrion] ADD FILE 
(
NAME = 'Cortex_documents1',
FILENAME = 'D:\DATA\SolarWindsOrion_Cortex_documents1.ndf',
SIZE = 5 MB,
FILEGROWTH = 1024 MB
), 
(
NAME = 'Cortex_documents2',
FILENAME = 'D:\DATA\SolarWindsOrion_Cortex_documents2.ndf',
SIZE = 5 MB,
FILEGROWTH = 1024 MB
), 
(
NAME = 'Cortex_documents3',
FILENAME = 'D:\DATA\SolarWindsOrion_Cortex_documents3.ndf',
SIZE = 5 MB,
FILEGROWTH = 1024 MB
), 
(
NAME = 'Cortex_documents4',
FILENAME = 'D:\DATA\SolarWindsOrion_Cortex_documents4.ndf',
SIZE = 5 MB,
FILEGROWTH = 1024 MB
) TO FILEGROUP [CORTEX_DOCUMENTS];

 

When you are finished, check the CORTEX logs on the Orion server or use the diagnostics. The results of the following query can help to verify that the file group was created successfully.

 

SELECT *
FROM sys.database_files sdf
INNER JOIN sys.filegroups fg ON sdf.data_space_id = fg.data_space_id
.

 

Suggested Tags:  Cortex

 

A reason for rework or Feedback from Technical Content Review:

 

 

Last modified

Tags

Classifications

Public