Support Article

Tracer does not work properly from SMA



When trying to access tracer from System Management Application (SMA), an error is received.

Error Messages

Please restart Tracer because Tracer session error: Session [session ID] does not exist

Steps to Reproduce

Select a requestor and click on the tracer.

Root Cause

Refer to the product documentation: SMA user guide does not provide enough clarity on the URL that needs to be specified for connecting to the Pega node. Often times the URL used to configure a node on prsysmgmt is same as the used to log into the Dev portal. These URLs are sometimes loadbalancerURLs and cause issues when SMA is configured to use them to connect to PRPC. 


The URL should use the exact your_hostname:soap_port instead of the loadbalanced URL.


Published July 26, 2016 - Updated August 1, 2016

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.