Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > Configuration Wizard fails with an error: Fatal error 824 occurred at XX/XX/XXX X:XX Note the error and time, and contact your system administrator

Configuration Wizard fails with an error: Fatal error 824 occurred at XX/XX/XXX X:XX Note the error and time, and contact your system administrator

Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 1,450 Votes: 0 Revisions: 4

Updated June 9, 2016

Overview

This article goes over an error that can occur during the configuration wizard or any other database update where it fails with the following error:

2016-05-24 08:07:10,216 [19] ERROR DBConfigProcessor - Error while executing script - Warning: Fatal error 824 occurred at May 24 2016  8:07AM. Note the error and time, and contact your system administrator..
 Error details: System.Data.SqlClient.SqlException (0x80131904): Warning: Fatal error 824 occurred at May 24 2016  8:07AM. Note the error and time, and contact your system administrator.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at SolarWinds.ConfigurationWizard.Plugin.Common.DBConfigProcessor.ExecuteSqlBatch(IDbConnection connection, String sqlQuery, ConfigurationLogDelegate configLog)
ClientConnectionId:c30e1bec-2c20-4d23-a13f-1f3f9a0b3055
Error Number:21,State:1,Class:24
 Failing Sql command:

Environment

  • All Orion core versions
  • All SQL Server database versions

Cause 

The issue is caused by the SQL server where it is at a point where it cannot process or read\write data to and from the disk it is utilizing. This means that either there is something specifically wrong in the SQL itself or more likely, there is something wrong with the disk where the data is being written.
Please note that this issue is specific to the SQL database and not with the Orion application or any of its modules. We may utilize SQL as many other vendors do, but for actual issues with SQL, it's deployment and environment, the support on that resides with Microsoft.

Resolution

This issue is specifically with the SQL database, so there may be other possible ways to resolve this issue. One such method is this:

 

What you can do is the following:

  • If you have a SQL DBA, contact them regarding this error and have them confirm the database is healthy and that the disk(s) the database is stored on is fine. If you have no DBAs, then I strongly recommend contacting Microsoft for assistance with correcting or repairing the database.
  • Verify where the SQL data files are stored on the server. Verify if the disk it's stored on is correct and present. If it has been removed, corrupted or the disk itself is having problems, then you will need to correct this
  • If the disk has no issues at all, you will need to open the database using SQL Studio and run this query:
    dbcc checkdb
  • That will give you an idea of what is happening with the database. If it is corrupt, you may need to run it again with a dbcc checkdb with the syntax REPAIR_REBUILD at the end to repair the database. It would look like this:
    dbcc checkdb repair_rebuild

 

 

 

Last modified
21:56, 22 Jun 2016

Tags

Classifications

Public