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

prpcUtils fails with JSR94 service authentication failure



User is running ./ import to import an archive into the system and fails on a JSR94 service authentication failure.

Error Messages

2015-04-22 09:40:44,096 [ ] [ STANDARD] [ ] ( external.util.Application) INFO - Importing application bundle as user PRPC71_DATABASE_USER
2015-04-22 09:40:45,774 [ ] [ STANDARD] [ ] (l.access.RuleCandidateIterator) INFO JSR94|Deployment|Utility|pxImportAppBundle - Single candidate rule resolution optimization is enabled
2015-04-22 09:40:59,063 [ ] [ STANDARD] [ PegaRULES:07.10] ( ERROR JSR94|Deployment|Utility|pxImportAppBundle|AB1629C53C51B81E2A27F3B79B1D1BE90 - JSR94 service [Deployment][Utility][pxImportAppBundle] failed:Authentication failed
2015-04-22 09:41:00,147 [ ] [ STANDARD] [ PegaRULES:07.10] (vices.jsr94.PRStatelessSession) ERROR - executeRules() - exception JSR94 service [Deployment][Utility][pxImportAppBundle] Authentication failed
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(

Steps to Reproduce

Run ./ import.

Root Cause

The root cause of this problem is defect or misconfiguration in the operating environment. Within the file there are properties to allow user to use a Pega operator's access group to determine runtime context instead of the App Requestor's access group.  

User had set these properties to the database username and password instead of a Pega operator's username and password.


The root cause of this problem is software use or operation error. Leave these properties blank in the file and then do the import.

# Use the following properties if you want to use a user's access group
# to determine runtime context instead of the App Requestor's access group

Published March 10, 2016 - Updated October 8, 2020

Was this useful?

100% 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