Question

search catalog read only mode

Updated February 19, 2019

asked on January 9, 2014

Hello,

Our repository is currently not indexing any documents. In the laserfiche admin console, under indexing properties, there is a message that says "The search catalog is in read-only mode. Full-text search is available, but indexing and stop word updating are disabled."

How can I take the catalog off read only? Will I need to put in a support ticket? Most of the questions I've seen so far about this have resulted in a support ticket.

2 0

Answer

APPROVED ANSWER

replied on January 9, 2014

The causes of this issue can vary.

First check and make sure that the Laserfiche Server service account has read and write access to the location of the search catalog. One customer had moved their search catalog to a network location and the Laserfiche Server service account didn't have access to it.

Second, make sure that no other processes are accessing the index files in the search catalog. Another time, a customer had a backup job running that had locked the .idx files preventing LFFTS from accessing the search catalog properly.

As a last resort, and if possible depending on your organization, you can try deleting and recreating the search catalog and then reindex the repository.

6 0

replied on December 18, 2017

Thank you for this information above Alex,

I was seeing a lot of errors out of no where in a client environment and it was telling me that the Search Catalog was in read only mode? I had never seen this issue before!

Seems as though someone decided to change the service account for the Search and Indexing Services from the Admin we had to "local system" account. As soon as I changed the account back and restarted the services, the index was back to normal again.

Thanks

Ziad Khamo

0 0

replied on February 19, 2019

I actually encountered this issue as well. Appears that the account running the index service did not have sufficient rights to the folder that the index service was trying to write to. I updated the share/security rights to the new drive hosting the LFData folder for the Local Sys account running the service. Restarted the service and then retried indexing repository and it worked successfully. Searching by text is now back to normal. Thank you for this tip!

0 0

Replies

replied on January 9, 2014

Have you checked the Laserfiche Services on the server? That would be a good place to start.

If they are running, or stopped but you are still getting problems with laserfiche (or restarting the services) then look at the event viewer on that machine as well.

1 0

replied on January 29, 2014 • Show version history

After putting in a support ticket, it turns out the service account for the full text search system needed to be changed to a different account. Thanks for the responses.

0 0

replied on January 29, 2014

We just had this same exact problem. Local System was not working but an actual administrator account does.

1 0

replied on February 11, 2014

I have this issue. I've swapped locl service account for an Admin account but still see the same issue. What else should I check?

0 0

replied on February 11, 2014

Have you confirmed that no other processes have locked the search catalog files? Have you tried creating a new search catalog?

0 0

replied on April 19, 2014

We have facing the same problem and we cannot take any action to delete or detach the search catalog. Please check the attached picture.

index-error.jpg (67.97 KB)

| Download

0 0

replied on April 22, 2014

Hello Adnan, are you encountering the read-only catalog issue? Do you still have the problem after restarting LFFTSrv service? If the restart action doesn't resolve the read-only issue, you may check the application logs in event viewer for more information. Or you can submit a support ticket.

0 0

replied on January 14, 2015 • Show version history

I tried restarting the service but no change so I changed the Local Account for the LFFT service to an Admin account and it worked great. Thanks for the info!

0 0

replied on July 11, 2018

Been having this exact problem for a very long time and this morning my automated Workflows bummed out because the Workflow was unable to properly text search, if at all, in the Repository.

Today I decided to fix this because it is going to have a massive impact on my future processes.

Every time I open the Admin Console I see:

I click detach, and click attach again:

It starts indexing and my problem is solved. But when you look at the Even Viewer, the situation is not so satisfied:

The errors were running up until I clicked detach and then attach. Then I got a few informational warnings which basically tells me that something happened to the catalog:

Then all seems well, and the follow pops up:

This one almost bothers me most because it is telling me that even though the indexing has started, there is still an existing problem. I have read through a few KB articles on the support.LF site and I found a thread that would seem to solve my problem:

https://support.laserfiche.com/kb/1011970/regenerating-a-repositorys-search-idx-files

Though, this seems to be a massive system change and I do not feel comfortable enough to do this myself.

I also saw that my local folders, which encapsulates the Repository are Read Only:

Any help? Can anyone point me in a general direction to troubleshoot this properly? I saw the above replies and I am not sure how to check Alexander Huang's solutions.

Thank you.

0 0

You are not allowed to follow up in this post.

Question

Question

search catalog read only mode

Answer

Replies

Sign in to reply to this post.