New to Telerik UI for ASP.NET AJAXStart a free 30-day trial

Server Error (500) Occurs

Environment

ProductProgress® Telerik® UI for ASP.NET AJAX

Description

When working with Telerik UI for ASP.NET AJAX, I get a 500 server error code.

Solution

Depending on the use case, use any of the following approaches to solve this issue:

  • (Padding is invalid and cannot be removed)

    This issue is likely to be related with the machine key. To create a custom machine key, refer to this MSDN article.

  • (Specified argument was out of the range of valid values. Parameter name: utcDate)

    The latest modified time of the assembly containing the embedded resources is probably later than the time this issue occurred, or you are deploying in a different time zone. To solve this issue, run the following command line statement: copy /b <path to assembly which is built in the future>+,,.

  • (RadAsyncUpload throws HTTP 500 with a red dot beside the uploaded file name

    To solve this issue, make sure that the Telerik.Web.UI.WebResource.axd handler is registered in the web.config file.

  • (Telerik.Web.UI.WebResource.axd 500 (Internal Server Error)

    This error might be due to a missing or incorrect stylesheet WebResource file. To solve the problem, upgrade to the latest available version of the product. You can also set the value of the RenderMode property to Lightweight or Classic to see whether it will help.

    It is recommended to report such errors in the feedback portal, the ticketing system, or the forum so that the team can verify and fix them.

  • (Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500)

    Usually, such an error is thrown when multiple or nested AJAX requests are initiated at the same time or when a server error is thrown during an AJAX update. To solve this issue, temporarily disable AJAX on the page to see what the actual error thrown on the page is. Then, debug its cause.

    Also, make sure that the handlers are properly registered inside the <httpHandlers> and <handlers> section of the web.config file as explained in the article on mandatory additions to the web.config.

    To identify more causes for the occurring issue, refer to the following resources:

Another way to look for the cause of the problem is to remove the AJAX settings one by one unless you find the one leading to the error and, respectively, the controls which updatе is causing it.

In this article
EnvironmentDescriptionSolution
Not finding the help you need?
Contact Support