Comments on: The mysterious problem with WebResource.axd http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/ Chatter about EPiServer, ASP.NET, CSS and Web Development. Wed, 21 Dec 2011 01:21:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: hassan http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-4130 hassan Tue, 28 Dec 2010 21:34:15 +0000 http://blog.fredrikhaglund.se/?p=41#comment-4130 I had this problem and that reason was incompatibility between Coldfusion and some configurations of ASP.NET applications when IIS App pool is in integrated mode. Coldfusion must be disable . I had this problem and that reason was incompatibility between Coldfusion and some configurations of ASP.NET applications when IIS App pool is in integrated mode. Coldfusion must be disable .

]]> By: Duke http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-4063 Duke Tue, 31 Aug 2010 15:19:27 +0000 http://blog.fredrikhaglund.se/?p=41#comment-4063 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? The last one worked for us. 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?

The last one worked for us.

]]> By: Victor http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-3150 Victor Thu, 12 Feb 2009 15:27:34 +0000 http://blog.fredrikhaglund.se/?p=41#comment-3150 I found that some extensions for the web site were mapped to aspnet 1.1 isapi dll (aspnet_isapi.dll) even though the application is set to run on 2.0 in the ASP.NET tab. I changed the extension for .axd to run with v2.0... and my JavaScript worked right away. I found that some extensions for the web site were mapped to aspnet 1.1 isapi dll (aspnet_isapi.dll) even though the application is set to run on 2.0 in the ASP.NET tab. I changed the extension for .axd to run with v2.0… and my JavaScript worked right away.

]]> By: Dominik Juszczyk » Blog Archive » WebResource.axd problem in EPiServer CMS 5 http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-3100 Dominik Juszczyk » Blog Archive » WebResource.axd problem in EPiServer CMS 5 Sat, 13 Dec 2008 07:20:14 +0000 http://blog.fredrikhaglund.se/?p=41#comment-3100 [...] searching for this exception in Google I have found a post about this on Fredrik Haglund’s blog. We have had applied his patch and it seems to solve the [...] [...] searching for this exception in Google I have found a post about this on Fredrik Haglund’s blog. We have had applied his patch and it seems to solve the [...]

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2828 Fredrik Haglund Fri, 29 Aug 2008 19:52:00 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2828 UPDATE: http://blog.fredrikhaglund.se/blog/2008/08/26/solution-to-webresourceaxd-exception/ UPDATE: http://blog.fredrikhaglund.se/blog/2008/08/26/solution-to-webresourceaxd-exception/

]]> By: Calle http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2817 Calle Thu, 28 Aug 2008 12:02:36 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2817 Hi! Before you all use the fix. Check your IIS-settings: Under add "application extension mapping" for wildcard (.*). Make sure that "validate that file exists" is NOT checked. I unchecked it and solved the problem for me... Hi!
Before you all use the fix. Check your IIS-settings:
Under add “application extension mapping” for wildcard (.*). Make sure that “validate that file exists” is NOT checked.
I unchecked it and solved the problem for me…

]]> By: Solution to WebResource.axd exception | Fredrik Haglund's blog http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2796 Solution to WebResource.axd exception | Fredrik Haglund's blog Tue, 26 Aug 2008 16:02:38 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2796 [...] earlier hack in my blog post The mysterious problem with WebResource.axd is no longer needed since the cause is [...] [...] earlier hack in my blog post The mysterious problem with WebResource.axd is no longer needed since the cause is [...]

]]> By: Paul McEwan http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2744 Paul McEwan Wed, 21 May 2008 15:54:45 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2744 Fredrik, we're having this same problem, but the workaround doesn't seem to help. As soon as we put anything with AutoPostBack="True" or a validation control it errors. We assume because of client-side Javascript? Do you have any more information from MS on this issue? Thanks -- Paul Fredrik, we’re having this same problem, but the workaround doesn’t seem to help. As soon as we put anything with AutoPostBack=”True” or a validation control it errors. We assume because of client-side Javascript? Do you have any more information from MS on this issue?

Thanks

– Paul

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2741 Fredrik Haglund Thu, 15 May 2008 07:45:09 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2741 Per Bjurström at EPiServer found the cause of this issue. He has also a workaround that prevents it from happening. The code above only recovers the application after the error is detected. Per Bjurström at EPiServer found the cause of this issue. He has also a workaround that prevents it from happening.

The code above only recovers the application after the error is detected.

]]> By: Per Bjurström http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2739 Per Bjurström Wed, 14 May 2008 13:16:03 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2739 Please read this post: http://labs.episerver.com/en/blogs/per/Archive/2008/5/The-not-so-mysterious-problem-with-WebResourceaxd/ Please read this post:

http://labs.episerver.com/en/blogs/per/Archive/2008/5/The-not-so-mysterious-problem-with-WebResourceaxd/

]]> By: Jørgen Tonvang http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2716 Jørgen Tonvang Fri, 18 Apr 2008 09:09:14 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2716 We've experiencing ever since we started using EPi 5. It occurs very frequently on both production and development servers. We've never seen it on independent asp.net 2.0 sites or EPi 4.6. We have several developers working against the same dev. server for a new enterprise site, and I'd say that after a compile it has a 50/50 chance of triggering the error. All the top google results for this seems to be EPi related, so this is definetly something they should look into. /Jørgen We’ve experiencing ever since we started using EPi 5.
It occurs very frequently on both production and development servers. We’ve never seen it on independent asp.net 2.0 sites or EPi 4.6.

We have several developers working against the same dev. server for a new enterprise site, and I’d say that after a compile it has a 50/50 chance of triggering the error.

All the top google results for this seems to be EPi related, so this is definetly something they should look into.

/Jørgen

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2701 Fredrik Haglund Thu, 10 Apr 2008 15:14:38 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2701 <strong>Update:</strong> Scott Guthrie help me to get in contact with Steve Molloy and Matt Gibbs at Microsoft about this issue. Steve has been running this in the stress lab for a couple days. After several hundered machine-hours of stress while touching config every 3 minutes they have not been able to reproduce the issue. This is probably a race condition that occurs because the framwork or application we have does something special. But I have not been able to create a simple reproducable test case. Has anyone? I have identified several things that increases the probability to get this issue: * You have login controls or other controls that uses validation on your start page. (Validation needs javascript and <em>EnsureHandlerExistenceChecked </em>will called because Webresource.axd is used) * You have a lot of assembles in your bin folder. In my case, the framwork I use (EPiServer), has code that loads all assemblies in the bin folder in the constructor of the global.asax class. It does this because it looks for classes with plug-in attibute. This in combination with the call to <em>EnsureHandlerExistenceChecked </em> on the start page does probably increase the risk for the problem. /Fredrik Update: Scott Guthrie help me to get in contact with Steve Molloy and Matt Gibbs at Microsoft about this issue.

Steve has been running this in the stress lab for a couple days. After several hundered machine-hours of stress while touching config every 3 minutes they have not been able to reproduce the issue.

This is probably a race condition that occurs because the framwork or application we have does something special. But I have not been able to create a simple reproducable test case. Has anyone?

I have identified several things that increases the probability to get this issue:
* You have login controls or other controls that uses validation on your start page. (Validation needs javascript and EnsureHandlerExistenceChecked will called because Webresource.axd is used)
* You have a lot of assembles in your bin folder.

In my case, the framwork I use (EPiServer), has code that loads all assemblies in the bin folder in the constructor of the global.asax class. It does this because it looks for classes with plug-in attibute. This in combination with the call to EnsureHandlerExistenceChecked on the start page does probably increase the risk for the problem.

/Fredrik

]]> By: Mats http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2700 Mats Thu, 10 Apr 2008 07:57:15 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2700 Hi! We have the same problem with some of our EPiServer sites. Thank you for the workaround! /Mats Hi!
We have the same problem with some of our EPiServer sites. Thank you for the workaround!
/Mats

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2626 Fredrik Haglund Wed, 19 Mar 2008 16:50:01 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2626 Martin, that is correct. My guess is that this error is triggered by some sort of race condition during startup. This will only allow it to try again... /Fredrik Martin, that is correct. My guess is that this error is triggered by some sort of race condition during startup. This will only allow it to try again… /Fredrik

]]> By: Martin http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2625 Martin Wed, 19 Mar 2008 15:40:31 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2625 To clear things up: this workaround does not fix this problem, it does just allow the handlers to reload if the app pool has already crashed. So if you use this code, you will still get the error, but you do not have to reset the iis every time it happens. To clear things up: this workaround does not fix this problem, it does just allow the handlers to reload if the app pool has already crashed. So if you use this code, you will still get the error, but you do not have to reset the iis every time it happens.

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2167 Fredrik Haglund Fri, 01 Feb 2008 16:03:33 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2167 Note! The fix above applies for IIS6 only.<br/><br/>There are other <a href="http://forums.asp.net/p/1155043/2119518.aspx" rel="nofollow">issues with IIS7 that you can read about in the forums</a> Note! The fix above applies for IIS6 only.

There are other issues with IIS7 that you can read about in the forums

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2121 Fredrik Haglund Thu, 15 Nov 2007 16:34:44 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2121 Jon, it appears to work well for us. The site has not stopped working since we applied the fix. We still see the error from time to time after the appdomain reloads so the sollution is not perfrect. But now it does not stop permanently but recovers. I did not manage to figure out the root cause of the problem but it appears to affect larger asp.net applications with many assemblies in the bin folder with constant trafic more often. Pages without need for scrips do not get the error (since they do not user the webresource.axd handler) and we have a validation control on our start page so it is quite obvious when it is not working... /Fredrik Jon, it appears to work well for us. The site has not stopped working since we applied the fix.

We still see the error from time to time after the appdomain reloads so the sollution is not perfrect. But now it does not stop permanently but recovers.

I did not manage to figure out the root cause of the problem but it appears to affect larger asp.net applications with many assemblies in the bin folder with constant trafic more often. Pages without need for scrips do not get the error (since they do not user the webresource.axd handler) and we have a validation control on our start page so it is quite obvious when it is not working…

/Fredrik

]]> By: Jon http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2119 Jon Wed, 14 Nov 2007 20:59:19 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2119 I'm desparate for a solution/workaround and hope to try this next. Have you had any more experience with the overall success/risks of this method? I’m desparate for a solution/workaround and hope to try this next. Have you had any more experience with the overall success/risks of this method?

]]> By: Andreas Engström http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2114 Andreas Engström Mon, 05 Nov 2007 10:52:48 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2114 Hej Fredrik, vi har också lidit av detta problem (bland andra) finns lite att jobba på i nya releasen innan den är ok. Tack för din fix MVH A Engström /din elev :) Hej Fredrik, vi har också lidit av detta problem (bland andra) finns lite att jobba på i nya releasen innan den är ok.

Tack för din fix

MVH
A Engström /din elev :)

]]> By: Fredrik Haglund http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2112 Fredrik Haglund Tue, 23 Oct 2007 08:35:37 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2112 Hej Andreas! Download example code here: http://fredrikhaglund.se/blog/070927/Global.asax.zip /Fredrik Hej Andreas!

Download example code here: http://fredrikhaglund.se/blog/070927/Global.asax.zip

/Fredrik

]]> By: Andreas Ek, Internetfabriken http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2111 Andreas Ek, Internetfabriken Tue, 23 Oct 2007 05:57:15 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2111 Hello! Could you, please, publish the code as text? It would be a lot easier ;-) Hello!
Could you, please, publish the code as text? It would be a lot easier ;-)

]]> By: Jimmy http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2110 Jimmy Wed, 10 Oct 2007 07:02:40 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2110 Hi! I have experienced this problem two times this week only, and its very frustrating. But you don't need to restart the IIS to fix this. Just stop the web, recycle the application pool and start the web again. I will try your fix and hopefully it will work for me too. Thanks. /Jimmy Hi! I have experienced this problem two times this week only, and its very frustrating. But you don’t need to restart the IIS to fix this. Just stop the web, recycle the application pool and start the web again. I will try your fix and hopefully it will work for me too. Thanks. /Jimmy

]]> By: Marnix http://blog.fredrikhaglund.se/blog/2007/09/27/the-mysterious-problem-with-webresourceaxd/comment-page-1/#comment-2109 Marnix Mon, 01 Oct 2007 14:50:43 +0000 http://blog.fredrikhaglund.se/?p=41#comment-2109 Hi Fredrik, I have the same issue and I'm able to reproduce it by overwriting an assembly with embedded resources with a newer version. I'm guessing the problem occurs somewhere while reloading the assembly. Normally an update like this will trigger the AppDomain to be reloaded which would confirm your story. I've tried your code and so far it works like a charm :) Thanks, Marnix Hi Fredrik,

I have the same issue and I’m able to reproduce it by overwriting an assembly with embedded resources with a newer version. I’m guessing the problem occurs somewhere while reloading the assembly. Normally an update like this will trigger the AppDomain to be reloaded which would confirm your story.

I’ve tried your code and so far it works like a charm :)

Thanks,
Marnix

]]>