EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage

If you have deployed an index and crawled it, say PTPORTALREGISTRY – when you run a search against it, you receive an error like “No results were returned. Refine your search by entering a different keyword”

Go to <SES Home>/logs/crawler/crawler and check the logs. You need to view the log, which has the name like search.crawler.i1ds*.mmdd*

Go through the log or search if it has any references to EQP-80330.

Sample search crawler provided below:

[2016-08-31T11:59:10.676-05:00] [search] [ERROR] [] [oracle.search] [tid: Thread-18] [ecid: 0000LRXY^NK9Le7InIZBFJ1NlknK000008,0] [[
java.lang.Exception: EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage
at oracle.search.plugin.rss.SAXThread.startElement(SAXThread.java:388)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1524)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:409)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:292)
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:183)
at java.lang.Thread.run(Thread.java:619)
Caused by: EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage
at oracle.search.plugin.rss.SAXThread.checkNamespace(SAXThread.java:223)
at oracle.search.plugin.rss.SAXThread.startElement(SAXThread.java:242)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1529)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:409)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:293)
... 2 more

]]
[2016-08-31T11:59:10.676-05:00] [search] [ERROR] [] [oracle.search] [tid: Thread-18] [ecid: 0000LRXY^NK9Le7InIZBFJ1NlknK000008,0] [[
java.lang.Exception: EQP-60305: Exception when parsing channel: EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage. Please check the following 1. Verify that the feed conforms to the feed schema and there are no XML parsing errors in the feed. 2. Check that the network to the repository is available. 3. Check that the feed has not been deleted from the repository.
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:194)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.Exception: EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage
at oracle.search.plugin.rss.SAXThread.startElement(SAXThread.java:388)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1524)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:409)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:292)
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:183)
... 1 more
Caused by: EQG-30237: Crawler plug-in warning: EQP-80330: Unrecognized QName <>:ErrorMessage
at oracle.search.plugin.rss.SAXThread.checkNamespace(SAXThread.java:223)
at oracle.search.plugin.rss.SAXThread.startElement(SAXThread.java:242)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1529)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:409)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:293)
... 2 more
]]

Most likely cause of this error is that the Search Framework “Callback User” does not have sufficient permissions necessary to build or crawl the search index. Such issues can arise when you’re installing/configuring SES for the first time or you might have performed an upgrade.

Check the userid used for “Callback User,” and make sure it has the following roles: Search Developer, Search Server, Search Query Administrator, PeopleSoft Administrator and PeopleSoft User.

If your issues is specific to PTPORTALREGISTRY and other search indexes are working fine – it is because of a bug, which has been fixed in PT8.55. To fix the issue, make sure that the permission list PTPT3100 is added to the “Callback User.”