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

Warnings in update logfile

SA-20229

Summary



An administrator has completed running the update.sh script and is seeing a variety of warnings in the logfile.
 


Error Messages



1. [java] 2016-02-22 12:52:13,604 [ main] [ ] [ ] (ernal.access.DataSourceManager) ERROR - Unable to obtain DataSource for thdb

2. Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting
[java] 2016-02-22 12:52:10,462 [ main] [ ] [ ] ( basic.config.SettingsImpl) WARN -
prconfig.xml missing key for initialization/settingsource
[java] 2016-02-22 12:52:10,462 [ main] [ ] [ ] ( basic.config.SettingsImpl) WARN -
This is likely due to using a copy of prconfig.xml from a previous install.
this excludes use of entries in Data-Admin-System-Settings as prconfig settings

3. [java] 2016-02-22 12:52:10,597 [ main] [ ] [ ] (r.context.EtierEnvironmentImpl) WARN - Enterprise tier has no local JNDI context
[java] reason: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial


Steps to Reproduce



Run the update.sh script with the '--force true' option.


Root Cause



These warnings are normal for the update process as it is performed stand-alone outside of an application server. Messages about the inability to access JNDI resource references are all normal and can be safely ignored.

Resolution



These warnings are completely normal for the install process and are no reason to be concerned.  You can move ahead to your next step without any problems.

 

Suggest Edit

Published February 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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