"Access is denied" JS error

[Adam]

We are using Telerik 2008 Q3. We have a page that is almost entirely inside of a RadAjaxPanel and we are using a RadScriptManager and RadStyleSheetManager in the master page.

For some reason, and this doesn't happen for everyone, when they load up the page and click on something inside of the RadAjaxPanel, they get an immediate "Access is Denied" javascript error.

I ran debugging on it and found that it is this line

g=e.screenLeft-top.screenLeft-top.document.documentElement.scrollLeft+2

which was in the MicrosoftAjax.js file.

I don't entirely understand what is causing this. I don't get it on my local machine or even on our test server, but I can replicate it using a PC with a fresh install of Windows XP with SP2 and IE6 against our production environment. I've found items from Microsoft suggesting that it is because of an iframe and they suggest hacking the framework to get fixed. However, we don't have any iframe on this page, and I was unable to find any when viewing the source.

Thanks,

Adam

[Adam]

Here is a bit more information that I've uncovered after running it through Fiddler. I was finally able to get the JS error from my Vista PC against our production environment, and I believe it will only break on our production environment because we are using SSL there. When the user is browsing the site they are not in SSL, until they get to the page with the error. At that point, the first time the page loads, it checks to see if it should be HTTPS and whether or not is is, and if it isn't, it redirects itself to an HTTPS version of itself. That alone doesn't cause the error, but as soon as you click something on the page, like inside of a textbox to edit the value, the JS error pops up.

[Sebastian]

Hello Adam,

I think that the information from the blog post linked below will help you bypass this unsupported scenario by the ASP.NET AJAX framework:
http://weblogs.asp.net/bleroy/archive/2007/01/31/how-to-work-around-the-quot-access-denied-quot-cross-domain-frame-issue-in-asp-net-ajax-1-0.aspx

The last updated in it indicates that the problem is fixed in the ASP.NET 3.5 version of the framework and no workaround is required there.

Best regards,
Sebastian
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Adam]

I had seen that article as well as others, but didn't really want to start hacking the framework libraries. I was curious if it was fixed in 3.5, as that is an option for us to upgrade, but we just haven't had a reason to yet. Perhaps this is it.