Javascript errors being thrown in IE10 after upgrading controls

[Michael]

Hello,

We've recently upgraded our Telerik asp.NET controls to v2014.1.403.40

We noticed that when browsing our pages in IE10 many different javascript errors are being thrown. Such as "Error: Unable to get property 'PageRequestManager' of undefined or null reference" We've done testing with IE11 and IE10 in compatibility mode and both are working properly. This problem is also affecting our screen layouts.

Let me know if you need more information to investigate this problem.
Thanks.

[Danail Vasilev]

Hi Michael,

I can suggest that you examine thoroughly the following blog posts that shed more light on the matter:

   - JavaScript errors in IE10 and the site is working fine in the rest browsers.
   - How to get your ASP.NET application working in IE11


Regards,
Danail Vasilev
Telerik

 

 

[Michael]

Hello Danail,

As I mentioned in my previous post the pages are rendering correctly in IE11 and I'm not getting the Javascript errors.
This is only an issue with IE10.

Also it only started happening when we recently upgraded our controls.

[Danail Vasilev]

Hi Michael,

Did you examine the JavaScript errors in IE10 and the site is working fine in the rest browsers. forum post I have provided earlier?

Said shortly:

If you receive "Unable to get property 'PageRequestManager' of undefined or null reference" error only on IE10, and your site is working in other browser, it is most probably that the MicrosoftAjaxWebForms.js fails to be included in the scripts for your page. This is known to be caused by bug in the browser definition files in .NET 4.0 and .NET 2.0 used by the ASP.NET.

In order to fix that you can use the corresponding hot fix as follows:

For .NET 4.0 check this one: http://support.microsoft.com/kb/2600088
For .NET 2.0:
http://support.microsoft.com/kb/2600100 for Win7 SP1/Windows Server 2008 R2 SP1, Windows Vista/Server 2008, Windows XP/Server 2003
http://support.microsoft.com/kb/2608565 for Win7/Windows Server 2008 R2 RTM

If, however, you are still having issues on this regard it would be better to open a support ticket and provide us with a small runnable VS example that reproduces the issue, so that we can make an investigation locally.

Regards,
Danail Vasilev
Telerik

 

 

[Michael]

Hello,

It seems that we had implemented a workaround on this server for the IE11 issue.
The issue that we were seeing in IE10 is exactly the way you described it.

Thanks for the prompt replies.