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

Question

Question

Search Error 9479 only on text searches. Service is running on the server (v10.4). Any ideas why?

asked on October 20, 2022

We have recently migrated Laserfiche from one server to a new one.  We de-licensed the old server, licensed the new server, and things seemed to be good.  Then someone tried searching for something.  We use a very basic setup, no real customization or anything, but searching is being problematic.  When someone searches for a document by date or other value, it works fine.

But if someone searches for a text value, the following error occurs:

"Error connecting to the search engine.  Either the search engine is offline or the search engine connection settings are misconfigured.  Please contact your Laserfiche administrator. [9479]"

Again, this ONLY happens when doing a search for text.  I checked on the server, and the index and search engine service is running.  I tried restarting it to no avail.  When clicking the details button on the error box, the following comes up:


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

LF.exe (10.1.1.320):
Call Stack: (Current)
CSearchView::RunSearch
CSearchView::BeginSearch
Call History:
GetOptionString ([Search]ContextHitLength)
CAttachedRepository::GetProfileValue
GetOptionString ([Search]IncludeShortcuts)
CAttachedRepository::GetProfileValue
GetOptionString ([Settings]UseDefaultCollation)
CAttachedRepository::GetProfileValue
CSearchView::GetTemplateIdFromSearchString
IdleTimerProc

If anyone has any ideas on what this could be, I'd greatly appreciate hearing them.

 

 

0 0

Replies

replied on October 21, 2022

There should be more detailed error messages in the Laserfiche Server event log.

1 0
replied on October 21, 2022

I think I found the issue.  The index in the administration panel was set to use the old server's hostname.  I changed it to the new server, and am reindexing now.  Looks hopeful.

 

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

Sign in to reply to this post.