Site goes down with odd error occasionally?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
14 years ago
Hi there,

URGENT:- Does anyone know what this error is - our shop goes down about once every 2 days and we have just launched it - we get it for no reason we can find and we need to restart the website IIS to get it working again?



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:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[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>]
   System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrlInternal(Assembly assembly, String resourceName, Boolean htmlEncoded) +8551998
   System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrl(Type type, String resourceName, Boolean htmlEncoded) +296
   System.Web.UI.ClientScriptManager.GetWebResourceUrl(Page owner, Type type, String resourceName, Boolean htmlEncoded) +82
   System.Web.UI.ClientScriptManager.RenderWebFormsScript(HtmlTextWriter writer) +58
   System.Web.UI.Page.RenderWebFormsScript(HtmlTextWriter writer) +26
   System.Web.UI.Page.BeginFormRender(HtmlTextWriter writer, String formUniqueID) +387
   System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +54
   System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +32
   System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output) +51
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +99
   System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +40
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +134
   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +19
   System.Web.UI.Control.Render(HtmlTextWriter writer) +10
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +99
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +134
   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +19
   System.Web.UI.Control.Render(HtmlTextWriter writer) +10
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +99
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +134
   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +19
   System.Web.UI.Page.Render(HtmlTextWriter writer) +29
   NopSolutions.NopCommerce.Web.BaseNopPage.Render(HtmlTextWriter writer) in D:\anoop programs\NewProject\nopCommerce_1.40\NopCommerceStore\Controls\BaseNopPage.cs:148
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +99
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1266

________________________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016



13 years ago
Did you find a solution to this error? It's driving me mad.

Thanks...
13 years ago
I had the same error crop up when I updated my 1.6 nopcommerce to 1.8. After searching high and low for an answer I found that it has to do with having ColdFusion installed on the same server as your .net 4. Microsoft apparently is aware of the problem and is supposedly working on a patch but you can find details on this ASP.Net forum - http://forums.asp.net/t/1155043.aspx

Now if you are not running ColdFusion server on your same server then this may not be your issue. And if you are in a hosted environment you may need to contact your host for help because you need access to IIS Admin to fix the problem.

Essentially you need to NOT have your asp.net 4.0 apps running on the same application pool as your cold fusion application pool. ColdFusion adds a wildcard (*) handler in the Handler mappings of your website and that throws off DotNet to throw this error. So you need to first create a separate application pool for your dotnet apps (separate from the application pool coldfusion is using (usually the default app pool) remove the * handler in the handler mappings of the DotNet application pool you assign to you nopcommerce website.

Below I quote from the forum link I gave earlier-

Since it's not really the best practice to combine a ColdFusion and DotNet application in one app pool, I moved the DotNet web application into a separate application in the same web site which allows me to assign it it's own application pool. Now I can remove the ColdFusion http handlers for this application (just remove them in the administrative tool for the application) which in fact will create "remove" entries for these mappers in the Web.config. That way the DotNet web application is running "clean" without interferance from the Cold Fusion mappings AND Cold Fusion can also run in integrated mode in it's own application pool with no interference.


I hope that is helpful
cheers
13 years ago
Victorialewis - wondering if you were able to find a solution to this problem (other than the above post).

After getting my shop set up officially it was running fine for about 2 - 3 weeks and is now experiencing the same issue with both the shop and admin section going down... Then mysteriously “fixing” itself. Then happening again the next day, or couple of days....
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.