This is a migrated thread and some comments may be shown as answers.

RadControls suddenly broken in IE9 only

1 Answer 38 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Marc Fearby
Top achievements
Rank 1
Marc Fearby asked on 28 Aug 2012, 03:46 AM
I have been working on an old system that uses "RadControls for ASP.NET AJAX Q3 2010 NET 40" where the controls are suddenly not working for IE9 only. The system works perfectly in Firefox and IE8, but in IE9 today (yesterday it was fine!) it suddenly won't work in any IE9 I can test it with. I've tried rebooting machines, clearing cache, rebooting web servers: it's only IE9. It's almost as if Microsoft have released an update that has wrecked it.

In the developer tools for IE9, it's saying this:

SCRIPT5022: ASP.NET Ajax client-side framework failed to load.
Default.aspx, line 90 character 34
SCRIPT5009: 'Sys' is undefined
Default.aspx, line 139 character 1
SCRIPT5009: 'Telerik' is undefined
Default.aspx, line 848 character 6
SCRIPT5009: 'Telerik' is undefined
Default.aspx, line 1145 character 1

But in Firefox, there's no whiff of there being any errors whatsoever and the thing works perfectly. Works fine in Chrome 17, as well.

What could be causing this sudden strangeness in IE9 only?

Thanks.

1 Answer, 1 is accepted

Sort by
0
Marc Fearby
Top achievements
Rank 1
answered on 29 Aug 2012, 03:08 AM
To cut a long story short, my corporate email account was migrated to a new server recently, and I've been added into some new AD groups, which has increased my request length to the (relatively new) web server in IE9. We had to add these two keys to the web server to increase the limit:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

Add these 2 Keys:

MaxfieldLength – REG DWORD – 65534 (0xffff)

MaxRequestBytes – REG DWORD – 65534 (0xffff)


IE9 (after installing Fiddler) revealed lots of 400 errors similar to this (as well as for WebResource.axd):

ScriptResource.axd?d=SgNRBvG7qnaG77B0krJ1ebi31QTAFk5Fq8G53mNNWzjoppyz5gzUeXujN8cW9zlTjRUNoKy3ckCXzoJxztRFIjvC0PERCuLPi-4rcRvFbk7oxWuySscjeq6iuKAgpcAnHaWLeTbDYVMbTAcyqynvPw2&t=6b9ad1b8

Firefox didn't have this problem, so I guess IE9 was adding to the request length just enough to trip up the application on our new IIS7.5 server, but Firefox wasn't. Strangely enough, Firefox (and Chrome) are now randomly not working with the application (Windows authentication) so I guess that's a problem to solve for another day. IE 9 is at least happy, now!

Oh, and by the way, the Developer Tools in IE9 suck! It didn't show ANY of those HTTP 400 errors at all. Thankfully I thought to install Fiddler. Why does Microsoft only ever make things 75% useful? Why can't they go to 100%????
Tags
General Discussions
Asked by
Marc Fearby
Top achievements
Rank 1
Answers by
Marc Fearby
Top achievements
Rank 1
Share this question
or