AWI Search is producing an error message - U00045014 Exception 'org.apache.lucene.queryparser.classic.ParseException

Document ID : KB000125430
Last Modified Date : 29/01/2019
Show Technical Document Details
Issue:
When executing a search in the AWI the following exception is issued: 
 
U00045014 Exception 'org.apache.lucene.queryparser.classic.ParseException: "Cannot parse '((name:*log*) AND (granularity:OBJECT) AND (client:XYZ) AND (isLink:false)) AND (((aclPath: OR aclPath:*)) OR aclPath:\\<NOFOLDER>)': Encountered " <OR> "OR "" at line 1, column 92. 
Was expecting one of: 
<BAREOPER> ... 
"(" ... 
"*" ... 
<QUOTED> ... 
<TERM> ... 
<PREFIXTERM> ... 
<WILDTERM> ... 
<REGEXPTERM> ... 
"[" ... 
"{" ... 
<NUMBER> ... 
"' at 'org.apache.lucene.queryparser.classic.QueryParserBase.parse():122'. 
U00045015 The previous error was caused by 'org.apache.lucene.queryparser.classic.ParseException: "Encountered " <OR> "OR "" at line 1, column 92. 
Was expecting one of: 
<BAREOPER> ... 
"(" ... 
"*" ... 
<QUOTED> ... 
<TERM> ... 
<PREFIXTERM> ... 
<WILDTERM> ... 
<REGEXPTERM> ... 
"[" ... 
"{" ... 
<NUMBER> ... 
"' at 'org.apache.lucene.queryparser.classic.QueryParser.generateParseException():698'. 
U00003620 Routine 'com.automic.search.lucene.searcher.IndexSearch' forces trace because of error.

The error appears in the CP JCP log file. 

This occurs after trying to create an object and assign the login object. 
Resolution:
Workaround: please check the Authority for the user and also all user groups for the user receiving the error. To get pass the problem, please replace any BLANKs with an '*' or a correct Name in the Authority for the user or user group.
Please refer to this article for further details:
https://comm.support.ca.com/kb/ae-blank-authorizations-name-cant-search-by-using-awi/KB000103054

Solution:
This issue has been corrected and is currently planned for release in the following versions: 
Automation Engine 12.1.4 - available 
Automation Engine 12.2.2 - middle of February 2019 
Automation Engine 12.3.0 - end of February 2019 

Please download and install one of the above mentioned or higher versions to obtain the correction.