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

Question

Question

Stalled Process

Forms Version 10
Updated August 28, 2018
asked on August 28, 2018

I have processes that are stalling (not suspended, so no action can be taken). It just stops mid-stream. I have two users experiencing stalls (where the task just doesn’t move forward) and there’s no indication that there’s a problem. Here’s one bit of info from the event log:

[502]: An unexpected error has occurred. [LFF502-UnexpectedError]

Details:
URL:
Error: UnexpectedError
Date: 8/27/2018 12:10:05 PM (Eastern Standard Time)
HTTP Status Code: 500
Business Process ID: 0
Business Process Name:

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

Inner exception: System.Data.Entity.Validation.DbEntityValidationException
Message: Validation failed for one or more entities. See 'EntityValidationErrors' property for more details.
   at System.Data.Entity.Internal.InternalContext.SaveChanges()
   at Laserfiche.Forms.Routing.RoutingMainProcessInstance.CancelProcessInstance(BPInstanceCancelMode cancelMode, Int32 retryCount, IRoutingContext routingContext)
   at Laserfiche.Forms.Routing.RoutingDispatcher.ExecuteSteps()
   at Laserfiche.Forms.Routing.RoutingEngineService.RunRouting(RoutingRequestParameters requestParam)
   at Laserfiche.Forms.Routing.RoutingEngineService.<>c__DisplayClass8_0.<StartRouting_Async>b__0()

These two users have used these processes before with no issues. Not sure what’s happening here suddenly. The one thing they have in common: The LF server is on the East coast and both users are on the West coast.

Any ideas anyone?

0 0

Answer

SELECTED ANSWER
replied on August 28, 2018

Found the problem. I had recently added a field variable as part of the instance name. That was fine until someone filled that field with too many characters. Apparently, this caused the process to bomb. I have removed that field variable from the instance name and the process is now working.

I tested it but had, apparently, not tested it with enough characters for it to bomb. I will create a new hidden field that will take the first 15 characters and use that for my field variable as part of the instance name.

1 0

Replies

replied on August 28, 2018

Hi Gloria, what I can pick out of the error log is "Validation failed for one or more entities." which sounds to me like a field validation error. You could disable validation on the form and have them test it to see if it worked (in the form that is stopping the process, slick on the gear to access Form Settings, then set validation level at the bottom to "No validation"), also look at the Process Diagram and click on the validate button to make sure that it is all properly connected and configured.

Let me know how it goes or if you need more assistance!

0 0
replied on August 28, 2018

I had already thought of this before emailing the group. I rechecked the two forms causing the issue ... both are already set to "no validation". I then checked the validation for the Process Diagram. I do get issues with the email address in the "From" field being invalid but that's because it's a fake email address. We use "LaserfichePROD@orano.group" for our email notifications. Never had issues before AND these email notifications are much later in the process ... not where I'm having issues.

Also, we have rebooted all systems (twice) to see if it would "release" the process and continue on. That didn't work. We are on Forms Ver. 10.2.1.246.

0 0
View 1 previous reply
replied on August 28, 2018

That is really interesting then - could it be possible that it is user specific problem then like you suggested in your original post. You can check that by building a short form and assign the User Task to the affected user.

Do you have a task called "Save Changes"?

0 0
replied on August 28, 2018

Good idea about building a short form and assigning it. I will do that.

I do not have a task called "Save Changes". I do have a task called "Save Initial DCR to Laserfiche". Why do you ask?

0 0
replied on August 28, 2018

In that case it must be an internal thing that the Forms does on the back-end. One other thing to look  at if you haven't already is to see if your Forms server is somehow being blocked by the firewall in the location of those two users. It looks like this is a server side error though so I don't think that is the case but it might be worth to look into.

0 0
SELECTED ANSWER
replied on August 28, 2018

Found the problem. I had recently added a field variable as part of the instance name. That was fine until someone filled that field with too many characters. Apparently, this caused the process to bomb. I have removed that field variable from the instance name and the process is now working.

I tested it but had, apparently, not tested it with enough characters for it to bomb. I will create a new hidden field that will take the first 15 characters and use that for my field variable as part of the instance name.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...