Question
SMA Tracer not working
Hi,
While trying to access the Tracer in DEV SMA , we are facing the following error.
Although the selected requester is an active session,the trace displays the below mentioned error.
Please suggest.
**Updated by moderator: Marissa. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option.***
Seeing the first screen, it suggests that you might be trying to trace the stale session.
Is this issue coming with all the requestors or only with some requestors?
Are you trying to remote trace any requestor?
These errors also come when it is configured with wrog details of the PRPC Primary and Diagnostic URL.
Hi,
With regards to this specific question (How can you trace an agent if the tracer isn't working via SMA), you can still delay the agent to cause the requestor to show up in the SMA's "Requestor Management" screen. You can then launch tracer from the developer portal, and use the "Remote Tracer" and select that same requestor from the dropdown. The timing can be a little tricky, so its not ideal, but it allows you to trace the agent when you can't launch tracer from SMA.
With regards to the original behavior, I found the following support article that sounds like it might be helpful:
https://community.pega.com/support/support-articles/tracer-error-when-event-traced-prpc-63-sp1
Hope this helps!
-Kurt