When attempting to run an application that uses certain Telerik controls, you may run into the error below:

 System.InvalidOperationException: ‘~/Telerik.Web.UI.WebResource.axd’ is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. Please, use the control Smart Tag to add the handler automatically, or see the help for more information: Controls > RadStyleSheetManager at Telerik.Web.UI.RadStyleSheetManager.OnPreRender(EventArgs e) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

I’ve seen that error on new DotNetNuke installations but it certainly isn’t specific to DNN, nor is it a problem with the Telerik controls. The issue is that the Integrated Pipeline Mode and Classic Modes handle the registration slightly differently within the web.config file

To resolve this error you can make changes to your web.config file, or, a perhaps faster and easier solution, is to change your site’s ASP.NET version to Classic Mode – both seem to work equally well.

Happy Hosting!


Be Sociable, Share!
    Resolving the error: ~/Telerik.Web.UI.WebResource.axd is missing in web.config.
    Tagged on:                     

    7 thoughts on “Resolving the error: ~/Telerik.Web.UI.WebResource.axd is missing in web.config.

    • February 3, 2012 at 10:57 am

      “Appreciate you sharing, great blog.Thanks Again.”

    • February 20, 2012 at 5:17 am

      Thanks for sharing this report and resources its really help full for me.

    • February 28, 2012 at 4:27 pm

      I been reading a bunch of articles and this is the most interesting post I have seen all week. Thanks for this!

    • May 4, 2012 at 1:21 am

      Thank you for your great posting!!
      You save my life!!

    • October 17, 2012 at 4:10 am

      Thanks, ur post solve my problem

    • April 19, 2013 at 12:46 pm

      U save my life… I was getting nuts with that…
      Thank You.

    • August 14, 2013 at 8:55 am

      In our case it was runtimeVersionv2.0 in the handlers section of the web.config

    Comments are closed.