Applies to Pega Platform versions 7.2.1 through 8.3.1

Symptoms

After installing hotfixes to support the latest Pega Predictive Diagnostic Cloud (PDC) features in previously updated Pega systems, you see PegaAESRemote agent issues manifesting in RuleNotFoundExceptions and ‘Execution denied’ errors.

Monitoring Details in the PDC Enterprise landing page are also missing. There is no information for the following sections:

• Database query statistics
• Database table statistics
• Agent status
• Queue status
• Listener status
• Hotfix history
• Elasticsearch status

Errors

Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PUSHDEADLOCKINFO' that applies to 'PegaAESRemote-Interface-DeadlockInfo'. There were 2 rules with this name in the rulebase, but none matched this request. The 2 rules named 'PUSHDEADLOCKINFO' defined in the rulebase are: 2 related to applies-to class 'PegaAESRemote-Interface-DeadlockInfo', but were defined in rulesets which are not in your rulesetlist: {PegaAESRemote:07-40-01, PegaAESRemote:07-40-02}  

ERROR - Execution denied for class: PegaAESRemote-Interface-DeadlockInfo (activity: PushDeadlockInfo)

ERROR - Execution denied for class: PegaAESRemote-Interface-DeadlockInfo (activity: PushDeadlockInfo) LogText:Execution denied for class: PegaAESRemote-Interface-DeadlockInfo (activity: PushDeadlockInfo)

ERROR - Execution denied for class: PegaAESRemote-Interface-AgentsInfo (activity: PushAgentsInfo) LogText:Execution denied for class: PegaAESRemote-Interface-AgentsInfo (activity: PushAgentsInfo)

ERROR - Execution denied for class: PegaAESRemote-Interface-ElasticSearchStatus (activity: PushElasticSearchStatus) LogText:Execution denied for class: PegaAESRemote-Interface-ElasticSearchStatus (activity: PushElasticSearchStatus)

ERROR - Execution denied for class: PegaAESRemote-Interface-DBStats (activity: PushDBStats) LogText:Execution denied for class: PegaAESRemote-Interface-DBStats (activity: PushDBStats)

Explanation

The symptoms and errors usually occur when you apply a hotfix to support PDC and later update your Pega system to the next Pega Platform release.

The problem is that the engine caches some rules and, during the update, the newly introduced rules are removed by the Pega Platform update. Consequently, the engine does not find the rules to execute and throws the errors and exceptions. 

Solution

Follow this suggested approach to troubleshoot and resolve the PegaAESRemote agent issues.

1. Collect and examine relevant artifacts:
   • System Scan
   • PegaAESRemote related Errors and Exceptions from PDC or PegaRULES log file
   • System installation and update history
2. Complete a thorough root-cause-analysis investigation:
   1. Review the PegaAESRemote hotfix installation status and ensure that the hotfix is not partially installed.
   2. If a PegaAESRemote hotfix is partially installed, identify the rules and data instances that are not installed.
   3. Check whether the DATA-ADMIN-OPERATOR-ACCESSGROUP PEGAAESREMOTE instance shipped in the hotfix and required to run the PegaAESRemote agents is present.
   4. Validate that the access group DATA-ADMIN-OPERATOR-ACCESSGROUP PEGAAESREMOTE points to the correct application or ruleset stack.
3. Choose the solution that best fits your problem scenario:
   • If rules or instances of DATA-ADMIN-OPERATOR-ACCESSGROUP PEGAAESREMOTE are missing, submit a Support Request for an Existing Hotfix or Product Defect. GCS will generate a custom RAP to ship you the missing instances, ensuring that pxCommitDateTime and pxSaveDateTime of the missing instances is more recent than the current values present in your target Pega system.
   • If DATA-ADMIN-OPERATOR-ACCESSGROUP PEGAAESREMOTE is pointing to the wrong ruleset version (for example, PegaRULES:07.10), manually update the access group record to point to the correct application and, in the Advanced tab, remove the Production ruleset.

Related Content

Updating the PegaAESRemote ruleset to support the latest PDC features

Data collected by Pega Predictive Diagnostic Cloud