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

Unable to quiesce from AES



Unable to quiesce nodes through Autonomic Event Services (AES). Run State node is Unavailable when Quiesce screen is loading.

It was found through the tracer that nodes were retrieved from the system when the Quiesce screen was loading. However, the ConnectionString was blank for each node.

Error Messages

Not Applicable

Steps to Reproduce

1. Open AES Manager Portal.
2. Go to Quiesce Management.

Root Cause

A defect in Pegasystems’ code or rules.


Follow the steps given below to enable the quiesce functionality from AES.

1. Log in as AES Developer. Under the Application Explorer, change the top level node to PegaAES-Data-Nodes.
2. Right click the class in the tree pane, and choose View > Instances. This displays the details of each node including a Connection String.
If this is blank, set it using the format given below.

http://<monitored node server>:<port>/prweb/PRSOAPServlet

3. Create a new Ruleset. Name it accordingly.
Check the Update my current Application to include the new version before clicking Create and …

An error may occur during the save. This must disappear at the end of the save.

4. Log out and log in. Open the AES Application rule, to see the ruleset listed under Application Rulesets. 

5. Clear out the older data page.
Since this already exists in the Clipboard, the activity which builds it will consider a rebuilt redundant.
To clear out the existing data page, search for the D_EnabledNodes Data Page rule.

6. On Load Management tab, click Clear Data Page. When prompted, check Flush All and submit.

A verification message saying that the page has been flushed successfully will be sent.
The presence of this page can be verified by looking at the Clipboard under Data Pages > Node.

7. Search and open GetAllNodes activity. Choose Save As, and save it in the new ruleset.

Make the changes to the Obj-Browse so that it returns ConnectionString and SystemNode. Check UseListWeightList and Select boxes for all fields.

8. Save the rule again.

9. Open the AES Manager portal with AES Developer's login. Click the Quiesce link.

The nodes must be in Running state.

This must be reflected in the Clipboard page as well.

Published February 25, 2016 - 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.

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