000031630 - RSA Via L&G Collector fails with an Illegal XML character error

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031630
Applies ToRSA Product Set: Via Lifecycle and Governance
RSA Product/Service Type: Access Certification Manager
RSA Version/Condition: 6.8.1, 6.9, 6.9.1, 7.0
Platform: Any
Issue
  • Test Collection fails with the following error message:
User-added image

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) ...


  • Collectors fail in the DataPreProcessing stage with the following error message:
User-added image

org.xml.sax.SAXParseException; lineNumber: 6; 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)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.generateUserDataFile
(SAXUserDataPreProcessingFilter.java:332)
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.process(SAXUserDataPreProcessingFilter.java:121)
at com.aveksa.server.xfw.SAXUserDataPreProcessingFilter.process(SAXUserDataPreProcessingFilter.java:407)
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:136)
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:745)

CauseOne of the collected attributes contains null characters (NUL) which is currently not supported by Via Lifecycle and Governance. An example of an attribute that always contains a null character is the Microsoft Active Directory objectSid attribute:
User-added image
WorkaroundThere is currently no workaround for collecting attributes that contain null characters. Avoid including such attributes any collector. For example: try using the objectGUID attribute instead of the objectSid attribute as a unique identifier for Microsoft Active Directory objects.

Attachments

    Outcomes