Question

workflow subscriber errors in event logs

Workflow

Updated February 12, 2016

asked on February 14, 2014

I have errors that are posted to the event viewer every 2 minutes that more or less read the following:

Timestamp: 2014-02-14 19:08:44.612

Local Time: 02/14/2014 11:08:44 AM

Category: Errors

Machine: XYZ

Severity: Error

Application Domain: Laserfiche.Workflow.Subscriber.exe

Process Id: 4536

Process Name: W:\Program Files\Laserfiche\Laserfiche Workflow 8.3\Laserfiche.Workflow.Subscriber.exe

Win32 Thread Id: 8924 - ZYX StartingRules Worker Thread 2

Thread Name: XYZ StartingRules Worker Thread 2

Message: <Exception handlingInstanceId="98593246-1527-4b6c-a71a-51abb2dc26b7">

<Description>An exception of type 'Laserfiche.Connection.LFSOException' occurred and was caught.</Description>

<ExceptionType>Laserfiche.Connection.LFSOException, Laserfiche.Workflow.Common, Version=8.3.0.0, Culture=neutral, PublicKeyToken=d8428ff9263e6cda</ExceptionType>

<Message>Entry not found. [9001]</Message>

<Property name="LFROError">False</Property>

</additionalInfo>

<ExceptionType>System.Runtime.InteropServices.COMException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>

<Message>Entry not found.</Message>

<Property name="TargetSite">System.Object GetEntryByID(Int32)</Property>

<StackTrace> at LFSO83Lib.LFDatabaseClass.GetEntryByID(Int32 ID)

at Laserfiche.Connection.Lfso.LFSO83.LFDatabase83.GetEntryById(Int32 id)

at Laserfiche.Workflow.Runtime.LaserficheEntryEvent.EnsureEntryLoaded()

at Laserfiche.Workflow.ComponentModel.Conditions.Rules.EntryTemplateRule.Laserfiche.Workflow.Runtime.IConditionEvaluator.Evaluate(IServiceProvider provider, LaserficheEntryEvent entryEvent, ConditionTraceContext context)

at Laserfiche.Workflow.ComponentModel.CompositeConditionEx.Laserfiche.Workflow.Runtime.IConditionEvaluator.Evaluate(IServiceProvider provider, LaserficheEntryEvent entryEvent, ConditionTraceContext context)

at Laserfiche.Workflow.Subscriber.Runtime.Evaluators.StartingRuleEvaluator.EvaluateRule(ConditionStartingRule startingRule, LaserficheEntryEvent entryEvent, String& evaluationLog)

at Laserfiche.Workflow.Subscriber.Runtime.Evaluators.StartingRuleEvaluator.EvaluateRules(EvaluationItem item, LaserficheEntryEvent entryEvent, List`1 startingRules)

at Laserfiche.Workflow.Subscriber.Runtime.Evaluators.StartingRuleEvaluator.Run()</StackTrace>

</InnerException>

</Exception>

I have tried searching for the meaning....

0 0

Replies

replied on February 14, 2014

One common way this issue comes up is when there are multiple starting rules that get triggered by the same action. Can you confirm if that may be the case or not?

1 0

replied on May 4, 2015

I have been getting the same type of error. It happens when a user deletes a document, then a workflow tries to process it when it is gone, generally if the rule is based on a schedule instead of an event. My question is how does the process ID tie to the workflow - if I can't identify the workflow that is causing the error, how do I troubleshoot? Is the process ID related to the rule or to the actual workflow?

0 0

replied on May 4, 2015

The error above in Bonnie's post has nothing to do with schedules. It occurs in the subscriber when it tries to process wait conditions on entries that were deleted. It can be safely ignored.

1 0

replied on February 12, 2016

Alex... Miruna...

We are experiencing many of these error messages which are now seeping into our event logs. We have created "Inboxes" for our employees to dump files into for routing so many of the starting rules monitor these folders and contain logic similar in nature.

While it is relieving to know these can be safely ignored, is there any way we can modify the messages so they don't display as errors? Or at least dump to another log not monitored in event viewer? There has to be a method by which the system will know that the item was legitimately deleted by a user and thus not display as an error message.

Being the diligent IT people we are, overloaded logs due to error messages that are just "informational" is not good practice and something we don't like to see.

Thanks guys!

0 0

replied on February 12, 2016

It is not an informational message, it's an actual error: an entry was created, satisfied a starting rule or wait condition, but no longer exists in the repository. So it could be a sign of inefficient starting rules or indicate a backlog on the Subscriber.

Subscriber errors are logged to both the Workflow Event log and the subscriber_error.log. You can't turn off specific error logging, but you can turn off writing all errors to the Workflow event log by editing the Subscriber config file: C:\Program Files\Laserfiche\Laserfiche Workflow 10\Laserfiche.Workflow.Subscriber.exe.config

Look for the section that looks like this:

      <add switchValue="Error" name="Errors">
        <listeners>
          <add name="Error file log" />
          <add name="Workflow Error Event Log" />
        </listeners>
      </add>

and change it to:

      <add switchValue="Error" name="Errors">
        <listeners>
          <add name="Error file log" />
          <!-- 
            add name="Workflow Error Event Log" />
            -->
        </listeners>
      </add>

Save the file and restart the Subscriber service.

0 0

You are not allowed to follow up in this post.

Question

Question

workflow subscriber errors in event logs

Replies

Sign in to reply to this post.