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

AES node information is not displaying in enterprise health tab



User have  AES 7.1.7 on PRPC 7.2.1.

 AES manager portal is not displaying the node information on enterprise health tab .

Error Messages

Rule-Connect-SOAP.PegaAES-Data-AlertOrigin.GetActivityData  - Exception SOAP service failed
    at com.pegarules.generated.activity.ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.step9_circum0(
    at com.pegarules.generated.activity.ra_action_invokeaxis_9ef2dcb432ce73a3cff35a859a998338.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.step8_circum0(
    at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pegarules.generated.activity.ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.step8_circum0(
    at com.pegarules.generated.activity.ra_action_executegetactivitydata_2b89bbb940a6a1b28105714de8f33cbc.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(
    at com.pegarules.generated.activity.ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.step8_circum0(
    at com.pegarules.generated.activity.ra_action_getruleinfo_d8fba9ad84eeeaf00ab660592c0acd8b.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(
    at com.pegarules.generated.activity.ra_action_researchorigins_b85a2d4be68d2552cd50ddd2a55b7b7b.step2_circum0_PegaAES_Data_AlertOrigin(

Steps to Reproduce

Not Applicable

Root Cause

The user has updated soap servlet url of monitoring node on the PDC landing page of monitored node. Then, the user updated the exception and alert appenders in prlogging.xml of monitored node. Original connection string url  is showing  wrong monitored node url in  pegaaes-data-nodes instance for the operator aesdeveloper.


All the exception and alert appenders related to AES has been removed .
User confirmed context root has been changed for monitored node .

So after updating  the correct monitored node url in new connection string of pegaaes-data-nodes ,system information started displaying .

Published October 7, 2016 - Updated October 8, 2020

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.

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