WARN Error - Exception in ExecuteTriggerActions

Question

Completely out of the blue, configuring advanced alerts has stopped working...

When I start the Advanced Alert Manager, the window opens okay, and I can look at current events or active alerts, but when I click the "Configure Alerts" button an error window pops up with "AlertManager" in the title bar, and the following error:

"Run-time error '5':  Invalid procedure call or argument"

and then Advanced Alert Manager closes.

An informational even shows up repeatedly in the Solarwinds.Net Applications and Services Log in Event Viewer.  The following are the details of the event:

2012-10-16 17:19:29,542 [AlertCheckingThread] WARN Error - Exception in ExecuteTriggerActions - 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() at AlertingEngine.CheckAlert.ExecuteTriggerActions()

I can connect to the SQL database used by Orion just fine with SQL Server Management Studio.  Any advice on resolving this issue would be helpful.

FormerMember · Answer

Thanks for your response - the server reboot seemed to clear my inability to access the Advanced Alert Manager-Configure Alerts section, but I continue to see errors on SWJobEngineWorker2.exe in Windows Event Log, so I am attempting to repair the service...

rjnicholson · Answer

I am seeing my SWJobEngineWorker2 dying on my secondary poller as well after a recent upgrade to SAM 5.2.

I haven't seen the Alert Manager issue yet though, and I use mine daily.  I have been able to restart the JobEngineWorker2 which is easy to spot since all polls from the poller won't write to the DB and I use the pre built alert to notify me when nodes haven't written to the DB in 10 mins.

I got a response from  about repairing/reinstalling these services which I will run in a maintenance window and see if I can repair it.  Below is a link to this post.

This is the response I got to try before I proceed in opening a Ticket since they would ask me to do this first as well.  If it continues after the repairs I will follow up with a ticket, but figured this information could help you in regards to the SWJobEngineWorker2 dying on you as well.

Maybe this is related to the Alert manager dying.  I can't say it is since this is happening on my secondary poller and the alert manager resides on my primary box where I have no issues with this service we both have mentioned.

FormerMember · Answer

Well, I'd still like to know what caused the issue, but a server reboot seems to have cleared the error....