If you have enabled Advanced Search and other parts of the ED dashboard are working fine, then check in the restapi.log file for messages like (For assistance with finding the restapi.log, please see this page: Configuring the Log and Audit Trail ):
'ERROR: column "lucene_sort_order" of relation "temp_violations" does not exist'
'bad SQL grammar [insert into TEMP_VIOLATIONS...'.
If these errors are found, then do the following to resolve the issue:
Stop Tomcat or your web application server (see the documentation with your web application server if you need assistance with this or other steps below).
In the pgadmin query window, issue the following commands:
set search_path=<name of the central database having the issue>;
drop table temp_violations;
Then, drop the folder ED located at <war-folder>/indexesDirectory/ED (the folder with the domain name under indexesDirectory and where <war-folder> is your deployment folder on your web application server)
Restart tomcat or your web application server
Using the static/default interface, send a PUT request : ED/violations-index (don't forget the PUT, if you let the GET you will have a 404 error) as in the below screenshot:
Go to the advanced Search page and see if this has resolved your issue.
This error is normally caused by using an older dashboard version and trying to use Advanced Search with that version prior to upgrading to a later version. Some prior versions had a partial implementation of Advanced Search.