Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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

The Orion database is corrupted

Updated April 10, 2017


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.



  • Any Orion Platform product


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.



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