Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

23
Replies
9922
Views
 Meera Mohiddin Shaik (Mohiddin) Wells Fargo Senior Software Engineer
Wells Fargo
IN
Mohiddin Member since 2018 1 post
Wells Fargo
Posted: April 18, 2019
Last activity: August 7, 2020
Posted: 18 Apr 2019 0:44 EDT
Last activity: 7 Aug 2020 8:04 EDT
Closed
Solved

Cannot Launch Multiple Tracer Sessions for a requestor

Report

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

Dev/Designer Studio
Purnendu Dash yvette tran
Posted: 3 years ago
Posted: 19 Apr 2019 13:48 EDT
Siva Arvapalli (SivaArvapalli) South Florida Water Management District
South Florida Water Management District
US
Report

we are using 7.2.1 and we are facing this issue recently. Not sure what setting caused this issue.
Posted: 3 years ago
Posted: 22 Apr 2019 12:21 EDT
Ravi Kumar B (br001) Pegasystems Inc. Principal Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Hi ,

 

try clearing all cache from the browser and test the same scenario, as it worked fine for me. 
Posted: 3 years ago
Posted: 4 May 2019 9:20 EDT
Rogier Simonis (RSIMONIS) FlowX Consultancy Lead System Architect
FlowX Consultancy
NL
Report

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?

Santosh Pratapuram
Posted: 3 years ago
Posted: 15 Jul 2019 22:13 EDT
Nandita Das (dasn1) PEGA Principal Engineer, Technical Support
Pegasystems Inc.
IN
Report

Hi,

For Pega 7.4 , there is a hotfix for the reported scenario.

Thank You,
Posted: 3 years ago
Posted: 7 May 2019 16:10 EDT
Shekhar Yadav (Shakes) Northbridge
Northbridge
CA
Report
We are using 7.4 and have recently started seeing this behavior in Chrome. Only solution is to log off and bank in. Any input from Pega?
Posted: 3 years ago
Posted: 29 Aug 2019 9:07 EDT
Nandita Das (dasn1) PEGA Principal Engineer, Technical Support
Pegasystems Inc.
IN
Report

Hi,

You can raise an SR to get the hotfix for Pega 7.4.

Thank You,
Posted: 3 years ago
Posted: 28 May 2019 9:07 EDT
Rogier Simonis (RSIMONIS) FlowX Consultancy Lead System Architect
FlowX Consultancy
NL
Report

We are now using chrome 74.0.3729.169 and do not have the issue anymore. (without changing anything in pega)
Posted: 3 years ago
Posted: 3 Jul 2019 0:35 EDT
Shantanu Nalawade (ShantanuN0145) ASB Bank Software Consultant
ASB Bank
NZ
Report

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
Posted: 3 years ago
Posted: 3 Jul 2019 2:17 EDT
Vidyaranjan AV (Vidyaranjan) Senior Online Community Moderator
Pegasystems Inc.
IN
Report

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.

Accepted Solution

Posted: 3 years ago
Posted: 15 Jul 2019 21:15 EDT
Shantanu Nalawade (ShantanuN0145) ASB Bank Software Consultant
ASB Bank
NZ
Report

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

<script>
window.onbeforeunload = function(){closeAllWindows();};
</script>
 
with 
<script>
window.onunload = function(){closeAllWindows();};
</script>
However, since this is a final rule you will need to raise an SR for it.
The team will provide you a hotfix for this .
Thanks & Regards,
Shantanu
Aditya Kulkarni Sudheer YLN
Posted: 3 years ago
Posted: 18 Jul 2019 21:30 EDT
Shantanu Nalawade (ShantanuN0145) ASB Bank Software Consultant
ASB Bank
NZ
Report

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
Posted: 3 years ago
Posted: 27 Aug 2019 7:33 EDT
Niti Solanki (NitiS22) Vodafone
Vodafone
IN
Report

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
Posted: 3 years ago
Posted: 2 Sep 2019 7:07 EDT
Rogier Simonis (RSIMONIS) FlowX Consultancy Lead System Architect
FlowX Consultancy
NL
Report

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.

Sreeni Kodati Krishnaveni Baavireddi Varadegowda V
Posted: 2 years ago
Updated: 2 years ago
Posted: 18 Feb 2020 3:03 EST
Updated: 18 Feb 2020 3:22 EST
Miklos Wagner (MIKLOSWAGNER) Wagner Development Solutions Certified Lead System Architect
Wagner Development Solutions
HU
Report

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. 
Posted: 2 years ago
Posted: 27 Feb 2020 1:32 EST
Masashi Tsuneizumi (tsunm) PEGA Senior Principal Sales Engineer
Pegasystems Inc.
JP
Report

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

 

Rochwyn Rodrigues Veera Kothakota
Posted: 2 years ago
Posted: 31 Mar 2020 0:58 EDT
Chiranjeevi Dupati (Chiranjeevi_Dupati) Coforge DPA Aus Pvt Ltd Consultant-Technology
Coforge DPA Aus Pvt Ltd
AU
Report

work-around - 

Private Edit activity pzStartTracerSession in class Data-TRACERSettings, Delete steps 2 to 6, Save rule

Alexey Kornilov Sundari R Allan Brooks Nalina Ravibiruthoji Abener Ochoa and 1 More
Posted: 2 years ago
Posted: 25 Apr 2020 16:09 EDT
Rimjhim Srivastava (srivr1) Pegasystems Inc. Senior Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Hi,

Try using another browser apart from chrome.

There seems an issue with the chrome browser.
Posted: 2 years ago
Updated: 2 years ago
Posted: 6 Aug 2020 15:26 EDT
Updated: 6 Aug 2020 15:27 EDT
Sudheer Nimmagadda (Sudheer Nimmagadda) Highmark Health Sr Application Developer
Highmark Health
Report

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.

 

Allan Brooks

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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