Question

What causes Extra Images and Extra Electronic Documents in a consistency check?

Laserfiche

Updated November 29, 2023

asked on November 24, 2023

I thought the only cause for this would be a disaster event where an old database copy was restored relative to the data on the disk, but in one environment we see thousands of extra images and electronic documents in a consistency check spanning 10 years of time all the way up to current date ranges.

What would cause a file to be generated on the server disk and no reference in the repository to it on a regular basis?

0 0

Replies

replied on November 28, 2023

Chad, Have you figured out anything on this? Jim.

0 0

replied on November 29, 2023

No, I don't understand what would cause files to be generated on the disk continuously over time

0 0

replied on November 29, 2023

How stable is/was their infrastructure? Maybe a power failure during document creation? Creates the files and then the DB insert is rolled back when the operation isn't completed?

0 0

View 4 previous replies

replied on November 29, 2023

It is too consistent for such an unusual event. There are extra images and electronic files spread across the years all the way up to the current year.

0 0

replied on November 29, 2023

I can't get the consistency checker to create the report for me, but now I'm really interested in finding out the results. I'll post here with anything I figure out in future.

0 0

replied on November 29, 2023

Have you tried to manually convert the file name back into the storeid and look for it in the toc or doc tables?

0 0

replied on November 29, 2023

I am not familiar with what a storeid is

0 0

replied on November 29, 2023

The 8 character filename of the disk file is translated into the edoc storeid in the toc table or the storeid (for pages) in the doc table. The storeid converts to a hex value which is interpreted as an ascii string (padded with leading zeros) to get the eight character filename (the first 6 characters are split into three pairs for the folder path).

So, if the filename is 001C04A1.tif then the page can be found in the doc table under storeid 1836193. The tocid (entry id) of the document is in the doc table.

0 0

replied on November 29, 2023

There are extra images, they do not exist in the database, they just appeared in the repository folder out of no where.

0 0

replied on November 29, 2023

I'm just saying I'd check. Maybe the problem is with the consistency checker...

0 0

replied on November 29, 2023

Chad, when you say no reference to it in the repository, I am guessing you mean the repository SQL database, correct?

That is a really strange scenario. To me it almost sounds like the system might save the image to the volume first and then write the entry to the SQL database and because there is a problem writing to the database it leaves the image in the volume, but never writes the row in the SQL table. Have you checked for errors in the event viewer for around the date and time the entry was created on the servers drive?

0 0

You are not allowed to follow up in this post.

Question

Question

What causes Extra Images and Extra Electronic Documents in a consistency check?

Replies

Sign in to reply to this post.