Hello,
I have a customer who hasn't been able to text search for a couple weeks. They had a power outage, and when everything came back online, LFFTS didn't work.
LFS and LFFTS are installed on the same machine. They deleted the search catalog folder while troubleshooting this, which didn't seem to change anything. We've uninstalled and reinstalled LFFTS to no effect. When we try to open the Index node in the Admin Console, the window hangs and goes to 'not responding' before eventually just showing an empty screen. The LFFTS service starts and stops without issues. There doesn't appear to be a port issue. AV was uninstalled, which also didn't change anything.
In the registry, there is no key within the Database key under LFFTS, which is the main difference I've observed there between a functional system and this one. In a functional system, there should be a subkey within the Database key for each search catalog configured. However, in this particular system, there is no Database subkey.
Another strange thing we've observed is that after we try to open the Index node in the Admin Console after a restart of the server, we can't right-click any files on the desktop or in File Explorer and get the context menu to appear where you can cut, copy, etc - the cursor just spins and nothing ever happens. It works right after a server restart, but as soon as we try to open the Index node in the Admin Console, then we observe this behavior. Restarting the explorer.exe process does not fix it.
I have a support case open regarding this but haven't heard anything back in a couple days and the customer is getting antsy, so figured I'd see if anyone else here has run into something like this.
Thanks!
Question
Question
LFFTS - Can't open Index node in Admin Console, text-searching does not work
asked on October 20
•
Show version history
0
0
Replies
replied on October 20
Never to this extreme. I have had corrupted indexes that had to be deleted, but no hang ups. Try unregistering and re-registering the repository.
0
0
replied on October 21
Ended up being a port issue. LFS had somehow been configured to communicate with LFFTS on port 5051, while LFFTS was expecting the default 5053. Not sure how that got changed, but everything worked normally after changing the FTSport key in the registry to 5053.
0
0
You are not allowed to follow up in this post.