Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
A couple of days ago a trigger for a task setted on multiple events completed has stopped working without any change on task schedules. Looking in the logs I found that file "Root_YYYYMMDD.txt" has the following entries:
4/5/2012 02:42:06.4842657 Information TaskCompletedTrigger 03a856ca-06fc-4afe-8098-80ad61a7901b <1> of <4> fired. AndTrigger: 83c9232b-e1f6-4b85-a68a-ff40084a7d20
4/5/2012 02:42:06.4842657 Information TaskCompletedTrigger c3b0d8ba-f3ee-4fc8-a1d1-f163a14cdfc5 <2> of <4> fired. AndTrigger: 83c9232b-e1f6-4b85-a68a-ff40084a7d20
4/5/2012 02:42:06.4842657 Information TaskCompletedTrigger f263eb79-83f7-4fff-abcc-63771fa7bf66 <3> of <4> fired. AndTrigger: 83c9232b-e1f6-4b85-a68a-ff40084a7d20
4/5/2012 02:42:06.4842657 Information TaskCompletedTrigger d15a0334-e2aa-4b1b-9c48-e879f8456492 <4> of <4> fired. AndTrigger: 83c9232b-e1f6-4b85-a68a-ff40084a7d20
4/5/2012 02:42:06.4842657 Information Time constraint encountered for AndTrigger: 83c9232b-e1f6-4b85-a68a-ff40084a7d20. TaskCompletedTrigger kept with ID c3b0d8ba-f3ee-4fc8-a1d1-f163a14cdfc5 and new StartTriggerTime (for AndTrigger): 4/5/2012 2:42:06 AM
Looking the xml configuration files, I found that the trigger id 83c9232b-e1f6-4b85-a68a-ff40084a7d20 is the trigger that stopped working.
The trigger's time constraint is set on 360 minutes. All the previous tasks ended in less time. I guess that a previous run of the trigger was alive and waiting.
After the first fail, it fails consistently every day. When something similar happened in the past, we fixed it re-creating the trigger. These
Any ideas?
i just got word from QV that this is an official bug (bug ID 39161), and is slated for a fix in QV10SR5, (probably next week).
the workaround is, to recycle the Distribution Services service
i just got word from QV that this is an official bug 39161, and is slated for a fix in QV10SR5, (probably next week).
the workaround is, to recycle the Distribution Services service
i just got word from QV that this is an official bug 39161, and is slated for a fix in QV10SR5, (probably next week).
the workaround is, to recycle the Distribution Services service
i just got word from QV that this is an official bug 39161, and is slated for a fix in QV10SR5, (probably next week).
the workaround is, to recycle the Distribution Services service
i just got word from QV that this is an official bug 39161, and is slated for a fix in QV10SR5, (probably next week).
the workaround is, to recycle the Distribution Services service