Question

10.3.1 getting timeouts when they search

Laserfiche

Updated October 2, 2018

asked on October 1, 2018

I have multiple users reporting that since they upgraded to 10.3.1 they are getting timeouts when they search.

LF Server: 10.3.1.181
LF Server OS: Server 2012 R2 Standard

LF Index Server 10.3.1.359
OS: Server 2012 R2 Standard

LF Client: 10.3.1.479
OS: Windows 10 Enterprise 2016 LTSB

I have added the registry entry for the KKEY_CURRENT_USR\Software\Laserfiche\LFSO\10.3\ReceiveTimeoutSeconds with a value of 360 but it made no difference.

1 0

Replies

replied on October 1, 2018

I've encountered this as well. Sometimes, but not always, when I run a search I receive a timeout error; if I try a few times, eventually it will work correctly, but it seems to even affect searches that usually run very quickly like searching by Entry ID.

0 0

replied on October 1, 2018

Hi Jason

I found this update 2 that is suppose to enhance the search

https://support.laserfiche.com/kb/1013996/list-of-changes-for-laserfiche-10-3-1-update-2

1 0

replied on October 1, 2018

Our system has had timeout issues that even affects displaying a list of folders or docs when browsing. It can happen to one user and the same action/search doesn't have a problem for another.

It get's this bad after importing 50k-100k documents.

Reorganizing the fragmented indexes seems to take care of the problem in most cases.

I'm hoping the latest update helps too, because defragmenting indexes doesn't always work.

0 0

replied on October 1, 2018

I’ve seen very similar behavior, sometimes I’ll need 3 or 4 tries to get a search to work, but another user can search just fine, and other times I have no issues even with complex searches.

It definitely seems to relate to the repository size because I’ve only seen it in our largest repository which has over 50 million documents.

0 0

replied on October 2, 2018

our repository is small. About 900k docs. We are converting from an Oracle system to a SQL system. I created a new set of servers for the SQL server system and are exporting volumes out of the Oracle system and importing to the SQL system.

The timeout issue occurred the day we went live with the SQL system and it only had 200k docs in it at the time. A few indexes were 95%+ fragmented and rebuilding them helped. The timeout issues came back after each import of docs from the old system until we rebuilt the indexes.

One time the SQL server itself was locking up and had to be rebooted to fix the timeout issue.

0 0

replied on October 2, 2018

I to have seen this (both the slow and/or failing searches and the slow browser folder content loading) at some of our customers and we found that resetting the attributes on the effected users helped. But resetting attributes is not really a good workaround for larger systems with a large number of users. We will be watching and testing to see if the new update will indeed resolve this issue before we try to push this to the customers.

0 0

replied on October 2, 2018

My customer applied the update version 2. It seems to have corrected the time out but the searches still take a long time. I have created a ticket with Laserfiche.

0 0

You are not allowed to follow up in this post.

Question

Question

10.3.1 getting timeouts when they search

Replies

Sign in to reply to this post.