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

Question

Question

Form Instance terminates unexpectedly

asked on July 28, 2016 Show version history

Good day,

 

Up till now, there have been 3 instances that have terminated on their own after the waiting period has expired. The Task is assigned to the user and then terminates. All three are from the same process and failed at the same step. 

 

Other instances have continued as usual without terminating. The Event Log for the latest process shows the following: 

An unexpected error has occurred. [LFF502-UnexpectedError]

Details:
URL: 
Error: UnexpectedError
Date: 2016/07/28 02:00:00 AM (South Africa Standard Time)
HTTP Status Code: 500
Business Process ID: 36
Instance ID: 7673
Business Process Name: Business Trip and Entertainment Inquiry

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: An unexpected error has occurred. [LFF502-UnexpectedError]


Inner exception: System.NullReferenceException
Message: Object reference not set to an instance of an object.
   at FormsModel.DomainServices.UserTaskService.CompleteTask(cf_bp_worker_instnc_to_resume wr, cf_submissions submission)
   at Laserfiche.Forms.Routing.FlowObject.MarkWorkerInstanceToResumeAsCompleted(cf_bp_worker_instances wi, cf_submissions submission)
   at Laserfiche.Forms.Routing.UserTask.ExecuteForReEntry(cf_bp_worker_instances processInstance, IRoutingContext routingContext)
   at Laserfiche.Forms.Routing.UserTask.Execute(Int32 instanceId, IRoutingContext routingContext)
   at Laserfiche.Forms.Routing.RoutingDispatcher.ExecuteSteps()

 

 

Thanks for any help

0 0

Replies

replied on July 29, 2016

What version of Forms are you using? Can you open a support case by providing the exported process so that we can check at which situation the instance is terminated?

0 1
replied on August 2, 2016

Thanks Xiuhong, 

 

I'll open the ticket shortly and link this page

0 0
replied on March 15, 2017

Hi Xiuhong

Have you found a resolution / work around for this as I am getting the same error in Forms 10.2. I've tried deleting the tsk and recreating it as well as the object connected to and the error persist. In my workflow, the task has only 1 action button and 1 outpath (defaulted). Any ideas?

0 0
replied on March 15, 2017

We didn't know yet. Can you open a support case with detail information?

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

Sign in to reply to this post.