We have a Process that has been working fine until we applied the latest Forms hotfix (not sure if that's coincidence or not). It has one activity in the Modeler that starts a Workflow. Currently it is not working correctly and everything that was submitted since the hotfix was applied is sitting in a suspended state. I have tried to manually retry them, but no luck. Any ideas?
Question
Question
Instance Suspended When it Reaches Workflow Activity
asked on December 1, 2014
•
Show version history
1
0
Answer
SELECTED ANSWER
replied on December 1, 2014
Is there anything in the event viewer when you retry the task?
0
0
replied on December 1, 2014
•
Show version history
On the Forms server there is the following message:
Log Name: Application Source: Laserfiche Forms Routing Service Date: 12/1/2014 10:31:24 AM Event ID: 0 Task Category: None Level: Error Keywords: Classic User: N/A Computer: xxxx.xx.xx.xx.xx Description: 12/1/2014 5:31:24 PM Message: Connection to the Workflow Server 'localhost' could not be created. Stack trace: at Laserfiche.Forms.Routing.LFWorkflowService.Execute(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Laserfiche Forms Routing Service" /> <EventID Qualifiers="0">0</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-12-01T17:31:24.000000000Z" /> <EventRecordID>2994484</EventRecordID> <Channel>Application</Channel> <Computer>xxxx.xx.xx.xx.xx</Computer> <Security /> </System> <EventData> <Data>12/1/2014 5:31:24 PM Message: Connection to the Workflow Server 'localhost' could not be created. Stack trace: at Laserfiche.Forms.Routing.LFWorkflowService.Execute(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext) </Data> </EventData> </Event>
There are no errors on the Workflow server.
1
0
replied on December 1, 2014
So the Workflow and Forms servers are 2 different machines? The message says Forms is configured to use "localhost" as the WF Server.
0
0
replied on December 1, 2014
It looks like the Workflow service was stopped on the server for some reason. Starting and then retrying the instances solved the problem. Thank you for pointing me in the right direction.
1
0