Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > The Orion database is corrupted

The Orion database is corrupted

Updated April 10, 2017

Overview

You experience different errors in SolarWinds Orion products, such as 

  • The nightly database maintenance does not complete. 
  • Database maintenance tasks access excessive numbers of Orion database structures to consolidate statistical data, defragment indexes, etc.
  • The product does not start or crashes.

Additionally, an error message asking to run DBCC CHECKDB command appears in the SQL server logs.

Msg 823, Level 24, State 2, Line 2
The operating system returned error 1(Incorrect function.) to SQL Server during a read at offset 0x00001382b14000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\NetPerfMon.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

 

Environment

  • Any Orion Platform product

Cause

The cause of these problems can vary from file system corruption, underlying hardware system issues, driver issues, corrupted pages in memory, or problems with the SQL Server Engine.

 

Resolution

Ask your database administrator to investigate the issue and perform a full database consistency check, such as running the DBCC CHECKDB command with appropriate options.

 

 

Last modified
15:40, 10 Apr 2017

Tags

Classifications

Public