RadScriptManager

[Trait]

I have various applications running on windows server 2008 and IIS 7 (.net 4.0 and 4.5). For some reason any application using the RadScriptManager is now throwing a 404 error on all .axd files and a "sys is not defined" error. The strange thing is that if I switch the the asp:scriptmanager these applications work correctly. Is there a setting on the server or in IIS that could cause this behavior? I am using version 2012.2.912.40 and 2013.3.1015.45 and they are both exhibiting the same behavior.

[Marin Bratanov]

Hi Steve,

Ensure you have the needed HTTP handlers in the web.config: http://docs.telerik.com/devtools/aspnet-ajax/general-information/web-config-settings-overview#mandatory-additions-to-the-webconfig.

RadScriptManager fetches the resources through the Telerik.Web.UI.WebResource.axd handler, while the standard script manager uses the built-in ScriptResource.axd handler.

Also, ensure that all users have access to those handlers by adding a <location> element to explicitly allow it, especially if you are using some form of authentication: http://docs.telerik.com/devtools/aspnet-ajax/general-information/troubleshooting/general-troubleshooting#using-the-telerik-controls-with-radscriptmanager-on-your-login-page-throws-an-error.

Regards,

Marin Bratanov
Telerik

[Trait]

i have tried all of the available fixes. Im actually getting the same error with a DNN installation that is configured correctly by default. are there any server or iis settings that could cause this?

[Marin Bratanov]

Hi Steve,

Assuming that all handlers are in place, I am not aware of any reasons for such behavior. If the standard ScriptManager can serve WebResources, then the needed IIS modules are installed.

That being said, my best advice at this point is to compare the IIS settings, Application Pool settings and IIS features on the machine where it does not work with those of the machine where things work as expected in order to identify the reason for the problem.

Regards,

Marin Bratanov
Telerik

[Trait]

I have compared IIS and the app pools and can't find any discernible difference. Are you aware of anything in the registry that could cause this behavior or maybe something to do with the version of system.web.extensions that exists on the server? The odd thing is that it started happening for all of my sites no matter what version of the controls I was using while these were working before. Like I said, I don't think it's a handler issue because the standard scriptmanager seems to work correctly.

[Marin Bratanov]

Hello,

I am not aware of reasons for such behavior, especially if the standard ScriptManager works as expected.

What I can suggest at this point is the following:

• make sure you are using the latest version of the controls (Q3 2015 at the time of writing)
• ensure the site runs in Full Trust mode on the production server
• if this happens only for a certain browser - reset it because there may be something wrong with the browser. We recently had a similar problem on a virtual machine where an IE started throwing "Sys is undefined" in all cases, regardless of the used script manager and even without any of our controls, even though all requests returned successfully. We could not find the cause, but restoring the VM to an earlier version helped.
• simplify the scenario as much as possible in case something else is affecting the situation (e.g., external script folder being added for combination). This blog post can help with that: http://www.telerik.com/blogs/isolating-a-problem-in-a-sample-project.
  • if you have a small sample that can showcase the problem on our end, please open a support ticket and send it to us so we can investigate
• fall back to the asp:ScriptManager control since it seems to work for your setup

Regards,

Marin Bratanov
Telerik