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

Question

Question

LFFTS Crashing and setting repository in read only mode.

asked on January 5, 2017

In the last couple of weeks, the LFFTS has been crashing and has placed our Repository Index in Read Only mode which causes our Workflows to crash.  We are using Laserfiche 9.1 on Windows Server 2012 R2.  Here is an excerpt of the Event logs.  We are unsure of the timelines for new releases so we are holding off upgrading right now.  Any help would be appreciated

--------------------------------------------------------------------------------------

Optimization ID: #6. Optimization of search catalog "IRIS" has started. Indexing will pause temporarily, and will resume automatically after optimization is finished. No user operation is needed.

Fatal error encountered: 0x1c5c000809f.

Thread 6728 is saving dump file: C:\Users\SA_LAS~1\AppData\Local\Temp\Laserfiche\DumpFile\LFFTS-20170104231458.MDMP.

The application status had been dumped into file, C:\Users\SA_LAS~1\AppData\Local\Temp\Laserfiche\DumpFile\LFFTS-20170104231505.xml.

Handling std exception, abort. Last error is '0: The operation completed successfully.  '.

Optimization ID: #6. Optimization and file replacement canceled for search catalog "IRIS". Please ignore this message if the Laserfiche Full-Text Indexing and Search Service or the search catalog is closing. No user action is required.

...

Search catalog: IRIS, idx err: 7801.

Error info: Entry ID is 0xffffffff000000000000000000000000, operation type is 3, the search catalog is IRIS.

LFException: (Line: 0) Search catalog: null, idx err: null., Search catalog IRIS will restart.

Search catalog IRIS will be switched to read-only mode. Nothing will be indexed.

-------------------------------------------------------------------------------------- 

 

0 0

Answer

SELECTED ANSWER
replied on January 5, 2017

Please contact your reseller to open a case with Tech Support and attach the .MDMP and .XML files mentioned in the error message.

0 0

Replies

replied on March 15, 2017

What was the resolution they have provided?

 

Regards

Kirubaa

0 0
replied on March 16, 2017

The end user deleted the search index and re-indexed the repository.  According to their VAR, they are in the process of upgrading to 10.2.

1 0
replied on March 16, 2017

Thanks Raymond!

I think this can be done only if the index is corrupted.

 

0 0
replied on March 16, 2017

It does not have to be corrupted. In general, it should not be necessary to delete your search catalog, but you may wish to do so if you want to change your stop words and completely reindex, or for troubleshooting purposes.

Further, a repository can be reindexed at any time, regardless of the number of documents waiting to be indexed. Reindexing a repository is useful when the search index configuration has been modified or if the repository contains many documents that have never been indexed.

0 0
replied on June 2, 2022

How do you convert the entry id value in the error message so you can find it in the repository?

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

Sign in to reply to this post.