You are viewing limited content. For full access, please sign in.

Question

Question

How to find out what Workflow an Activity Error is from?

asked on April 13, 2022

I am looking at the Activity Errors log in the Workflow Administration Console and when I look at an error that is listed, it does not specify which workflow the activity belongs to that is throwing the error. What is the best way to figure that out so I can troubleshoot the problem?

1 0

Replies

replied on April 13, 2022

If you look at the stack trace, it should have something like this:

 <Property name="ActivityName">MoveEntry</Property>
 <Property name="ActivityType">Laserfiche.Workflow.Activities.MoveEntry.MoveEntryTaskActivity</Property>

If it does, the log viewer should pull it into the Activity Name column. If it doesn't, it might've happened somewhere in a subsystem where we didn't have the activity name.

Paste the stack trace in here and we'll help you read it.
 

(Oh, and welcome back! smiley)

0 0
replied on April 13, 2022 Show version history

Thanks Miruna! I won't be as involved with Laserfiche as I have been, but it will still be nice to be part of the community.

Below is the stack trace from the error:

----------------------------------------
Timestamp: 2022-04-13 19:49:58.486
Local Time: 4/13/2022 12:49:58 PM
Category: Activity
Machine: XXXXXXXXX
Severity: Error
Application Domain: Laserfiche.Workflow.Service.exe
Process Id: 4000
Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 10\Laserfiche.Workflow.Service.exe
Win32 Thread Id: 11564 - Task Work Thread [CustomTasks]
Thread Name: Task Work Thread [CustomTasks]
Message: <Exception handlingInstanceId="57eb441b-ddfc-4bf4-87f5-dd2ec03662cf">
  <Description>An exception of type 'System.ArgumentException' occurred and was caught.</Description>
  <DateTime>2022-04-13 12:49:58Z</DateTime>
  <ExceptionType>System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
  <Message>Tag name cannot be null or empty.
Parameter name: tagName</Message>
  <Source>Laserfiche.RepositoryAccess</Source>
  <HelpLink />
  <Property name="ParamName">tagName</Property>
  <Property name="ActivityName">SDKScriptAssignTags</Property>
  <Property name="TargetSite">&lt;undefined value&gt;</Property>
  <Property name="HResult">-2147024809</Property>
  <StackTrace>   at Laserfiche.RepositoryAccess.Tag.GetInfo(String tagName, Session session)
   at WorkflowActivity.Scripting.SDKScriptAssignTags.Script1.Execute()
   at WorkflowActivity.Scripting.ScriptBase.ExecuteScript(ScriptExecutionContext context)</StackTrace>
  <additionalInfo>
    <info name="MachineName" value="XXXXXXXX" />
    <info name="TimeStamp" value="4/13/2022 7:49:58 PM" />
    <info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    <info name="AppDomainName" value="Laserfiche.Workflow.Service.exe" />
    <info name="ThreadIdentity" value="" />
    <info name="WindowsIdentity" value="XXXX\XXXXXXXX" />
  </additionalInfo>
</Exception>
----------------------------------------

 

0 0
replied on April 13, 2022

Ah, SDK scripts. That message seems to be missing the instanceID property. I'll double-check if that's a bug or if that info is not accessible to the task subsystem.

If you go to the Designer and search for workflows terminated with "time of last action" around 4/13/2022 12:49:58 PM, you should be able to narrow it down to only a few instances to check for an SDK Script activity called "SDKScriptAssignTags "

2 0
replied on April 13, 2022

We were able to find the workflow that contained the activity in question. Please let me know if not showing the instanceID is a bug or not. It would be great if there was a simpler way to track it down.

0 0
replied on April 15, 2022

Dude, you can't just roll in here and ask questions all nonchalant without updating your goodbye post. Glad you'll still be around! And that you got to keep all those sweet Laser Points you earned with your previous account.

0 0
replied on April 15, 2022

You hit 10,000 points, we bend some rules when you make requests wink (seriously though, we will merge accounts when people change jobs, if requested).

0 0
replied on April 15, 2022

@████████,
That was great man! I'll be sure to update my post for ya, just in case you forget later, lol.

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.