jscript error: "Invalid argument" in Telerik.Web.UI.WebResource.axd

[Tim]

This has me stumped.  It just started showing up one day.  We get a javascript error in some of the pages.  The error is in the WebResource.axd.  It seems to be referring to the html <col> fields related to the rad tree. It looks like it chokes on the columns with no width specified.
The really odd thing is that it works fine when it is launched from VStudio (debugging).  It errors on our dev server when we use the unqualified server name, but works when we use the fully-qualified name (http://server/page.aspx vs http://server.domain.com/page.aspx).  On production, it errors when we go through the load balancer, but not when we use the unqualified name or the non-load balanced name.  So, its hard to narrow-down the conditions.

Anyway, here is the javascript error message that we are getting:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8; .NET4.0C; .NET4.0E; .NET CLR 1.1.4322; InfoPath.3)
Timestamp: Mon, 17 Oct 2011 21:21:22 UTC

Message: Invalid argument.
Line: 14240
Char: 9
Code: 0
URI: http://servername/Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl00_radScriptManager_TSM&compress=1&_TSM_CombinedScripts_=%3b%3bAjaxControlToolkit%2c+Version%3d4.1.50508.0%2c+Culture%3dneutral%2c+PublicKeyToken%3d28f01b0e84b6d53e%3aen-US%3a0c8c847b-b611-49a7-8e75-2196aa6e72fa%3aea597d4b%3ab25378d2%3bTelerik.Web.UI%2c+Version%3d2011.2.915.40%2c+Culture%3dneutral%2c+PublicKeyToken%3d121fae78165ba3d4%3aen-US%3a9 ...etc
 

1. ASP.NET version is  .NET 4.0
2. OS  is Windows 2008 R2 x64 (server) and Windows 7 x64 (client)
3. exact browser version is IE 8.0.7600.*
4. exact version of the Telerik product is Telerik.Web.UI v 2011.2.915.40
5. preferred programming language is C#

[Veli]

Hi Tim,

The WebResource URL you are referring to points to a combined script URL. You seem to be using RadScriptManager and it combines script resources where possible to reduce the number of requests a page makes to the server. Try removing the RadScriptManager and substitute it with a standard ScriptManager control. Let us know what you are getting. If you are still getting exceptions, please, post the ex exception message and status code.

Web resources and HTTP  handlers in ASP.NET are an often problematic aspect when working in load-balanced environments. Particularly, web resources requested through HTTP handlers most often contain a resource key in the URL to identify the requested resource. This resource key is encrypted and encryption depends on the machine key that is used by the application. In load-balanced environments, you need to ensure that every node uses the same machine key. Here is an external article on this issue:

rosshawkins.net: Troubleshooting WebResource.axd


Veli
the Telerik team

[Vikram]

I am facing the similar issue. As suggested I have replaced the RadScriptManager with the regular asp control ScriptManager, but now I get a different error. This is specific to IE and does not happen in Mozilla Firefox or Chrome.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8)
Timestamp: Fri, 28 Sep 2012 21:00:47 UTC


Message: Invalid argument.
Line: 273
Char: 1
Code: 0
URI: http://localhost:41080/pagename/ScriptResource.axd?d=wMh-fC192bwNKV1clMA_hYIOfXc5cJQVTfKDSOqnFenPz0ljlblgfnbA9EcIwkUxQvXHb-NkIkGr8LQbur17TLypDXvqgTzjt-JkAc1K_gU5M8hckSFdYnzjmAS4YAupKc25wUNiMC8ATgyFdl0pVnGgV3DxsJ0uoP0zBUucHS41&t=65104505

[Galin]

Hello Vikram,

Could you please send us a sample project where the issue can be observed? This we will be able to test it locally and provide a proper solution.

Regards,
Galin
the Telerik team

[Sam]

Has this issue been resolved?

thanks,
Sam

[Galin]

Hello Sam,

I am not quite sure what is the exact problem you are facing. Therefore, I suggest that you send us more information about your issue or possible a sample runnable version of your project , so we can debug it locally and find out what causes the issue in your scenario and address it respectively.

All the best,
Galin
the Telerik team

[Sam]

Galin,

As I researched the problem a little more, I found that that issue is regarding the FormDecorator. It’s causing a Java error and freezing the pages. The issue was very unpredictable because when we did QA on the new DLLs we did not encounter any issues, but we our clients did (of course). We immediately asked them to upgrade their Java package, and crazy enough, it solved the issue for some of the users, but not all of them. When we take the Decorator out of the pages, everything works great, but of course we cannot really do that because of the way the pages are designed. So we had to rollback the Telerik upgrade. I would imagine you are aware of the issue and working on it – please confirm.

Thanks,
-Sam

[Galin]

Hello Sam,

I guess you mean there is a JavaScript error in the page and it is related to the RadFormDecorator.

In this case, this is a already known problem and it is resolved in the latest internal build. Could you try to upgrade and let me know how it goes?

Otherwise, please send a sample runnable project, which we can use to debug the error locally.


Greetings,
Galin
the Telerik team

[Cindy]

I downloaded 2012.3.1113_Dev_hotfix and this fixed my error.  I was having both problems below.  Make sure to turn CDN off when you download the internal build.

RadFormDecorator

What's fixed

• FIX decorated <select> tags in a div with 100% height renders with an extra space underneath, i.e. a double scroll occurs.
• FIX RadFormDecorator throws a JavaScript error under old IE versions when EnableRoundedCorners=true and a RadDatePicker is present on the page

[Chuck]

Just to add to this, after upgrading to 2012.3.1016.35, my RadDatePicker is no longer displaying (it is completely invisible) inside a RadPageView (inside a RadMultiPage) in IE7 & IE8.  It works as expected in other browsers and IE9.

The RadPageView with the RadDatePicker is not selected at first, but when it is selected an invalid argument error is thrown.  It is then selected, but the RadDatePicker is not visible. Changing EnableRoundedCorners to false does not fix it.  Completely removing the RadFormDecorator does fix the issue.

[Bozhidar]

Hi Charles,

I have tested your scenario, setting EnableRoundedCorners RadFormDecorator property to false, and it works as expected in IE7 and IE8. I have prepared a short video showing my test with IE7: http://screencast.com/t/DqDNxs7nYWfs.

This is the test code:

<body>
    <form id="form1" runat="server">
    <telerik:RadScriptManager ID="RadScriptManager1" runat="server">
    </telerik:RadScriptManager>
    <telerik:RadFormDecorator ID="rfd1" runat="server" DecoratedControls="All" EnableRoundedCorners="false" />
    <telerik:RadTabStrip ID="RadTabStrip1" runat="server" MultiPageID="MultiPage1">
        <Tabs>
            <telerik:RadTab Text="Tab1" PageViewID="PageView1">
            </telerik:RadTab>
            <telerik:RadTab Text="Tab2" PageViewID="PageView2">
            </telerik:RadTab>
        </Tabs>
    </telerik:RadTabStrip>
    <telerik:RadMultiPage ID="MultiPage1" runat="server">
        <telerik:RadPageView ID="PageView1" runat="server" Selected="true">
        </telerik:RadPageView>
        <telerik:RadPageView ID="RadPageView2" runat="server">
            <telerik:RadDatePicker ID="RadDatePicker1" runat="server">
            </telerik:RadDatePicker>
        </telerik:RadPageView>
    </telerik:RadMultiPage>
    </form>
</body>

You could see that when the property is set to false, everything works fine, and when it is not, it throws a JS error.  Hope that will be useful. If you need further help, open a support ticket and send us a simple sample project with the existing issue, so we would be able to test it further.

All the best,
Bozhidar
the Telerik team

[Chuck]

Thank you.  I actually had a more complex scenario, and wrongly assumed this was the cause.