ASR fails to generate with 'ORA-31011: XML parsing failed' and 'LPX-00225: end-element tag "ROWSET" does not match start-element tag "APPLICATION_NAME" ' errors in RSA Identity Governance & Lifecycle
Originally Published: 2020-02-05
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.1.0, 7.1.1
Issue
NOTE: An ASR is generated by going to (Admin > Diagnostics > Create Report) or (Admin > System > Diagnostics tab > Create Report) depending on your version of RSA Identity Governance & Lifecycle.
The RSA Identity Governance & Lifecycle user interface (Admin > Diagnostics) shows all Statistic Reports with a status of Generating.
The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has the following errors:
10/13/2019 18:22:21.636 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] Exception checking for internal table usage in collectors java.lang.NullPointerException at com.aveksa.server.system.SystemReport.appendCollectorContainerName(SystemReport.java:359) at com.aveksa.server.system.SystemReport.appendCollectorRow(SystemReport.java:346) at com.aveksa.server.system.SystemReport.checkCollector(SystemReport.java:332) at com.aveksa.server.system.SystemReport.checkForSuspiciousCollectors(SystemReport.java:315) at com.aveksa.server.system.SystemReport.getDBLockdownInfo(SystemReport.java:226) at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:121) at com.aveksa.server.system.SystemReport.access$000(SystemReport.java:52) at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:71) at java.lang.Thread.run(Thread.java:748) 10/13/2019 18:24:43.210 INFO (SystemReport) [com.aveksa.server.db.persistence.PersistenceServiceProvider] executeCallableStatement giving up after hitting SQLException: ORA-31011: XML parsing failed ORA-19213: error occurred in XML processing at lines 11325 LPX-00225: end-element tag "ROWSET" does not match start-element tag "APPLICATION_NAME" ORA-06512: at "SYS.XMLTYPE", line 272 ORA-06512: at "AVUSER.SYSTEM_REPORT", line 257 ORA-06512: at line 1
Please refer to RSA Knowledge Base Article 000030327 -- Arrtifacts 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
This is a known issue reported in engineering ticket ACM-101728.
Note: This issue also causes the problem reported in RSA Knowledge Base Article 000038645 -- 'Exception checking for internal table usage in collectors' and 'java.lang.NullPointerException' errors when generating a Log Artifact zip file in RSA Identity Governance & Lifecycle.
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P05
- RSA Identity Governance & Lifecycle 7.2
Workaround
Related Articles
ASR fails to generate with an 'ORA-31011: XML parsing failed ORA-06512: at "AVUSER.SYSTEM_REPORT", line 245' error in RSA … 225Number of Views Menu bar is not refreshed after creating a Change Request or Pending Submission in RSA Identity Governance & Lifecycle 47Number of Views Partial reject for approvals still provision indirect entitlements for accounts in RSA Governance & Lifecycle 40Number of Views ASR fails to generate with an 'ORA-01422: exact fetch returns more than requested number of rows' error in RSA Identity Go… 65Number of Views How to reset the RSA Authentication Manager 8.x system fingerprint 255Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?