Support Article
App explorer does not populate after update
SA-36363
Summary
After an update from Pega 7.1.7, the Application Explorer in Designer Studio does not populate. There was no on-screen error, but Section Rendering Errors are written to the logs.
Error Messages
Caused by:
org.xml.sax.SAXNotSupportedException: http://xml.org/sax/features/external-general-entities
at org.apache.xerces.framework.XMLParser.setExternalGeneralEntities(XMLParser.java:485)
at org.apache.xerces.framework.XMLParser.setFeature(XMLParser.java:1320)
at org.apache.xerces.parsers.SAXParser.setFeature(SAXParser.java:578)
at org.apache.xerces.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
at org.apache.xerces.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
at com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:466)
... 86 more
Steps to Reproduce
Log in to Designer Studio and click Records.
Page is blank or does not load,
Root Cause
A defect or configuration issue in the operating environment
The wrong SAXParserFactoryImpl class is being used. For a custom Java integration issue, the xerces.jar file was imported into the Pega database. The SAXParserFActoryImpl class in this JAR file is being used instead of the version that Pega expects to be used.
Resolution
Perform the following local-change to the operating environment:
Remove the xerces.jar file from the database.
The Application Explorer displays as expected.
Published April 28, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.