4 Replies Latest reply on Jan 24, 2014 9:32 AM by crzyr3d

    AlertingEngine timeout errors.


      Hi, I receive about 10 messages like this every 10 minutes. Is there a way to increase AlertEngine query timeout?

      Event Type: Information
      Event Source: AlertingEngine
      Event Category: None
      Event ID: 0
      Date:  11/23/2009
      Time:  4:14:09 PM
      User:  N/A
      Computer: AAA001
      2009-11-23 16:14:09,673 [AlertCheckingThread] WARN  Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects
      System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
         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()


        • Re: AlertingEngine timeout errors.

          Ironically enough, years later I'm also having the same issue and it seems to be messing things up.

            • Re: AlertingEngine timeout errors.

              If you are getting these errors frequently, from our experience, it is an indication something is tying up the database (e.g., locks, deadlocks) causing the alertingengine query to timeout. An occasional timeout should be no harm. We commonly see one at the time the daily sql maintenance backup job cranks up.

                • Re: AlertingEngine timeout errors.

                  You are correct. The Alerts by default are executed every 60 seconds and have a timeout just before the new Alert is queried again. If you are seeing a lot of these Errors you can check the database to find out which Alerts are having this issue. We log the timestamp of when the error last occurred as well.


                  --SQL Query to pull back the Alert Name, Description of the Alert, SQL Query used, Last Time the Alert was executed, Last Time that the Error Occurred, Error Reported.

                  Select AlertName, AlertDescription, TriggerQuery, LastExecuteTime, ResponseTime, LastErrorTime, LastError from AlertDefinitions where LastErrorTime is not null