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

Question

Question

Random workflow error when creating record folder since upgrade to 12

asked 7 hours ago

We are having an intermittent error with a workflow that has been in place for many years but only since our upgrade to Laserfiche 12. In each case, the point of failure is when the workflow attempts to create a Record folder for a new employee. We will get a general database error [9008] at the point where the document should be moved to the record folder that is created within the activity.

Of the 2,236 instances of this workflow running since our upgrade to version 12, we have experienced this only 21 times. At first it seemed to be isolated to only one branch of the workflow and as a work around we added a step to create the folder before the move entry instead of as a part of it, but now we are seeing it in other branches, but always at the point where it should be creating the Record folder. When I create the folder manually, the documents process as they should through the rest of the workflow.

Neither our internal database manager, our solution partner, nor Laserfiche has been able to figure this out yet. Is there anyone here with ideas...? This is the detailed error in the Event Viewer. 

An error occurred when executing an SQL query, retrieving the results of a query, or otherwise communicating with the database server. Session ID=326299; Dialog ID=16660788; Repository="HR"; Function=SysEntryMove; Message="[Microsoft][ODBC Driver 18 for SQL Server][SQL Server]The UPDATE statement conflicted with the FOREIGN KEY SAME TABLE constraint "toc_parentid_fk". The conflict occurred in database "Lf_HR_Repository", table "dbo.toc", column 'tocid'."; Statement="{call move_doc(:tocid<int,in>,:oldpar<int,in>,:newpar<int,in>,:newname<char[255],in>,:now<timestamp,in>,:modifier<raw[85],in>,:reviewcycle<int,out>,:reviewinterval<int,out>,:reviewintervalunit<char[1],out>,:lastreview<timestamp,out>)}"; SQL Variable=""; SQL State="23000".

 

HR Autofile snipit.png
0 0

Replies

replied 2 hours ago

To begin with, "toc_parentid_fk" is the constraint that makes sure that the folder you are trying to move an entry to actually exists in the folder tree. I take it that the folder id used in the move operation is the output of the create folder activity? If you have access to the actual integer value used, I would compare it to the current toc table. I wouldn't expect a row with that id to exist, but ids are assigned consecutively - do rows with ids near that one have creation dates near the run time of this activity? If the id appears reasonable but is not in the table, that suggests that the folder was deleted between the time it was created and the move was attempted. Does the audit log have any events for the missing folder id? The low incidence of this problem does suggest that it takes an unlucky event to trigger it - is there a cleanup workflow that could be deleting an empty folder at just the wrong time?

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

Sign in to reply to this post.