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

Question

Question

Workflows will not work after Server Re-boot

asked on September 24, 2014

I have to Restart the Laserfiche Workflow 9.1 Service (Service Name - LFWFServer)  after a Laserfiche Server reboot.  If I do not do this, none of the Workflows will work.

 

I tried changing the Log On to the Administrator Userid and Password, but still the same thing.  I have the Startup Type set to "Automatic".

0 0

Answers

APPROVED ANSWER
replied on September 24, 2014

You may try changing the service to have a delayed start. It may be having an issue at startup that is not allowing it to start completely.

1 0
SELECTED ANSWER
replied on September 29, 2014

Hi Ray, 

If your question has been answered, please let us know by clicking the "This answered my question" button on the appropriate response.

If you still need assistance with this matter, just update this thread. Thanks!

0 0
replied on November 14, 2014

The Delayed Start Option seemed to fix it. Life is Good.

replied on November 14, 2014

The Automatic(Delayed Start) fixed it.   Life Is Good.

0 0

Replies

replied on September 24, 2014

You should be able to configure a task to trigger whenever the LF Server service is started to restart the Workflow service, then you would get around this issue. 

0 0
replied on September 24, 2014

It's not clear if you are referring to starting workflows or instances that are already running.

The Workflow Subscriber attempts to reconnect when the Laserfiche Server is restarted. If you restarted the Laserfiche server and workflows are not starting, you want to look in the Subscriber Trace in the WF Administration Console and see if the Subscriber has reconnected already or if any errors are listed.

The Workflow Server also reconnects to the repository if the Laserfiche Server is restarted. However, there is a 15 minute delay on retrying to connect when Workflow runs into "Could not connect to the Laserfiche Server." errors in the middle of a executing a workflow. The duration can be configured from the corresponding task error handler in the Workflow Administration Console.

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

Sign in to reply to this post.