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

Question

Question

Error in business process when upgraded from LF Form 10.0 to 10.1

asked on July 20, 2016 Show version history

Hi,

Today i upgraded from LF Form version 10.0 to 10.1 ,the same process i used before which was working without any error,but once i upgraded to LF 10.1,the same business process gets terminated in between the process.I am calling the sub process inside the main process,once it reaches the sub process the process gets terminated and event viewer shows below error

 

An unexpected error has occurred. [LFF502-UnexpectedError] Details: URL: Error: UnexpectedError Date: 7/20/2016 5:18:10 PM (Arabian Standard Time) HTTP Status Code: 500 Business Process ID: 4019 Instance ID: 33785 Business Process Name: SB-Outgoing Correspondence 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 Laserfiche.Forms.Routing.StartEvent.InitializeDataForNewMainProcessInstance(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.StartEvent.Execute(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.RoutingDispatcher.ExecuteSteps()

 

Note:The same business process works before upgraded to 10.1

Any solution to resolve ?

0 0

Replies

replied on July 20, 2016 Show version history

What exact version of Forms 10.1 are you using? Did you get the latest from Support site? The latest Forms version should be 10.1.0.579 which include Forms 10.1 update 1 https://support.laserfiche.com/kb/1013775/list-of-changes-for-laserfiche-forms-10-1-update-1- that  include the fix for similar issue : Forms no longer incorrectly terminates the start event in a sub-process that follows a Workflow service task that is configured to wait for the workflow to finish. (143469)

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

Sign in to reply to this post.