Search Catalog Error 9491

asked on January 25, 2018 • Show version history

Hi All,

I am wondering if anyone has seen this issue before? There seems to be an issue where the Search Catalog "Index" in Administration Console is going to an "Unknown" State. Upon restarting the services, it seems to index the files fine, then 6 or so hours later, the same error is occurring?

I captured this from the Index Page:

Error Code: 9491
Error Message: The search catalog is in read-only mode. Full-text search is available, but indexing and stop word updating are disabled. [9491]

------------ Technical Details ------------

LFSO:
Call Stack: (Exception)
LFSession::ProcessResponse
LFSession::SendRequest (GET /+LF/indexstatus)
CLFIndexStatus::GetPropertiesFromServer
ILFObjectImpl::Read
CLFIndexStatus::get_IsOptimizingIndexFiles
Additional Details:
HRESULT: 0xc0042513 (LFSession::ProcessResponse, LFSession.cpp:3902)
(LFSO/10.3.0.84)
LFAdmin.dll (10.3.0.457):
Call Stack: (Current)
CIndexStatusPropPage::RefreshIndexStatus
Call History:
CIndex1PropPage::SetupCatalog
CIndex2PropPage::DisplayNoiseList
CIndexStatusPropPage::RefreshIndexStatus
CIndexStatusPropPage::RefreshIndexStatus

The user running the service is a System Administrator.

The error i see in Event Viewer before i restart the services is saying: "Failed to modify the read-only search catalog "RepoName."

Once the process restarts, I also starting seeing these warnings in Event Viewer and they vary on extensions (xls/xlsx/xlsm etc), and I am not sure if they relate to the issue. I am trying not to re-index the whole repository as there are over 400,000 documents in there to date.

Warning Message:

The TextProvider process was terminated due to an unhandled exception when extracting text from a "xlsx" document. Search catalog: RepositoryName. Entry ID: xxxxxx. 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.

Any feedback would be kindly appreciated

Regards

Ziad

0 0

replied on January 25, 2018

Also,

If I was to re-index / Create a whole new search Catalog, I need to know if the issues seen would be resolved?

Thanks

Ziad

0 0

View 9 previous replies

replied on January 29, 2018

"The TextProvider process was terminated due .." should not be related to the issue. Please check event logs by following steps:
1. On LFFTS machine, open event viewer and go to Application and Services Logs/Laserfiche/SearchEngine/Service/Admin
2. Filter log to include error level events and exclude event id 33566. (See Filter.logs.png attached). You may exclude more messages if needed.
3. Check the error messages, there should be messages indicating the failure reason.

If there is no useful message after filtering the event log, please increase the maximum log size and choose "Archive the log when full, do not overwrite events" in Log properties (https://msdn.microsoft.com/en-us/library/aa754305(v=bts.10).aspx) and restart Laserfiche Full-Text Indexing and Search Engine. Check event log if the issue still exists. If there is still no useful messages, please file a support ticket with LFFTS event logs and the excluded event ids.

One possible guess might be insufficient disk space. If it is the case, re-index / Create a whole new search Catalog may not help.

Filter.logs.png (111.45 KB)

| Download

0 0

replied on January 29, 2018

Hi Cangfei,

I have just done this filter and found the following: (screenshot attached)

Last week Friday, I done the following:

1. Stop the Services

2. Change the search folder from SEARCH to SEARCH.OLD

3. Restart the Services

This created a new search Folder for me, but of course all the documents now that were Search Textable are no longer there as the old Search Folder contained all the data,

I can also confirm:

* The HDD still has over 60GB of Space remaining.

* The user running the service is full Administrator user

So, I am not sure why it would advise it is failing to modify the read-only search catalog.

thank you

Ziad

0 0

replied on January 30, 2018

The info is not enough for troubleshooting. There should be messages indicating the failure reason. It is not easy to find them because there are many duplicated messages (Event ID 32951). Please follow the steps in previous post to filter the event log to exclude the message 32951. If there are other duplicated messages, please exclude them in the same way until you find useful messages.
If there is still no useful message, please do the 2nd part in previous reply.

0 0

replied on January 30, 2018

Hi Cangfei,

Here is what i found after the filter was put in place:

The information highlighted is giving me the following:

Operation: TRACE, result: WordTree.cpp:368. Please ignore this message if there are no other error messages. No user action is required.

The error above it:

Fatal error encountered: 0x170c000809f.

The error above that:

std error: abort, Search catalog "RepositoryName" will restart.

Which then advises me that the SearchCatalog is restarting, then stopped and a warning of:

.IDX files for the search catalog "RepositoryName" have been rolled back.

Thoughts?

Thank you

Ziad

0 0

replied on January 30, 2018

I would try putting in exceptions for your backup software and/or antivirus for the full text search index location, something you have running on the machine is likely locking those files. You also show you are running 10.3, which is fairly new. If everything was running fine in 10.2, it might also be a bug.

The lack of ifilter for those type of electronic documents shouldn't cause this.

0 0

replied on January 30, 2018 • Show version history

This is a known issue in 10.3.0. As a workaround please try the following:

1. Delete the catalog in Admin console (make sure index files are deleted after deleting catalog).
2. Stop the LFFTS service.
3. Disable Optimization by creating a "OptionalOptimizationType" key under HKEY_LOCAL_MACHINE\SOFTWARE\LASERFICHE\LFFTS\Config and set the value to 0.
4. Restart the LFFTS service.
5. Re-create the catalog and reindex the entire repository.

An official fix will be included in the next release.

1 0

replied on January 31, 2018

Hi Cangfei,

Do you mean the whole SEARCH folder to be deleted in point (1)?

Thank you

Ziad

0 0

replied on January 31, 2018

Yes.

0 0

replied on February 24, 2018

Hi Cangfei,

I was wondering if this issue will be resolved in the next release of 10.3? Looks like by just changing the name of the search and restarting the services which i initially did has now stopped working and I get the unknown state again on the search catalog.

Thank you

Ziad

0 0

replied on February 26, 2018

The issue I mentioned before will be resolved in the next release of 10.3. However, if you apply the workaround correctly, the issue should not happen again. Did you disable optimization using the registry value, and then re-start the service, and recreate the catalog? And is there a message about 'Operation: TRACE, result: WordTree.cpp:368.' this time? If that is not the case, then it could be a different issue, and please contact your VAR to open a support ticket.

1 0

replied on March 29, 2018

Hi Cangfei,

For a final confirmation, is this what you mean when you say create a new key?

Thank you

Ziad

0 0

SELECTED ANSWER

replied on April 12, 2018

Hi Ziad. Yes, it is correct.

2 0

Question

Question

Answer

Replies

Sign in to reply to this post.