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

Question

Question

File Not Found Exception\Invalid Operation Exception

asked on September 21, 2022

I have two different error messages, the first concerns the Assembly Reference that cannot be loaded, and the second concerns one of the WFs with a Script activity that are stuck in a waiting state. There are hundreds of these in log. Restarting the WF services does seem to resolve this error, however, this happens fairly frequently and is disruptive to our entire county. I've pasted the two errors below:

Timestamp: 2022-09-19 17:20:10.991

Local Time: 9/19/2022 10:20:10 AM

Category: Activity

Machine: WF-server

Severity: Error

Application Domain: Laserfiche.Workflow.Service.exe

Process Id: 6604

Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 10\Laserfiche.Workflow.Service.exe

Win32 Thread Id: 6032 - Task Work Thread [CustomTasks]

Thread Name: Task Work Thread [CustomTasks]

Message: <Exception handlingInstanceId="91276cae-7bcb-48a9-ae2f-b636785cff63">

  <Description>An exception of type 'System.IO.FileNotFoundException' occurred and was caught.</Description>

  <DateTime>2022-09-19 10:20:10Z</DateTime>

  <ExceptionType>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>

  <Message>Could not load file or assembly 'CustomCodeLib, Version=2.0.3.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.</Message>

  <Source>WF Process Name</Source>

  <HelpLink />

  <Property name="FileName"> CustomCodeLib, Version=2.0.3.0, Culture=neutral, PublicKeyToken=null</Property>

  <Property name="FusionLog">WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

</Property>

  <Property name="ActivityName">Recombine File</Property>

  <Property name="TargetSite">&lt;undefined value&gt;</Property>

  <Property name="HResult">-2147024894</Property>

  <StackTrace>   at WorkflowActivity.Scripting.RecombineFile.FileBuilder.Execute()

   at WorkflowActivity.Scripting.ScriptBase.ExecuteScript(ScriptExecutionContext context)</StackTrace>

  <additionalInfo>

    <info name="MachineName" value="WF-server" />

    <info name="TimeStamp" value="9/19/2022 5:20:10 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="Domain\service.account" />

  </additionalInfo>

</Exception>

 

 

Timestamp: 2022-09-19 17:20:10.994

Local Time: 9/19/2022 10:20:10 AM

Category: Activity

Machine: WF-server

Severity: Error

Application Domain: Laserfiche.Workflow.Service.exe

Process Id: 6604

Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 10\Laserfiche.Workflow.Service.exe

Win32 Thread Id: 6032 - Task Work Thread [CustomTasks]

Thread Name: Task Work Thread [CustomTasks]

Message: <Exception handlingInstanceId="3d98f920-8f97-4de5-8309-246050cc1f63">

  <Description>An exception of type 'System.InvalidOperationException' occurred and was caught.</Description>

  <DateTime>2022-09-19 10:20:10Z</DateTime>

  <ExceptionType>System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>

  <Message>Workflow with id "d5a602b6-58b8-491d-a205-5a0f88d110c8" not found in state persistence store.</Message>

  <Source>System.Workflow.Runtime</Source>

  <HelpLink />

  <Property name="InstanceId">d5a602b6-58b8-491d-a205-5a0f88d110c8</Property>

  <Property name="ActivityName">RecombineFile</Property>

  <Property name="TargetSite">System.Workflow.ComponentModel.Activity InitializeExecutor(System.Guid, System.Workflow.Runtime.CreationContext, System.Workflow.Runtime.WorkflowExecutor, System.Workflow.Runtime.WorkflowInstance)</Property>

  <Property name="HResult">-2146233079</Property>

  <StackTrace>   at System.Workflow.Runtime.WorkflowRuntime.InitializeExecutor(Guid instanceId, CreationContext context, WorkflowExecutor executor, WorkflowInstance workflowInstance)

   at System.Workflow.Runtime.WorkflowRuntime.Load(Guid key, CreationContext context, WorkflowInstance workflowInstance)

   at System.Workflow.Runtime.WorkflowRuntime.GetWorkflow(Guid instanceId)

   at Laserfiche.Workflow.Runtime.WorkflowManager.GetWorkflowInstance(Int32 workflowId, Guid workflowInstanceId, Boolean refreshInstanceCache)

   at Laserfiche.Workflow.Runtime.WorkflowManager.Laserfiche.Workflow.Runtime.IWorkflowRuntimeHost.GetWorkflowInstance(Int32 workflowId, Guid instanceId)

   at Laserfiche.Workflow.ServerApplication.GetWorkflowInstance(Int32 workflowId, Guid instanceId)

   at Laserfiche.Workflow.Runtime.Systems.Tasks.TaskDatabaseRuntime.NotifyWorkflowInstance(Task task, IResult result, WorkItemFinishedEventArgs args)</StackTrace>

  <additionalInfo>

    <info name="MachineName" value="WF-Server" />

    <info name="TimeStamp" value="9/19/2022 5:20:10 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="Domain\service.account" />

  </additionalInfo>

</Exception>

0 0

Replies

replied on September 22, 2022

The first is an issue loading the "CustomCodeLib" library in a script. This could happen for various reason, like the library actually not being on the machine or the dll being updated to a newer version or unaccounted for references going missing.

The error message seems to have the Workflow name ( <Source>WF Process Name</Source> ) and the activity name ( <Property name="ActivityName">Recombine File</Property> ) so you can check the referenced assemblies to see if they're present. If they are, then it might be lower level references that get loaded on-demand, so the next step would be to turn on assembly bind failure logging as indicated in the error and reproduce the issue. The log generated will indicate which assembly it was looking for and where it looked to find it. Don't forget to turn off logging immediately after you reproduce the issue (as they can use quite a bit of disk space if left on).

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

Sign in to reply to this post.