Event Log Trigger Crashing Application 8.2.0 - VisualCron - Forum

Community forum

rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-06T16:00:18Z
Having issues using the Event Log Trigger in version 8.2.0. The trigger is causing the application to crash the service. The below error is being output. Running on Server2012R2.

Application: VisualCronService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.PNDOIPEJICOONBJAEPPCINMKAFPIELNKHGIG.DMBMGBMAGCEPOOOFPHCEMMGNBFGMKBEHJDMJ(System.Diagnostics.Eventing.Reader.EventRecord, System.Exception)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.PNDOIPEJICOONBJAEPPCINMKAFPIELNKHGIG.KFACCCGBJMJMADEHJPFHLIBAMGLJJLKLOBDB(System.Object, System.Diagnostics.Eventing.Reader.EventRecordWrittenEventArgs)
at System.Diagnostics.Eventing.Reader.EventLogWatcher.HandleEventsRequestCompletion()
at System.Diagnostics.Eventing.Reader.EventLogWatcher.RequestEvents()
at System.Diagnostics.Eventing.Reader.EventLogWatcher.SubscribedEventsAvailableCallback(System.Object, Boolean)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(System.Object, Boolean)

Any help with the issue would be appreciated. Thanks!
Support
2016-10-06T17:01:49Z
Thanks for the report, we have just uploaded latest build of 8.2.1 with more debugging. Could you please install it? It should not crash now but give an error to the file log_serverDATE.txt which we would like to have (zipped please):

http://www.visualcron.co....aspx?g=posts&t=6875 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-07T10:40:22Z
  log_server20161006.zip (2kb) downloaded 45 time(s).

Here is the relevant portion of the log.

Thanks!
Support
2016-10-07T12:47:23Z
Thank you. Please test this version and upload the same file again please. Also, please upload a screenshot of Event Trigger settings.


Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-07T15:28:02Z
Support
2016-10-08T14:34:13Z
Thanks, now please test this version - it should be fixed now - thanks:

http://www.visualcron.co....aspx?g=posts&t=6875 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-10T19:26:27Z
That looks to have solved it. Thanks!
Support
2016-10-11T12:42:15Z
Great, thank you for your patience and testing!
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-11T15:59:18Z
Unfortunately looks like there is a different issue now. The event log trigger is working, however it is now ignoring the polling interval and executing the job for any time the event log entry was posted not just within the polling interval. For example if a event log entry was made 3 hours ago, whne enabling the trigger it will fire the job instead of realizing that is an old entry and looking only for new ones.
Support
2016-10-11T21:18:55Z
Strange. It is true that polling is not relevant anymore as it reacts right away instead of actually poll. So, basically it cannot react on old events. Have you tried to log the event id etc. to make sure it is really not old events?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-14T15:39:25Z
So we finally got around to some testing. Looks like the job will run multiple times based of the same event log entry from the past. When we attempted to use the Event log Id and description values it was unable to trigger off the event at all.
Support
2016-10-14T15:57:19Z
What I meant was to log the incoming Event log data. For example, you could create a Write file Task that appends this to a file:

{DATEFORMAT(yyyy-MM-dd HH:mm:ss)}: {TRIGGER(Active|LastTrigger|EventLog.Result.RecordNumber)} - {STRING(Substring|{TRIGGER(Active|LastTrigger|EventLog.Result.Message)}|0|30)}

Then you will see if there are unique record id's and messages.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-14T16:00:57Z
We can give that a try. We are creating these event entries though. This is not an normal event type. We are intentionally writing to the event log to trigger a job.
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-14T16:23:31Z
  eventlogtest.txt (1kb) downloaded 43 time(s). eventlogtriggerconfig.png

Looks like the trigger is just firing on every new log entry, not filtering based on what we set as the description.

Thanks!
Support
2016-10-14T18:30:54Z
Thanks, it seems like there was a problem in the filter. Please re-download and re-install:

http://www.visualcron.co....aspx?g=posts&t=6875 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-17T17:46:51Z
We are no longer seeing it trigger on every event log entry, but now it is not triggering based on our filter. We have tried description and event id and it will not trigger the job.
Support
2016-10-17T18:44:59Z
Please send screenshots of current settings.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
rst3b
  •  rst3b
  • No customer Topic Starter
2016-10-17T18:58:07Z
Same settings as in the previous screenshots.
Support
2016-10-18T18:49:15Z
So just the Message/Description and the log name?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2016-10-19T13:53:11Z
As we cannot reproduce this we have added more debugging in this build: http://www.visualcron.co....aspx?g=posts&t=6875 

Please download and turn on Extended debugging in Sever settings. Now, when it triggers on even that you feel should not trigger on please find the file log_serverDATE.txt and zip and email it to support@visualcron.com
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top