Differences in SAS Enterprise Guide 4.1 and 4.2

1

SAS Enterprise Guide uses HTML as the output default format. So for converted projects in SAS EG 4.2, there is a possible situation where the reports fail to view. Change the default back to HTML (or deploy SAS EG 4.2 with that format option selected).

The option in 4.2 is available at: Tools > Options > Results > Results General

An example of the error message:

Unable to read SAS Report file.
--------------------------------------------------------
'<', hexadecimal value 0x3C, is an invalid attribute character. Line 241, position 81.
------------------------------ Technical Information Follows ------------------------------
System.Xml.XmlException: '<', hexadecimal value 0x3C, is an invalid attribute character. Line 241, position 81.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args)
at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at SAS.Report.Models.XML.XMLParse.CreateDOM(Stream file, String fragment, Hashtable customObjectMap)
at SAS.Report.Models.XML.XML.ReadReport(Stream inputStream, Hashtable customObjectMap)
at SAS.Report.Models.XML.XML.ReadReport(FileInfo file, Hashtable customObjectMap)
at SAS.Report.Models.XML.XML.ReadReport(String filename, Hashtable customObjectMap)
at SAS.Report.Viewer.SASReportView.ReadReport(String reportFileName)
at SAS.EG.ProjectElementViews.SasReportView.OpenDocument()
------------------------------ End of Technical Information ------------------------------

Share

About Author

Angela Hall

Senior Technical Architect

Angela offers tips on using the SAS Business Intelligence solutions. She manages a team of SAS Fraud Framework implementers within the SAS Solutions On-Demand organization. Angela also has co-written two books, 'Building BI using SAS, Content Development Examples' & 'The 50 Keys to Learning SAS Stored Processes'.

1 Comment

  1. We hope such errors are few and far between, but we are aware of a few fancy uses of TABULATE and REPORT that can cause some issues with SAS Report output.If you encounter something like this, you can help us to make sure we've got you covered: e-mail a sample report (export as SRX file) to SAS Technical Support (support@sas.com).Chris@SAS

Back to Top