My Oracle Support Banner

Xml Error When Crawling WebCenter Spaces Source (Doc ID 1557435.1)

Last updated on NOVEMBER 22, 2016

Applies to:

Oracle WebCenter Portal - Version 11.1.1.6.5 and later
Information in this document applies to any platform.

Symptoms

After upgrading WebCenter from 11.1.1.5.4 to 11.1.1.6.5, there are some problems with crawling of WebCenter Spaces sources. The crawl schedule finishes without a fatal error, but the crawl log shows errors like:

'EQP-60305: Exception when parsing channel'and 'XML-20108: (Fatal Error) Start of root element expected.

 

17:36:44:372 ERROR Thread-4 EQP-60303: Exiting saxthread due to errors
17:36:44:373 ERROR Thread-4 <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected. org.xml.sax.SAXParseException oracle.xml.parser.v2.XMLError:flushErrorHandler:422 oracle.xml.parser.v2.XMLError:flushErrors1:287 oracle.xml.parser.v2.NonValidatingParser:parseRootElement:345 oracle.xml.parser.v2.NonValidatingParser:parseDocument:307 oracle.xml.parser.v2.XMLParser:parse:212 oracle.xml.jaxp.JXSAXParser:parse:292 oracle.search.plugin.rss.SAXThread:run:161 java.lang.Thread:run:595
17:36:44:374 ERROR Thread-4 EQP-60305: Exception when parsing channel: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.. 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. java.lang.Exception oracle.search.plugin.rss.SAXThread:run:173 java.lang.Thread:run:595
17:36:44:374 ERROR Thread-4 caused by:<Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
17:36:44:374 ERROR Thread-4 EQP-60305: Exception when parsing channel: EQP-60305: Exception when parsing channel: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.. 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.. 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.
17:36:44:375 ERROR Thread-4 EQP-60307: Error when processing item channel_error: EQP-60305: Exception when parsing channel: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.. 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.
Error Stack:
java.lang.Exception: EQP-60305: Exception when parsing channel: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.. 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:173)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:345)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:307)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:212)
at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:292)
at oracle.search.plugin.rss.SAXThread.run(SAXThread.java:161)
... 1 more
. Verify that the details of the item such as URL, ACL, etc. are correct

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.