Data Collections fail with 'An invalid XML character (Unicode: 0x0) was found in the element content of the document' / 'Illegal XML character: 0x0' errors in RSA Identity Governance & Lifecycle

4 years ago

Originally Published: 2015-10-30

Article Number

000042740

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: All

Issue

The Test of a Data Collector (Collectors > {Collector type} > {Collector name} > Test button) in RSA Identity Governance & Lifecycle fails with the following error message:

Collector test failed:
org.apache.xmlbeans.XmlException: error: Illegal XML character: 0x0
org.apache.xmlbeans.impl.piccolo.io.IllegalCharException: Illegal XML character: 0x0
at org.apache.xmlbeans.impl.piccolo.xml.XMLReaderReader.read(XMLReaderReader.java:169)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yy_refill(PiccoloLexer.java:3474)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:3958)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:706)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:690)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:677)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208)
at com.aveksa.schema.system.IdentityDataDocument$Factory.parse(IdentityDataDocument.java:247)
at com.aveksa.server.core.IdentityDataCollector.getTestIdentityData(IdentityDataCollector.java:310)
at com.aveksa.gui.objects.collector.identity.GuiIdentityDataCollector.getTestIdentityData(GuiIdentityDataCollector.java:175)
at com.aveksa.gui.pages.admin.collector.identity.test.TestIdentityCollDialogView.printContent(TestIdentityCollDialogView.java:27)
...

An attempt to run the Collector fails in the DataPreProcessing step and Admin errors are generated:

The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log). Note the error helps pinpoint the location of the data that cannot be parsed.

09/01/2020 11:58:06.065 INFO (Exec Task Consumer#1 - Main) [com.aveksa.server.xfw.TaskExecutor] UNSetting thread on 1909355724 method=Execute
09/01/2020 11:58:06.068 INFO (Exec Task Consumer#1 - Main) [com.aveksa.server.xfw.TaskExecutor] Setting thread Thread[Exec Task Consumer#1 - Main,5,Execution Task] on 1985655897 method=Execute
09/01/2020 11:58:06.291 ERROR (Exec Task Consumer#1 - Main) [com.aveksa.server.xfw.DataPreProcessingExecutor] XML parsing failed at data source=/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/deployment/deployment4f07de1dfaea6726/aveksa.war-20d1cb8965a61cc3/WEB-INF/config/agent-transaction-data/file_63
09/01/2020 11:58:06.297 ERROR (Exec Task Consumer#1 - Main) [com.aveksa.server.xfw.TaskExecutor] Failed method=Execute ExecutionTask[TaskID=380 RunID=212 Source=3 Type=DataPreProcessing Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.collector.DataProcessorException: org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 16; An invalid XML character (Unicode: 0x0) was found in the element content of the document.
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:152)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeTask(DataPreProcessingExecutor.java:64)
at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.aveksa.server.collector.DataProcessorException: org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 16; An invalid XML character (Unicode: 0x0) was found in the element content of the document.
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.generateUserDataFile(SAXUserDataPreProcessingFilter.java:320)
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.process(SAXUserDataPreProcessingFilter.java:121)
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.process(SAXUserDataPreProcessingFilter.java:385)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:137)
... 4 more
Caused by: org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 16; An invalid XML character (Unicode: 0x0) was found in the element content of the document.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment, if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)

Cause

One of the collected attributes contains null characters (NULL). An example of an attribute that always contains a null character is the Microsoft Active Directory objectSid attribute:

Resolution

RSA Identity Governance & Lifecycle Data Collectors do not support collecting attributes that contain NULL characters. Only collect attributes that do not have NULL characters. For example, try using the objectGUID attribute instead of the objectSid attribute as a unique identifier for Microsoft Active Directory objects.

Don't see what you're looking for?

Related Articles

Trending Articles