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

Question

Posted to Laserfiche Lounge

Question

Laserfiche Lounge

Forms Error Log

Forms
Updated November 8, 2019
asked on November 7, 2019

HI Everyone, 

Not sure if anyone has come across this error log message:

"The call to Laserfiche Workflow API was not successful. (Connection to the Workflow Server 'localhost' could not be created.). [LFF5203-WFServerApiFault]"

I have also attached screen shots of the whole message. Does any one know what this means? I cannot find out what is causing it.

Capture 1.PNG
Capture 2.PNG
Capture 1.PNG (23.62 KB)
Download
Capture 2.PNG (20.22 KB)
Download
0 0

Replies

replied on November 7, 2019

I have come across this error as well, and I will be following everyone's responses! :)

I have tried a few things over the last couple of weeks, and I've been monitoring what has helped:

1) Our Database Administrator deleted any orphaned sessions/connections in the Workflow database, but this did not appear to help.
2) In the Workflow Administration Console, under Server Configuration / Server Timers, I noticed that there was a Database Maintenance Timer that was set to run hourly - I have changed this to run off of regular business hours, thinking this maintenance might interfere with calls to Workflow (just a guess at this point).
3) In order to eliminate too many calls to one Workflow database, I have started to split off some workflows onto a separate server in hopes of reducing the workload (thinking multiple Workflow evaluations via the Subscriber service might be causing lag on the server).

I'm interested to hear what everyone's experiences have been with this, and what might have worked to reduce or eliminate this error!

Marty Gaffney - Network Analyst
Town of Okotoks

0 0
replied on November 8, 2019

Just a quick update on this, after changing the times that the "Database Maintenance Timer" is set to run in the Workflow Administration Console, I did experience these same errors, however it was in the window of when the Timer was set to run.  That said, I've narrowed the times this has run even further to 1-5am to see if we can eliminate this error happening completely!

0 0
replied on November 8, 2019

We found out what happened with our side. So it looks like it depends on the company and what happened. With us it ended up being because we lost internet for 2 days due to a blowout in the IT department with the servers. 

Our IT department ended up re-running the suspended forms and most of them were able to move forward to the next step in the process. We still have some that are not moving and are working to see if we can find out why. 

I will let you know if we find out anything else that might have happened as well.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...