Thread: WebResource.axd Handler Question

I'm trying to upgrade a site to ADNS 8 and I'm getting a error when trying to add items to the cart or viewing the admin. I'm using Windows Server 2008 and SQL 2008. Any idea what could cause this?

Thanks!

Error Details...

The WebResource.axd handler must be registered in the configuration to process this request.

Server Error in '/' Application.

The WebResource.axd handler must be registered in the configuration to process this request.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<httpHandlers>
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
</httpHandlers>
</system.web>
</configuration>

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The WebResource.axd handler must be registered in the configuration to process this request.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<httpHandlers>
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
</httpHandlers>
</system.web>
</configuration>

Source Error:


Line 454: }
Line 455: IterateControls(Controls);
Line 456: base.Render(writer);
Line 457: }
Line 458:

Source File: c:\Websites\westcoastcorvette.com\App_Code\SkinBas e.cs Line: 456

This error is thrown when ASP.NET cannot verify that WebResource.axd is mapped to the correct handler (AssemblyResourceLoader), when it's trying to retrieve resources from a DLL file.

This mapping is hardwired by default, but can be disrupted if wildcard ("*") HttpHandlers are added to web.config (either "system.web/httpHandlers" for Classic Mode or "system.webServer/handlers" for Integrated Mode). This error can also appear if the resource DLL has been altered without triggering a restart of IIS.

A few things to check:

• Does the issue go away with a recycle of the AppPool, or a restart of IIS?
• Have any additional handlers been added to the site? AJAX perhaps?
• Does the problem change if the AppPool is switched from Integrated Mode to Classic Mode?

Yes, when I switched to Classic mode, the problem went away. Are there any issues with switching to Classic mode?

Thanks for the help!

I'm glad you were able to get it working. I can't definitely state that Integrated Pipeline Mode is the root cause, because I run W2K8 with an Integrated Pipeline every day without seeing this issue. Without analyzing the loading order of all handlers found in machine.config and web.config, the root cause may never be known.

An Integrated Pipeline moves the ASP.NET runtime into the core web server, rather than using an ISAPI extension as in previous versions. On the surface, there aren't significant differences between the two approaches, so you aren't going to notice a difference.

Under the covers, there are implementation differences, and minor advantages to having ASP.NET integrated with IIS. But it's difficult for us to implement them into the product, until the vast majority of customers have access to an Integrated Pipeline.

THANK YOU!!!

Just ran into this issue with new install on IIS 7.

Thank you.