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

Question

Question

After upgrade to 10.2.1 Error: The call to Laserfiche Workflow API was not successful.

asked on December 4, 2017

After we upgraded Laserfiche server, WF and forms to 10.2.1 the forms gives error message on start Workflow step and the workflow doesn't start. 

In the event viewer we get these errors:

1.

[5203]: The call to Laserfiche Workflow API was not successful. (Value was invalid.
Parameter name: sddlForm). [LFF5203-WFServerApiFault]

Details:
URL: 
Error: WFServerApiFault
Date: 12/3/2017 7:33:24 PM (Arab Standard Time)
HTTP Status Code: 500
Business Process ID: 1
Instance ID: 5
Business Process Name: test wf call

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: The call to Laserfiche Workflow API was not successful. (Value was invalid.
Parameter name: sddlForm). [LFF5203-WFServerApiFault]
   at Laserfiche.Forms.Routing.LFWorkflowService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus)
   at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

-----

2.

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

Details:
URL: 
Error: UnexpectedError
Date: 12/3/2017 7:33:24 PM (Arab 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.Exception
Message: Value was invalid.
Parameter name: sddlForm

-----------

workflow web services seems working and accessible, and in forms when open the instances page, it keeps loading forever as the forms DB is large about 480 GB, but was working before upgrade.

 

I even configured the forms with new database and created test form just to call test wf but we got the same issue.

Any one has any idea about this issue?

 

 

0 0

Replies

replied on December 4, 2017

Check you AppPool Indentify in IIS for Forms (Inetmgr). If you were using a local service account instead of the AppPool default account, sometimes this will get reset on installation of the upgrades

0 0
replied on December 4, 2017

Have you tried to republish the WF after the upgrade?

0 0
replied on December 4, 2017

Thank you for your fast responses, this issue resolved by creating new WF database and then import all the workflows from .wfi file.

 

It seems that the upgrade some how damaged the database.

 

Now I have another issue which is when I create Forms web service from Workflow administration console the URL test return 404 Not Found error, what ever I put as the URL of the same server (localhost, IP, Server name) I get same 404 error, although I configured the forms to use same workflow server in Forms configuration.

0 0
replied on December 4, 2017

Please start a new thread for your new issue.

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

Sign in to reply to this post.