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

Question

Question

Laserfiche Client version 11 - General Database [Error 9008] while Searching

asked on December 4, 2021 Show version history

We are facing a General Database Error [9008], on different computers while searching. 
We are using the Laserfiche version 11, and Database is SQL Server (SQL 2019 CU 14 Standard).
The search criteria is Field Search and Field is EmpID. The Template Fields are already set to indexed. 


Additionally, Whenever we reset the Client settings, it works and search the data for the first 5-6 queries later on for every query it start giving the Error [9008]. The Detail error is as follow:

Error Code: 9008
Error Message: Error executing SQL command.
General database error. [9008]

------------ Technical Details: ------------

LF.exe (11.0.2103.223):
    Call History:
        CSearchView::OnSearchDone
        IdleTimerProc
        CFolderListCtrl::Refresh
         CFolderListCtrl::LoadContentsHelper
          CTocCacheWorkerThread::SetDatabase
        CSelectionProperties::GetFlags
        IdleTimerProc
        IsRepositoryLoggedIn

 

 

##Laserfiche Client
Error Code: 9008
Error Message: Error executing SQL command.
General database error. [9008]

------------ Technical Details: ------------

LF.exe (11.0.2103.223):
    Call Stack: (Current)
        CSearchView::RunSearch
        CSearchView::BeginSearch
    Call History:
          CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           GetRepositoryProperties
            GetOptionString ([Settings]CloudCustomer-kcc)
          CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
          CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
          CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           GetRepositoryProperties
            GetOptionString ([Settings]CloudCustomer-kcc)

0 0

Replies

replied on December 6, 2021

Please open a support case.

1 0
replied on December 6, 2021

Please post back if you get a resolution to the issue. 

We are seeing this as well.  Work around for us is to limit the search.  Example being to limit the depth of folders and not searching text.  If the search criteria is as narrow as possible, it won't error out.

1 0
replied on December 6, 2021

Hi Shawn,

I'm finding this issue sometimes also.

I hope Laserfiche can find a solution.

 

0 0
replied on December 20, 2021

I resolved this issue for one of our users by wiping out the account attributes. Once done, the search error went away.

1 0
replied on December 20, 2021 Show version history

If that is using tools-options-reset in the client then it will likely just come back.  I reset my client last Thursday and searches began working again and were fast.  However, it is Monday today and the error is back. 

Another odd thing is I will get the error logging in to 2 different machines.   My laptop is one and the other is a virtual machine.  I use the same login credentials in both cases.  Once I reset the client on my laptop searches begin working for both the laptop and the VM. 

This only started happening to me once I moved to Laserfiche 11 client.  The server has also been upgraded as well. 

0 0
replied on December 20, 2021 Show version history

I took it as LF Admin Console, user properties, attributes. It is also per Repository.

I tested this by removing all attributes from one of my users and the searches worked. Now it is going through them all to try and figure out which of them are the cause.

Edit:  You can view just the attributes related to Search from a drop down list.  I also had a weird problem with OCR on dragging and dropping files into LF that was fixed by removing the attributes for OCR.  Didn't even think about it until the Search removal worked and I saw OCR listed.  Both errors came up after updating to version 11.

0 0
replied on December 22, 2021

I'm that user ;)

You are correct - in the admin console. 

So far it is still working well.

But, when I restore my exported attributes, it still has the problem. So I removed the Search attributes and that ... didn't fix it!

By chance, I then removed the XmlColumnDisplay attributes next and it DID fix it!

For me, as a user sample as one, I narrowed it down to the attribute in

XmlColumnDisplay: 

Name: Data

Data: MULTI-ATTR:2

I've now restored that attribute twice and it causes the search to fail, while removing it fixes search!

Steve

XmlColumDisplayAttribute.jpg
1 0
replied on December 9, 2021

Here as well. If there is a solution, please post it!

My server is LF 11 and I've tried both the 11 and 10.4 clients. At the bottom of the error in the event log on the server (after all the query text) I see the timeout is set to 15 seconds?

...order by q1.row_num"; Timeout=15(sec).

I know I'm doing a query that might take a little time. I'm asking the search engine to traverse 636 folders and inspect 14,482 documents with 179,620 pages and return to me any that are over a certain size (or even worse, greater than nn and less than nnn!). 

But I'd rather not break it up into smaller chunks of search. I'm ok with it taking a minute or two.

Steve

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

Sign in to reply to this post.