Question3Replies50Views×Close popoverAkshay Sawai (AKSHAY) Cognizant Technology Solutions Lead System Architect Cognizant Technology Solutions CA View ProfileSend Message AKSHAY Member since 2012 15 posts Cognizant Technology Solutions Posted: October 24, 2019Last activity: October 30, 2019Posted: 24 Oct 2019 13:31 EDTLast activity: 30 Oct 2019 11:04 EDT Closed Solved Remote tracer from Requestor Management shows blank pageI am facing an issue with the remote tracer option available in Requestor management page. When a user clicks on the tracer option then it shows "Web page cannot be found error".Is there any configuration change cause this kind of issue? Its working fine with other applications in the same environment. Pega version 7.3Please provide inputs. Thanks. System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 1 year agoPosted: 25 Oct 2019 2:42 EDT×Close popoverMarc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer PEG FR View ProfileSend MessageMarcLasserre_GCS PEGA replied to AKSHAYHello, Do you have the same behaviour if you open the tracer normally and change the requestor from there? Posted: 1 year agoPosted: 28 Oct 2019 13:45 EDT×Close popoverAkshay Sawai (AKSHAY) Cognizant Technology Solutions Lead System Architect Cognizant Technology Solutions CA View ProfileSend MessageAKSHAY Cognizant Technology Solutions replied to MarcLasserre_GCSNo, It works fine with the above-mentioned change. Accepted Solution Posted: 1 year agoPosted: 30 Oct 2019 11:04 EDT×Close popoverAkshay Sawai (AKSHAY) Cognizant Technology Solutions Lead System Architect Cognizant Technology Solutions CA View ProfileSend MessageAKSHAY Cognizant Technology Solutions replied to AKSHAYThe problem identified and it was due to flaw in Tomcat 8 which restricts the Access Group code which has special characters. To fix this issue you need to add the below configuration in the server.xml file of your tomcat server, <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" relaxedQueryChars="[ ]" relaxedPathChars="[ ]" /> Restart server.