Support Article
Pega7 rulebase setup process fails
SA-6024
Summary
Pega 7.1.7 Rulebase setup with MS SQL Server was failing to create an XPathFactory for the default object model.
JDK version (javac -version) - 1.7.0_51
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 Pega7 Rulebase.
Root Cause
Issue was with the JAVA_HOME environment variable setting. There was an extra backward slash at the end the JDK path which was causing this issue.
Resolution
Removing extra backward slash at the end of JAVA_HOME variable has resolved the issue. For example, user should set JAVA_HOME as “C:\Program Files\Java\jdk1.7.0_10” instead of “C:\Program Files\Java\jdk1.7.0_10\”.
Published January 31, 2016 - 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.