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

Question

Question

Documents not restoring to original location

asked on October 2, 2014

Good Morning All,

I have an active ticket with Laserfiche on this issue, but I wanted to see if anyone else had ever experienced this, and what their solution was.

 

I’m going to present this in breakout format as I’m attacking it from multiple angles.

 

Issue:

Deleted documents in Laserfiche are not restoring to their original location when the restore option is implemented.

 

Scenario:

Document abc123.pdf is deleted from folder \123456. It moves to the Laserfiche Recycle Bin. Restore document is chosen. Document is restored with same name, but to location ICM\TEMP - System Required - DO NOT DELETE\Import Personnel Files\01 INITIAL HIRE PACKET\testme

 

Reproducible:

Yes.

 

Troubleshooting performed:

 

Documentation of the error is available. Video, images, csv files.

 

  1. Ran DBCC integrity checks on the Laserfiche  Workflow database, and Laserfiche Repository database. No errors generated
  2. Ran the attached script (SP_SEARCHTABLE.SQL.TXT on the Laserfiche  Workflow database, and Laserfiche Repository database. Found references to the “testme” folder in both. (See attached CSV files and screen captures)
  3. Verified that the referenced workflow does not exist in the Workflow designer, nor the Workflow Admin console.
  4. Verified there are no starting rule remnants.
  5. Turned off all workflows and still reproduced the issue.
  6. Verified there is no setting that is modifying the restore location.

 

Comments:

 

My suspicion of a corrupt database is largely based on the fact that the one workflow containing any reference to a “testme” folder was last used in  March 2014 based on my date / time stamps on the workflow. (Workflow backups can be examined with text search tools such as Grubs). After searching my entire backup archive I only found the one reference.) With no starting rules or workflows in use the invalid routing should not be occurring, and the fact it is happening via a process that is “fixed”. By fixed I mean that when a restore function is executed inside the repository, the document should be restoring to the original location, not the location \TEMP - System Required - DO NOT DELETE\Import Personnel Files\01 INITIAL HIRE PACKET\testme

 

It is also based on the fact I am seeing references in both Laserfiche databases to that no longer used folder location. (See attachments).

 

This is also the second SQL environment issue that has been experienced. Microsoft had to be contacted to generate a script to stop workflows from reverting to earlier versions in the SQL system. (Documentation on that issue is also available.)

 

 

Best Regards,

Brian

Capture of SQL phantom 1.PNG
Capture of SQL phantom 2 from Repository database.PNG
0 0

Answer

SELECTED ANSWER
replied on October 2, 2014 Show version history

Hi Brian,

 

Given your test scenario, when you look at the entry in the Recycle Bin, under the "Original Location" column, can you confirm that it says \123456?

 

Could this issue with restoring just be the result of the user previously having restored a different entry to ICM\TEMP - System Required - DO NOT DELETE\Import Personnel Files\01 INITIAL HIRE PACKET\testme and then checking the option to "Don't show this dialog again?"

 

Go into the Laserfiche Administration Console and look at the attributes for the affected user. Check to see if the [HiddenDialogs]RestoreEntryDialog attribute exists and is set to Yes. Try deleting that attribute for the user and then have the user log out and log back into the repository via the Client. Then test by deleting a document, confirming the "Original Location" in the Recycle Bin and then try restoring it. You should now get prompted about where to restore the entry to.

 

Regards

1 0

Replies

replied on October 2, 2014

Hi Alex!

 

You're the man!

The issue was the [HiddenDialogs]RestoreEntryDialog attribute. Any idea why I am seeing references to that path in the various SQL databases ?

 

Regards,

Brian

1 0
replied on October 2, 2014

I don't have enough information to provide an adequate answer, but that can be something further looked into in your support case.

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

Sign in to reply to this post.