Question


Wells Fargo
IN
Last activity: 7 Aug 2020 8:04 EDT
Cannot Launch Multiple Tracer Sessions for a requestor
Hi,
when I launch a tracer and close it. Again when I launch the trace I am getting this error "Cannot Launch Multiple Tracer Sessions for a requestor. This requestor is being traced by the operator ' ' "I am using Pega in my local machine.
I need to log off and log in to launch tracer


Pegasystems Inc.
FR
Hello,
What version of PRPC are you running exactly?


South Florida Water Management District
US
we are using 7.2.1 and we are facing this issue recently. Not sure what setting caused this issue.


Pegasystems Inc.
IN
Hi ,
try clearing all cache from the browser and test the same scenario, as it worked fine for me.


FlowX Consultancy
NL
We are on Pega 7.4 and have recently encountered the same issue, while as far a we know it was not a problem in the past. We are not aware of changing any settings in pega. We can only solve this each time by logging out and in again.
We encountered this issue using Chrome. Are you using Chrome as well (maybe the chrome browser was updated recently and causes this behaviour)?
Are you also using Pega Cloud?


Pegasystems Inc.
IN
Hi,
For Pega 7.4 , there is a hotfix for the reported scenario.
Thank You,


Northbridge
CA


Pegasystems Inc.
IN
Hi,
You can raise an SR to get the hotfix for Pega 7.4.
Thank You,


FlowX Consultancy
NL
We are now using chrome 74.0.3729.169 and do not have the issue anymore. (without changing anything in pega)


ASB Bank
NZ
Hi Guys,
We are facing the same issue with Chrome. I believe the issue is due to the Chrome update.
If anyone has got a solution or an update from Pega please share the steps to resolve this.
Thanks,
Shantanu


Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.


aflac
US
Having same issue. have you find the solution yet?
Accepted Solution


ASB Bank
NZ
Yes there is a rule TraceMain in which you need to replace


FlowX Consultancy
NL
Thanks @ShantanuN0145 your solution worked like a charm in a private edit.
I hope Pega will put this in a hotfix soon.


ASB Bank
NZ
You are welcome !
There is a hotfix for this by the number HFIX-54777.
You can request Pega for the hotfix by raising an SR.
Regards,
Shantanu


Vodafone
IN
Hello ,
I am facing this same issue in Pega 7.1.8. Can anyone please provide solution.
I have searched the function name is TraceMain but i cannot find it.
Thanks,
Niti


Pegasystems Inc.
US
Hello!
Did you try the solution that was provided in the reply marked as the Correct Answer by @ShantanuN0145?


FlowX Consultancy
NL
As said before you can request and install a hotfix.
If you prefer a local change instead, you can search for the rule TraceMain. Since this rule is an internal rule, it is shielded of from rule search by default.
Until Pega 7.3:
If you want to be able to find such rules anyway, you can type the prefix 'old:' in front your search text. For example: old:TraceMain
From Pega 7.4 onwards:
If you want to be able to find such rules anyway, you can go to your operator preferences (right top click your operator icon and select 'Preferences'), and select the checkbox for 'Enable diagnostic features'. Log out, log in, and you can search for internal rules as well so you can find the TraceMain rule.
Updated: 18 Feb 2020 3:22 EST


Wagner Development Solutions
HU
Hi, it's still occurring in Pega version 8.3 with Chrome 80.0.3987.106 even in incognito mode.
I also tried the mentioned change in private edit but did not help.


Pegasystems Inc.
JP
This is occurring in 8.2.1 too. I guess this problem is caused by recent chrome update. In my case, I can avoid logout/login to run tracer again by one of the followings.
- Admin studio > Requestors. Run "Terminate Trace" on your requestor
- Run pzTerminateTracerSessoin activity. The parameters can be found in clipboard. NodeId should be pxProcess.pxSystemNodeID, RequestorId should be pxRequestor.pzRequestorId
- Private edit TraceMain (HTML). Modify "window.onbeforeunload = function(){closeAllWindows();};" to "window.parent.onunload = function(){closeAllWindows();};"
- Use Firefox


Coforge DPA Aus Pvt Ltd
AU
work-around -
Private Edit activity pzStartTracerSession in class Data-TRACERSettings, Delete steps 2 to 6, Save rule


Pegasystems Inc.
IN
Hi,
Try using another browser apart from chrome.
There seems an issue with the chrome browser.
Updated: 6 Aug 2020 15:27 EDT


Highmark Health
I am getting this same issue in Pega v8.3 and v8.4 as well , is pega trying to fix this issue in v8.5 ??
Thanks,
Sudheer Nimmagadda.
Updated: 7 Aug 2020 8:04 EDT


Clocklike Minds Sp. z o.o.
PL
Try to enable this flag in Chrome chrome://flags/#allow-sync-xhr-in-page-dismissal