If specific search does not work

Try to change the search criteria, e.g. change the word(s).

If it works, check the search criteria:

•Is it a stop word? If it is, you cannot search for such words.

•Is it a word that cannot be used in searching? For example, Exalead cannot search for any words that contain the "_" (underscore).

•If the content you are searching for was recently uploaded, perhaps is still not being indexed. Check if the Back4 service is running normally.

•If you searched for the same word(s) previously and it worked, consider to rebuild indexes that are maybe damaged.

If any full-text searching does not work

1.Check if the index service (Exalead or other) is started and running on the index server. See How to locate index server in a GN4 system?

2.If available, try to perform searches from the index Web interface and see if there are results. See Connect to the Exalead CloudView Search. If you cannot connect to index Web interface, or it doesn't work, make sure that no other software uses ports required by the index server.

3.If the searching still does not work, scratch and rebuild indexes.

4.If all the previous does not help, consider to reinstall the search engine. See Install Exalead CloudView 5.1.

If the searching used to work and then stopped to work

A possible reason may be the difference of the system clocks between client and server. Ensure that the clocks are always synced. See also If client clock is out of sync with server. See also the explanation in the Typical error messages on startup for the WSE910: An error happened during the processing of a response message... WSE065: Creation time of the timestamp is in the future...

Anyway, if the interruption happened for server unexpected restart, try to refresh manually to re-establish the normal flow of the content on a screen that searches for, let's say, wires, and stopped to update automatically.

Make also sure that the Back4 service is running.

See also

Exalead FAQ and troubleshooting

Reset the CloudView configuration before applying a new configureindex