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

Question

Question

database statement execution error encountered

Workflow Laserfiche Version 9
Updated September 7, 2015
asked on September 2, 2015

Hi Guys,

 

Sorry need help on this one and if you can tell me if this is a SQL issue or a Laserfiche bug.(think I may have read somewhere its a bug but not sure if that was just LFSO related)

Our client has recently moved there Laserfiche db onto their SQL farm and onto the latest version of SQL.

Since doing this they perform a weekly restart of the SQL server (weds @2am) and I find that on this day users are complaining that running workflows have been terminated.

On investigating why they have been terminated I see "error executing SQL command" and in the event viewer I see the attached application event errors.

 

If anyone is who willing to help has any questions regarding this then please let me know.

 

All help appreciated :)

Thanks

Tina

SQLISSUE.pdf (182.85 KB)
Download
0 0

Replies

replied on September 2, 2015

Those are normal errors if the Laserfiche Server tries to access SQL while the SQL server is starting up. The Laserfiche Server will attempt to reconnect.

There's nothing in your PDF about Workflow.

0 0
replied on September 4, 2015

Thanks for the response Miruna.

Below is the error message I see in workflow designer. This links with the reboot at 2:01am.

My understanding was that if the connection is lost then workflow would just wait until it is recovered and then keep going instead of terminating. Is this incorrect?

0 0
View 1 previous reply
replied on September 4, 2015

That's for Workflow's connection to its own SQL database. This is an error returned by the Laserfiche server. What type of activities are "decision made or 48hrs passed" and "ValidationBP"?

0 0
replied on September 4, 2015

repeat 5 is a repeat job which checks to see if a decision value has been chosen or if the date & time exceeds the 48hours passed. So once it jumps out here as it cannot talk to SQL it goes onto a  conditional decision "decision made or 48 hours passed" which it doesnt meet any of the conditions because its not valid / invalid / 48hours passed. The validation bp is the name of the workflow, not an activity so it is even strange that it brings this up, no?

0 0
replied on September 4, 2015

Not really. The errors propagate out to the workflow when they terminate it, so it's normal to see the error on the workflow itself.

So it looks like you're getting the errors when Workflow tries to look up the field. If you don't mind me asking, why not use an escalation activity to wait for the field change or the deadline?

0 0
replied on September 7, 2015

Hi Miruna,

 

To be honest I hadn't thought about the escalation activity but that is a good call.

If the error persists then I will look at changing up the workflow.

 

Thanks

Tina

0 0
replied on September 4, 2015

repeat 5 is a repeat job which checks to see if a decision value has been chosen or if the date & time exceeds the 48hours passed. So once it jumps out here as it cannot talk to SQL it goes onto a  conditional decision "decision made or 48 hours passed" which it doesnt meet any of the conditions because its not valid / invalid / 48hours passed. The validation bp is the name of the workflow, not an activity so it is even strange that it brings this up, no?

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...