SQL errors found in the event viewer for NPM v.10

I am running Orion NPM version 10 with Service Pack 1. My event viewer for SolarWinds is getting hammered with SQL errors (8 a minute, sometimes more). Any information to get rid of these would be appreciated.

Notes: Originally the install was done with NPM 9. I built a brand new machine, beefier than Grandpa's chili and installed NPM v.10 and attached it to the old database. I imagine the errors are coming from tables/row changes in the newer software... but how to fix?

There are two errors:

1. (Error in Update Rows That Are Reset)

2010-09-13 15:39:25,052 [AlertCheckingThread] WARN Error - Error in UpdateRowsThatAreReset() -
System.Data.SqlClient.SqlException: Invalid column name 'CPUmon'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   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)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at AlertingEngine.CheckAlert.UpdateRowsThatAreReset()

2. (Error in Update Rows That Are Triggered)

2010-09-13 15:39:25,067 [AlertCheckingThread] WARN Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects
System.Data.SqlClient.SqlException: Invalid column name 'Scripts'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   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)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at AlertingEngine.CheckAlert.UpdateRowsThatAreTriggered()

Find more posts tagged with

Accepted answers

jasonbrown

Thanks for the response .. I found some other posts talking about bad alerts. At some point some of our custom fields were modified and caused alert issues.

The steps provided by lhorstma makes it easy to find the bad alert.

All comments

bshopp

Best path is going to be to open a support ticket so our support team can further investigate what is going on here.

jasonbrown

Did you ever find out what was going on here? I am seeing the same thing, 8 of these messages every min.

lhorstma

I have a similar issue, the response I got from support is that I have a bad alert set up. They said:

Open the \Program Files\Solarwinds\Orion\AlertingEngine.exe.config file.

Edit the below section:

    < logger name="UpdateResetRows" >
      < additivity value="true" / >
      < level value="NONE" / >
    < / logger >
Set the level value to ALL. Disable all of the alerts.

Re-enable them one by one, checking the log after each one to see when the errors start showing up again.

Beside checking the Event log, you should see the error(s) in the \Program Files\Solarwinds\Orion\swAlert.log.x files too.

Once you know which alert is causing the issue, disable it and roll back the level value to NONE in the AlertingEngine.exe.config file.

You can probably do the same thing and just find the section for UpdateRowsThatAreTriggered section for the second one and do the same. I haven't done it yet (just got the support response yesterday) so I can't add anything on how well it worked, but will probably work on it this weekend.

jasonbrown

Thanks for the response .. I found some other posts talking about bad alerts. At some point some of our custom fields were modified and caused alert issues.

The steps provided by lhorstma makes it easy to find the bad alert.