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

Failed to retrieve Rule-Service-SOAP instance PegaAES.Events

SA-16759

Summary



Recurring "Failed to retrieve Rule-Service-SOAP instance PegaAES.Events.logAlert using default rulesets" error message found in the application logs.

User Environment Details
  • Pega 7.1.8
  • AES 7.1.7

Error Messages



ERROR your_hostname.your_domain.org|127.0.0.1  - Failed to retrieve Rule-Service-SOAP instance PegaAES.Events.logAlert using default rulesets (Data-Admin-ServicePackage PegaAES doesn't exist)
com.pega.pegarules.pub.PRException: Failed to retrieve Rule-Service-SOAP instance PegaAES.Events.logAlert using default rulesets (Data-Admin-ServicePackage PegaAES doesn't exist)


Steps to Reproduce



Not applicable


Root Cause



A defect or configuration issue in the operating environment: 
This issue usually occurs when the system is not setup as an AES server but some Pega node is sending to it SOAP requests misinterpreting it as one.  
When the remote node send a SOAP request to the current PRPC isntance and the AES SOAP service is not present, the error is logged.

Resolution


 
Perform the following local-change:
  1. Identify the IP address of the remote node that is executing the SOAP request (127.0.0.1 in the former example)
  2. Connect to the node idenfied by the IP Address and either update the AES URL in the Pega Diagnostic Cloud Landing Page or update the prlogging.xml file with the correct endpoint of the AES Server.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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