We are having an issue deploying to our user acceptance test and production environments, the telerik webresource.axd file is getting a 404 there, causing the infamous 'Sys' is undefined error I presume. The application works fine on the programmers development web server. The developers app pool is set up as Framework 4.0 Integrated pipeline Windows 7, the test and production environments we deploy to are also set up as Framework 4.0 Integrated pipeline, Windows 2008. We have had our server admin verify that the axd handler mappings are enabled. Additionally I have read all the threads concerning this error and have tried everything, to no avail. Pasted below are the system.web and system.webserver sections of our config file, we have included the telerik webresource axd handler, and it is recognized because if we remove it we get a telerik exception to go add it. The crux of the problem appers to be why we are getting a 404 on this axd. The site is accessed via IBM TAM (Tivoli Access Manager) in the deployment environments, if that makes any difference. Our telerik menus remder however they dont fly out due to not having their axd resources, I presume, so it appears like the telerik dll is getting loaded, telerik tags are recognized. We are deploying the telerik dll's in the /bin (not the GAC). Also pated below is the fiddler log of our default.aspx page loading, note the telerik axd file gets 404.
I tried a small experiment, I created a dummy test.axd text file and browset it from my development machine IIS, I got a 404.17 error "The requested content appears to be script and will not be served by the static file handler".
Then I copied the same file to our deployment server site root and browsed it. Instead of getting a 404.17 error I got a flat out 404 error saying that the resource could not be found.
There is definitly a diference in how the developer box and the deployment boxes are configured, does anyone have an idea.
We are desperate, and fully licensed for this product, we have a user community of 80,000 people waiting for us to deploy this release. So far the only thing holding it back is this problem. I would appreciate any help, we've exhausted everything we could find.
I tried a small experiment, I created a dummy test.axd text file and browset it from my development machine IIS, I got a 404.17 error "The requested content appears to be script and will not be served by the static file handler".
Then I copied the same file to our deployment server site root and browsed it. Instead of getting a 404.17 error I got a flat out 404 error saying that the resource could not be found.
There is definitly a diference in how the developer box and the deployment boxes are configured, does anyone have an idea.
We are desperate, and fully licensed for this product, we have a user community of 80,000 people waiting for us to deploy this release. So far the only thing holding it back is this problem. I would appreciate any help, we've exhausted everything we could find.
1 Answer, 1 is accepted
0
Hi Richard,
We have already answered to this query in the support threads, however, I will paste the answer here for a community reference:
Looking at your web.config I can see that there are multiple handlers (for example:
that have *.axd set in their path attribute. Please note that all such handler must be placed at the end of the web.config otherwise they are going to intercept all requests for other axd handlers, which includes
In order to solve the problem please structure your web.config in a way that the specialized handlers, such as Telerik.Web.UI.WebResource.axd, are placed in the beginning of the web.config whereas the more generic ones, which accept path at *.axd are placed at the end.
Kind regards,
Genady Sergeev
the Telerik team
We have already answered to this query in the support threads, however, I will paste the answer here for a community reference:
Looking at your web.config I can see that there are multiple handlers (for example:
ASPNET-ISAPI-1.1-AXD)that have *.axd set in their path attribute. Please note that all such handler must be placed at the end of the web.config otherwise they are going to intercept all requests for other axd handlers, which includes
Telerik.Web.UI.WebResource.axd. And this is exactly what is going on, the more general *.axd handlers intercept the requests for Telerik.Web.UI.WebResource, however, they are unable to serve the requested scripts hence the errors.In order to solve the problem please structure your web.config in a way that the specialized handlers, such as Telerik.Web.UI.WebResource.axd, are placed in the beginning of the web.config whereas the more generic ones, which accept path at *.axd are placed at the end.
Kind regards,
Genady Sergeev
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.