You perform keyword searches with wildcards but no search result is returned.
Archive Full Text Search Service shows error in Application Events:
Error in Full Text Search.
Exception has been caught in the application
Exception Source: Archive Full Text Search Service
Exception Type: Lucene.Net.Search.BooleanQuery+TooManyClauses
Exception Message: System error.
Exception Target Site: Add
The value of maxClauseCount in Lucene.Net is set to 1024 by default.
Workaround:
To address the issue of keyword searches with wildcards not returning results and encountering a "TooManyClauses" error in the Archive Full Text Search Service, you can implement the following workaround:
1. Edit Configuration File:
Modify the Archive Full Text Search Service.exe.config` file as follows:
xml
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322" />
<requiredRuntime version="v1.1.4322" />
</startup>
<appSettings>
<add key="Lucene.Net.maxClauseCount" value="2048" />
</appSettings>
</configuration>
- Add the key Lucene.Net.maxClauseCount with a higher value (e.g., 2048) in the <appSettings> section of the configuration file.
2. Save Changes:
Save the modified configuration file.
3. Restart Service:
Restart the Archive Full Text Search Service for the changes to take effect. This step ensures that the service now allows a higher limit for the number of clauses in search queries.
Note: Adjust the value of Lucene.Net.maxClauseCount as needed based on your specific requirements and environment. Increasing this value can help alleviate the "TooManyClauses" error when performing searches with wildcards.
This workaround should enable keyword searches with wildcards to function correctly without encountering the previous error in the Archive Full Text Search Service.
