Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error while installing Pega 7.1.7

SA-4271

Summary



Rulebase setup for Pega 7.1.7 fails.

Error Messages



[java] Error generating ddl for mssql: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: java.util.ServiceConfigurationError: javax.xml.xpath.XPathFactory: jar:file:/PEGA_MEDIA/scripts/lib/saxon9he.jar!/META-INF/services/javax.xml.xpath.XPathFactory:2: Illegal configuration-file syntax

     [java] java.lang.RuntimeException: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: java.util.ServiceConfigurationError: javax.xml.xpath.XPathFactory: jar:file:/PEGA_MEDIA/scripts/lib/saxon9he.jar!/META-INF/services/javax.xml.xpath.XPathFactory:2: Illegal configuration-file syntax
     [java]          at javax.xml.xpath.XPathFactory.newInstance(XPathFactory.java:102)
     [java]          at com.pega.pegarules.data.ddl.SchemaManager.getTopLevelDocument(Unknown Source)
     [java]          at com.pega.pegarules.data.ddl.SchemaManager.getSchemaManagerFromCustomExpression(Unknown Source)
     [java]          at com.pega.pegarules.data.ddl.SchemaManager.getCustomCreateDDL(Unknown Source)
     [java]          at com.pega.pegarules.data.ddl.SchemaManager.getCreateDDL(Unknown Source)
     [java]          at com.pega.pegarules.data.ddl.SchemaGenerator.generateInstallDDL(SchemaGenerator.java:238)
     [java]          at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1168)

 

Steps to Reproduce



Run the PRPC_Setup.jar to setup the rulebase.

Root Cause



Issue was with the JAVA_HOME variable. There was an extra backward slash at the end  the JDK path, causing this issue.

i.e JAVA_HOME was set to “C:\Program Files\Java\jdk1.6.0_10\”

Resolution



Removing extra backward slash at the end of JAVA_HOME variable solved the issue. JAVA_HOME should be for example “
C:\Program Files\Java\jdk1.6.0_10” instead of  “C:\Program Files\Java\jdk1.6.0_10\”

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us