Question
AI4Process Ltd
GB
Last activity: 17 Aug 2017 5:06 EDT
Creating a unit test suite fails,it throws HTTP 403 error
Creating a unit test suite fails,it throws HTTP 403 error in 7.1.9.If anybody is aware of the issue,please let me know how to resolve the same.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Virtusa
AU
Hi,
Can you please share the complete exception stack trace and a screenshot of the error?
Regards,
Madhuri
Updated: 25 May 2017 9:21 EDT
AI4Process Ltd
GB
Hi Madhuri ,
When are trying to create a new Unit test suite by clicking on Create and Open button we are getting the error as shown in the screenshot below.We are not getting any stack trace error in the log.
Thanks,
Ronali
Virtusa
AU
hi Ronali,
This could be due some missing privilege. Did you check running the tracer when you click on the Create button? Can you please share it across?
Regards,
Madhuri
AI4Process Ltd
GB
As we are using PegaRules:AutoTest access role,it is taking care of required privilege.
Pegasystems Inc.
US
Can you run Fiddler to see the request being sent when the error occurs?
AI4Process Ltd
GB
In the Fiddler,we are sending below parameters in the Request:
pyActivity- @baseclass.pzTransformAndRun
pzPrimaryPageName-pyNewResults
action-display
harnessname-RuleFormLegacy
ClassName-Rule-AutoTest-Suite
pyPreActivity-doUIAction
-
phani deepika
Pegasystems Inc.
US
Do you have any pop-up blockers, firewall constraints, etc that would prevent the application from opening the content in a new window?
AI4Process Ltd
GB
Nothing has been written in to Tracer Stack while opening an instance of Test Case and getting the same error like Creating a unit test suite HTTP 403 error.PF below screenshots.
AI4Process Ltd
GB
Can anybody respond?
Pegasystems
US
That error is similar to the one you would get if you put a slash at the end of a url so that the server thinks you are trying to view a directory, when you are not authorized to view directories.
You mentioned 7.1.9. Are you saying that the exact same test worked fine in an earlier version of Pega?
I would think you could narrow down your issue with both the Pega tracer and fiddler (but not necessarily at the same time, unless you properly filter out the tracer events from fiddler).
Temporarily remove large pieces of your application until the error goes away, and then put half the last piece back in, so you can iteratively zero in on the issue.