Support Article

Import using prpcUtils fails when using encrypted DB passwords



When running a rule import using prpcUtils using encrypted database passwords in and keyring file for prconfig.xml, the import fails with the below error.

Error Messages

Checking Configuration Files: 

/appfiles/PRPCDeploy/scripts/utils/prpcUtils.xml:419: Failed to connect using provided properties. [jcc][t4][10205][11235][4.19.26] Null password is not supported. ERRORCODE=-4461, SQLSTATE=42815

Steps to Reproduce

  1. Encrypt password in 
  2. Create Keyring file for prconfig.xml 
  3. Remove password from prconfig.xml and 
  4. Set pegarules.config and prbootstrap.config in
  5. Run prpcUtils to import a rule

Root Cause

A defect in Pegasystems’ code or rules. The prpcUtils tool has several tasks which are expecting an unencrypted database password in the pega.jdbc.password property in file. Also, there is no way to specify the location of the keyring file to use.


Perform the following local-change: 

Modify prpcUtils.xml to skip testconnectioninfo and _findSystemName tasks. Add the location of the keyring file to the path in prpcUtils.xml.

1.  Comment out pega:testconnectioninfo task around lines 409 to 418
2.  Modify "Processing Configuration Files" task around line 421 to remove the depends='_findSystemName"
3.  Add a path element to the prpc.base.path around line 255 to include the location of the keyring file.  
For example, <pathelement location="C:\PathToDirectoryWithKeyringFile"/>

Published January 31, 2016 - Updated October 8, 2020

50% found this useful

Have a question? Get answers now.

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