VERIFIED SOLUTION i

Error "Failed to load config repository class com.pb.config.repository.xml.XMLConfigRepository"

Product Feature: Installation / Upgrade
Configuration: JBoss
 

Issue

JBOSS is started with errors, causing inability to login to EO Admin or EO Correspondence. The errors seen in JBOSS:
 
Caused by: com.pb.eventmonitor.exception.EventMonitorException: Failed to load config repository class com.pb.config.repository.xml.XMLConfigRepository.
at com.pb.eventmonitor.util.EventMonitorConfig.getString(Unknown Source) [eventmonitor-common.jar:]
at com.pb.eventmonitor.util.EventMonitorConfig.getConfigPath(Unknown Source) [eventmonitor-common.jar:]
at com.pb.eventmonitor.event.consumer.EventConsumer.getConfigPath(Unknown Source) [eventmonitor-core.jar:]
at com.pb.eventmonitor.event.consumer.EventConsumer.loadConfiguration(Unknown Source) [eventmonitor-core.jar:]
... 18 more
Caused by: com.pb.config.ConfigFrameworkException: Failed to load config repository class com.pb.config.repository.xml.XMLConfigRepository.
at com.pb.config.repository.ConfigRepositoryFactory.newInstance(Unknown Source) [config-framework.jar:]
at com.pb.config.repository.ConfigRepositoryFactory.newInstance(Unknown Source) [config-framework.jar:]
at com.pb.config.iface.pojo.ConfigAPIPojo.<init>(Unknown Source) [config-framework.jar:]
at com.pb.config.iface.pojo.ConfigAPIPojo.getInstance(Unknown Source) [config-framework.jar:]
at com.pb.eventmonitor.util.EventMonitorConfig.getString(Unknown Source) [eventmonitor-common.jar:]
... 21 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_45]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_45]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_45]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_45]
at com.pb.config.repository.ConfigRepositoryFactory.newInstance(Unknown Source) [config-framework.jar:]
... 25 more
Caused by: java.io.FileNotFoundException: C:\Windows\System32\{INSTALLATION.LOCATION} (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method) [rt.jar:1.6.0_45]
at java.io.FileInputStream.<init>(FileInputStream.java:120) [rt.jar:1.6.0_45]
at java.io.FileInputStream.<init>(FileInputStream.java:79) [rt.jar:1.6.0_45]
at com.pb.config.repository.xml.XMLConfigRepository.loadRepository(Unknown Source) [config-framework.jar:]
at com.pb.config.repository.xml.XMLConfigRepository.<init>(Unknown Source) [config-framework.jar:]
 

Cause

Usually FileNotFoundException error is caused by missing running the database post update script after the base installation. The database post update script will update {INSTALLATION.LOCATION} with the correct location. it is possible that the post-install-update sql script has not been ran or you are pointing to the wrong database with the datasources.


We can run the sql statement below to validate whether we have missed running post-install-update.sql.

SELECT * FROM CF_PROPERTY;

Above query will return few columns of which one of them is named CONFIG_VALUE; the value of this column will be the correct path of config-settings.xml file. This will not be the case if we have missed running post-install-update.sql.

Resolution

UPDATED: August 1, 2019
In order to resolve the error:
Run post-install-update.sql to update the correct EngageOne database. The script is located at
<Install_Folder>\sql\post-install-update.sql

<Install_Folder> above is the installation directory configured during EO installation. Default is C:\Program Files\PBBI CCM|EngageOne


It is IMPORTANT to note that above sql script is NOT the same as the sql scripts found under the "mssql" folder within Engage One installation CD.