Hi Sulfath, one of my Sage colleagues (Robert Hurson) created a great troubleshooting list for troubleshooting Quick Find, please see the below list.

Troubleshooting steps

Should an issue be reported with the Quick Find feature, it’s important to determine the scope of the problem. The following questions may be relevant:

• Are all records for a given entity affected, or just a certain search string? It’s important to determine whether the feature as a whole is not working, or whether records added before or after a certain time are affected.
• Does the issue affect just that entity / field, or are results returned on other entities or fields? If only certain entities or columns or affected, it may be worthwhile checking the field options under Administration | Customisation | | Fields, or the indexed entity settings under Administration | System | Quick Find.
• Can the sought-for record be found using a normal search as that user in Sage CRM? Does the user have rights on the entity?
• Are all users affected?
• Does Quick Find work using another browser, or on another machine? Does the affected user use a different method (a different domain name, or a VPN) to access Sage CRM?

The following steps are suggested as a method for troubleshooting a reported failure of the Quick Find feature.

1. Attempt to search for a known good record using the Search box on any Sage CRM screen. If a record is returned, then investigate whether a sought-for record is missing, and whether the issue is due to when the record was added / updated, or whether the user has security rights on the record.
a. If records created before a particular time are not found, then try updating one and seeing if it is found by Quick Find after a short delay.
b. If records created after a particular time are not found, then try restarting the service. If the record is not found after a few minutes, then the core may need to be recreated.
2. As an administrator, navigate to Administration | System | Quick Find. Check the value of the Quick Find service status field. Remember that this is an end-to-end test. If this is reporting that the status is stopped, then there may be an issue with HTTP requests going from the user’s browser to the CRMJ webapp, and onwards to the Quick Find service.
3. Check whether the Quick Find service is running. When logged in on the server, an administration server should be available at http://localhost:8983/solr/. Details regarding the loaded CRM cores should be available by selecting the Core Admin link on the left.
a. If this works, then there may be an issue with the CRMJ webapp. Check if the Interactive Dashboard is working, and troubleshoot further if that feature is not working. A “Hello World!” status page should be available at http://localhost/sdata/j/
b. If the dashboard is working correctly, then you can try one of the following:
i. Use the browser’s developer console to determine whether a JavaScript error is occurring when the Search screen is accessed or admin page are used.
ii. Use Fiddler to check for HTTP errors when accessing /sdata/j/sagecrm2/$service/quickFind
4. If the Quick Find / Solr admin page does not display, then check whether the Quick Find service is running using the services control panel (services.msc).
a. If it is not running, attempt to start it.
b. If it is running, then attempt to restart the service. Wait thirty seconds after restarting, then attempt to access the URL again.
5. If the service is running and the page cannot be accessed, then check whether the URL being used is correct. This URL can be obtained by checking the SolrEngineUrl entry in the Custom_Sysparams table.
a. If this value is not http://localhost:8983/solr/ then there may have been an issue changing the Quick Find service port. You may want to determine why this was done, and double-check the steps for changing the port.

Hopefully working through the list has resolved the issue, however should you still require assistance, please may you log the issue with regional support, once resolved, we can update this post.