nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR: Cannot search because indexer is 'offline'

trond

Hi folks,

I am new to WorkSite MP, and have a pretty serious issue that I would really appreciate some help with.
When trying to perform a fulltext search on our worksite MP portal, we get the following error message:
Information
WorkSite MP cannot perform a full-text search at this time because the indexer is offline. Please contact your support staff.
Please try your search again after your support staff ensures that the indexer is running.

What is really weird, is that the search engine doesn’t work unless I put something into the meta data tags. The error message says that the indexer is offline – but if I put something in one of the meta data tags it works just fine...

It looks like we have MP 3.1 SP1 installed.

* We have tried restarting the indexer, but the problem remains.
* I also tried Re-Indexing the Index Collection.

Any help/guidance/brainstorms would be highly appreciated.

Thanks,

Trond

Edited by trond on 11/12/04 04:55 PM (server time).

Find more posts tagged with

Comments

sphan_xell

Hi,
I experienced the same problem before in WorksiteMP 3.0. The issue was with the Indexer engine. What I did was to rebuild it? However, it seems like you've already tried that.
What you might want to try:
1. Look at the CMS log file to see the behind the scene interaction on the server. Maybe there are error messages there that could give you more hint.
2. Try the Advanced Search on a non-extended workspace (where there's no customization of the WebApp interface). Improper modifications of the "searchAdvanced.xml" could also be a factor.

Hope this help,
sphan_xell.

Migrateduser

Open configuration manager. You can either recreate the configuration from scratch or just make some changes. Either way you want to activate a save configuration mode.

After saving the configuraion, restart BOTH the indexer and CMS and searches should work now.

JTNeville

You should look in the CMS log and the indexer log on the indexer server. I would guess you will see an error indicating that the the Indexserver can't see the CMS server and make a connection.

Verify that whatever you are using, host files, dns entries correctly identifies both servers and that they can resolve each other's name to IP.

You will also want to verify that the indexer service in config manager has the correct libraries assigned to it.

Finally, there is a known issue where the indexer needs to be forced to rebuild itself after upgrading to SP1, 3.1. There is a hot fix available on the support site and a document describing the steps to take to implement it.

That should get ya rolling.

maltobello

as others have suggested, the answer, or the start of one is probably in the log files. our indexer goes off line from time to time when the server loses touch with the file server where the index is located. I get error messages saying that the indexer can't write to the file server, then I delete the index collection and re-index, and it works OK. This may not be your problem, but it shows that the logs are the place to look to find out the nature of the issue.

Migrateduser

Hi,
1) Delete the created indexer in configuration Manager and recreate it.
2) Restart the CMS as well as indexer.

Hope this should work.