AlertingEngine Event Log Error

Question

I am getting an error in the event log that is sourced from the AlertEngine. The error reads:

2007-11-26 08:12:03,018 [AlertCheckingThread] WARN  Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects
EXCEPTION STACK: -->  Ambiguous column name 'NodeID'. : .Net SqlClient Data Provider :    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();;;

Has anyone ever seen this error?

Mike_C · Answer

I am also getting the same errors, however mine only occur at 2 specifiec times of day   2:17am a and 4:00am   Since these do not occur at all times of day, the 'shutdown of all alerts and enable one at a time' would not work in this senario.  Any suggestions??

SamuelB · Answer

I'd recommend that you open a Support ticket for that one. I already have ticket # 24077 open from 11/16. 1. 1. Edit the AlertingEngine.exe.config file. Find this section: And change NONE to ALL. That will increase the logging and should let us figure out which query is bombing out. 2. 2. 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. Followed the above steps and was able to locate the alert causing the errors. Thanks Mark!

mark_wiggans · Answer

Sam- This might be caused by a malformed query- A couple of suggestions to try are: 1. 1. 1. Edit the AlertingEngine.exe.config file. Find this section: And change NONE to ALL. That will increase the logging and should let us figure out which query is bombing out. 2. 2. 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.