Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Not Embedding a pega search screen via IAC in dotnet portal.



Not loading the pega search screen when Dotnet portal uses an iframe tag to load pega search screen via IAC. In a HTML file the iframe tag holds the url to connect pega portal via IAC. This functionality is not working in Production only. It renders a blank screen and the chrome browser displays the below errors

Error Messages

1. First time it appears as blank screen. but when we try to use Inspect element, the below error appears

Uncaught SecurityError: Blocked a frame with origin "XXXXXX" from accessing a frame with origin "XXXXXX". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match.

2. when we again click on the button for second time from dotnet portal . the below error appears in the Inspect elements.

Uncaught TypeError: Cannot read property 'd' of undefined(anonymous function) @ $STANDARD?pyActivity=%40baseclass.doUIAction&action=display&harnessName=IACHarness&className=Data-P…:1
$STANDARD?pyActivity=%40baseclass.doUIAction&action=display&harnessName=IACHarness&className=Data-P…:1 Uncaught TypeError: Cannot read property 'd' of undefined(anonymous function) @ $STANDARD?pyActivity=%40baseclass.doUIAction&action=display&harnessName=IACHarness&className=Data-P…:1
$STANDARD?pyActivity=%40baseclass.doUIAction&action=display&harnessName=IACHarness&className=Data-P…:1 Uncaught ReferenceError: checkContainersExpanded is not definedonload @ $STANDARD?pyActivity=%40baseclass.doUIAction&action=display&harnessName=IACHarness&className=Data-P…:1

3. When we keep on submitting the button, we get the below issue.

PRGateway Exception: error response from PRPC

Steps to Reproduce

1. copy paste the iframe tag in file.html
2. run the html file from chrome browser.

Root Cause

A third-party product issue the host name was restricted by user's load balancer, hence couldn't be able to process the URL to render the content of HTML file


User has to allow the hostname to access via load balancer, and
User need to check the gadget and prgateway are deployed on the same domain.


Published February 27, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us