Problem Note 48911: "[Fatal Error] :93:49: An invalid XML character (Unicode: 0x0) was found in the element content of the document" when using a numeric cross class
In SAS® Risk Dimensions®, when you specify a numeric cross-classification variable and attempt to output graphics such as the ALGAP graph by using ODS, an error like the following occurs:
[Fatal Error] :93:49: An invalid XML character (Unicode: 0x0) was found in the
element content of the document.
Internal Exception:org.xml.sax.SAXParseException: An invalid XML character
(Unicode: 0x0) was found in the element content of the document.
org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found
in the element content of the document.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.sas.graphics.app.StatGraphSSR.parseXML(StatGraphSSR.java:499)
at com.sas.graphics.app.StatGraphSSR.render(StatGraphSSR.java:197)
Problem reading XML java.lang.NullPointerException
at
com.sas.graphics.applets.statgraph.StatGraph.getSessionLocale(StatGraph.java:363
2)
at com.sas.graphics.app.StatGraphSSR.render(StatGraphSSR.java:205)
java.lang.NullPointerException
ERROR: Physical file does not exist, C:\DOCUME~1\<userid>\LOCALS~1\Temp\SAS
Temporary Files\_TD440_d22020_\_4B00FA510FB44319DCE03261BFD318D.bmp.
ERROR: Physical file does not exist, C:\DOCUME~1\<userid>\LOCALS~1\Temp\SAS
Temporary Files\_TD440_d22020_\_4B00FA510FB44319DCE03261BFD318D.bmp.
Also, the ODS graphical output is not produced.
The error occurs because invalid characters are written to an XML element when a numeric cross classification is used.
To circumvent this problem, either remove the numeric cross-classification variable or replace it with a character cross-classification variable.
Operating System and Release Information
| SAS System | SAS Risk Dimensions Enterprise Edition | Microsoft® Windows® for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2003 Standard Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2003 for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2008 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows Server 2008 for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Microsoft Windows XP Professional | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Enterprise 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Enterprise x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Home Premium 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Home Premium x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Professional 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Professional x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Ultimate 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows 7 Ultimate x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows Vista | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Windows Vista for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| 64-bit Enabled AIX | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| 64-bit Enabled HP-UX | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| 64-bit Enabled Solaris | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| HP-UX IPF | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Linux | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Linux for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
| Solaris for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2013-01-14 09:21:01 |
| Date Created: | 2013-01-11 17:29:45 |