Telerik controls are not loading in container

1 Answer 117 Views
Top achievements
Rank 1
Chinnu asked on 20 Jul 2023, 01:33 PM

Hi Friends,

I'm trying to migrate ASP.NET web application (.NET 4.7.2) running on Windows server to ECS windows container but having following issues after hosting the image saying

1. 'Failed to load resource: the server responded with a status of 404()'  for WebResource.axd, ScriptResource.axd and Telerik.Web.UI.WebResource.axd.

2. Uncaught Error: ASP.NET Ajax client-side framework failed to load.

3. Uncaught ReferenceError: Sys is not defined at jsdebug

4. Uncaught ReferenceError: $get is not defined

Please someone help me in resolving these issues.

1 Answer, 1 is accepted

Sort by
Telerik team
answered on 25 Jul 2023, 07:56 AM

Hi Chinnu,

The errors you get show that your project is not configured to run ASP.NET Web Forms or something prevents the loading of the MS ASP.NET AJAX scripts. 

It seems like the issues you are facing after migrating your ASP.NET web application to ECS Windows containers are related to the loading of required resources and JavaScript libraries. These issues could be caused by various factors, so let's go through some troubleshooting steps to identify and resolve them:

404 Errors for WebResource.axd, ScriptResource.axd, and Telerik.Web.UI.WebResource.axd:

These files are generated by ASP.NET for handling resources such as JavaScript and CSS files. The 404 error indicates that the server cannot find these resources.

First, ensure that the required ASP.NET handlers are registered in the web.config file. Check that you have the following entries under <httpHandlers> and <handlers> sections in your web.config:

    <add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="true" />
    <add path="ScriptResource.axd" verb="GET" type="System.Web.Handlers.ScriptResourceHandler" validate="true" />

    <add name="ScriptResource.axd_GET" path="ScriptResource.axd" verb="GET" type="System.Web.Handlers.ScriptResourceHandler" preCondition="integratedMode" />

Uncaught Error: ASP.NET Ajax client-side framework failed to load:

This error suggests that the ASP.NET Ajax client-side libraries are not loaded correctly.


Uncaught ReferenceError: Sys is not defined at jsdebug:
This error indicates that the Sys object, which is part of the ASP.NET Ajax framework, is not defined.

  • Confirm that the ASP.NET Ajax client-side libraries are correctly loaded as mentioned in the previous step.
  • Check for any script errors or conflicts in your application that might prevent the Ajax libraries from loading properly.

Uncaught ReferenceError: $get is not defined:

The $get function is a part of the ASP.NET Ajax client-side library, and this error implies that the function is not available.

  • Ensure that the ASP.NET Ajax client-side libraries are correctly loaded.

Overall, these issues seem to be related to the correct setup and loading of ASP.NET resources and JavaScript libraries in your containerized environment. Double-check the configuration in your web application, verify that all necessary DLLs and resources are included in the container, and check for any script errors or conflicts.

If needed contact Amazon AWS support and ask them to help you configure your ASP.NET WebForms application to run on their system. In this article, you can also get information on how to Migrating .NET Classic Applications to Amazon ECS Using Windows Containers

Progress Telerik

Heads up! Telerik UI for ASP.NET AJAX versions for .NET 3.5 and 4.0 are retired. Progress will continue shipping assemblies compatible with .NET 4.5 and later. See whether this affects your apps in this article.
Asked by
Top achievements
Rank 1
Answers by
Telerik team
Share this question