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

Question

Question

Index never finishes

asked on January 29, 2020

So I have a repo that has been indexing for days. Search of ocr'd text via search bar never returns any results. In Index properties under status the index ques size hoovers between 1300000 and 1650000 documents in Que. I have stopped services cleared out the the IDX files and re indexed the whole repo and it is the same situation.

Any Ideas as to whats going on?

Could it be that I have so many documents that I am overlapping ques time with some sort of index window? 

indexing.PNG
indexing.PNG (15.37 KB)
0 0

Replies

replied on January 30, 2020 Show version history

It's kind of funny as we are in the same boat with the indexing - however I would love to know what spec your server is as our indexing a lot slower than yours!?

 

In terms to the text search, you won't find any results for anything that has been added to Laserfiche recently as it is most likely is sat on the back of that queue waiting to be indexed.

 

The solution is using the Quick Re-index - if I understand it correctly (I'm sure someone will correct me if I'm mistaken), it indexes existing data within the database and doesn't retrieve anything outside the database. And my guesses with your statistics above is it will be done within 24 hours. Further more info can be found here smiley

 

And look at your workflows, if you have a workflow that changes fields that are marked as index or creates new versions etc, I believe it can cause the document to get re-indexed.

 

Hope that helps!

 

 

1 0
replied on January 30, 2020

I had a repository with the same issue, never finished Indexing and the queue kept growing.  The Quick Reindex solved the problem.

 

0 0
replied on February 3, 2020

I did some checking in the Windows Envent viewer and Im getting several of these errors. Woudl this have anything to do with my issue?

"The TextProvider process was terminated due to an unhandled exception when extracting text from a "pdf" document. Search catalog: Choctaw-Nation. Entry ID: 1148865. This is usually caused by a problematic IFilter or a corrupted document. Please install a proper IFilter and see if it solves the problem. You can also skip the problematic type of electronic documents by modifying the BlockedExtensions list in registry."

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

Sign in to reply to this post.