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

InvalidConfigurationException: No such Access Group: AESRemote

SA-48501

Summary



InvalidConfigurationException displays in the SystemOut log on monitored nodes.


Error Messages



com.pega.pegarules.pub.context.InvalidConfigurationException: No such Access Group: AESRemote for thread STANDARD
From: (ABD5B8E90C01735F42116E63F268DD16D:PegaAESRemote)


Steps to Reproduce



Unknown


Root Cause



A defect or configuration issue in the operating environment

The service package used the PegaAESRemote access group which was configured incorrectly.


Resolution



Perform the following local-change in the PegaAESRemote service package:
  1. Set the access group to PegaAESRemote.
  2. On the Advanced tab of the PegaAESRemote access group, set the Production Ruleset to PegaAESRemote:07-10.
  3. Click Save.

Tags:

Data Integration

Published March 10, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Visit the Collaboration Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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