Serious IIS Application Pool recycling bug/design flaw

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
5 years ago
I agree, bleeding edge is what is says, get your bandages out. I went from 3.2 to 3.9 without any issues on my sites and then decided one site will be the bleeding test, yeah same issue as everyone is having, still no solution. Going back to 3.9..
5 years ago
bayden10 wrote:
I agree, bleeding edge is what is says, get your bandages out. I went from 3.2 to 3.9 without any issues on my sites and then decided one site will be the bleeding test, yeah same issue as everyone is having, still no solution. Going back to 3.9..


I just cant believe they are ignoring the issue.
5 years ago
Zyje_sobie wrote:
yeap, we have same problem. We use solution from this topic, but today we have holiday i try to rest, and clients sends PM and asking us "what's going on, page don't working"...

I check logs... and 5 hours page was been down...

It's so weak... we waited a half year to take stable nop 4.0... and... have something like this... In nop 3.7 we have 0 problems... i'm so disapointed... we need write script today, and application will be restarted all time when server generate 500 error... but... is this a really solution? Well...  maybe 4.1 will solve this... but what certainty this has no to a generate new bugs like this...


I'm not sure which solution you used, but this will fix it. It just removes the shadow copy code altogether.


timmit wrote:

Download Nop 4.0 source
Replace PluginManager.cs code with this - https://pastebin.com/RABL78sb
Build in release mode
Copy Nop.Core.dll to all affected websites
Delete the Plugins/bin folder (where the shadow copy dlls used to preside)

Won't take you more than 30 minutes. Nop Team don't give a shit, there's no patch coming.

I've been using this fix in production for a very long time without issue.
5 years ago
Hi there! Any news?
5 years ago
Hi everyone, we fixed this issue in nopCommerce 4.10, but our development process does't support making changes in already released versions of the product, so we ask you to look at this commit and make them in your code yourself.
5 years ago
Nop-Templates.com wrote:
Hello,

I don't think this issue is resolved with the fix provided here.
Our demo stores are having the same issues. From 32 stores roughly 1 or 2 crash every day with the same error - no access to a .dll when trying delete/create shadow copies. If we set the Disable Overlapped Recycle setting in IIS to true we stop having this issue. That is not a fix to this issue but rather a workaround due to the disadvantages it brings.
Moreover, our clients that use Azure do not have this option as far as I am aware and they are left with no choice at the moment and this is a very big problem for them. We have numerous people writing tickets to us about this issue and none of the fixes we've implemented have lead to any success so far.

Can you take a look at this problem again?

Regards,
Anton


Hi Sergei-k
Is the fix production ready? As I can see Nop-Templates.com had some doubts about the fix.
5 years ago
s.isupov wrote:
Hello,

Hi Sergei-k
Is the fix production ready? As I can see Nop-Templates.com had some doubts about the fix.


If you implement these changes and disable the shadow copy mechanism it will work well.
5 years ago
Sergei-k wrote:
Hello,

Hi Sergei-k
Is the fix production ready? As I can see Nop-Templates.com had some doubts about the fix.

If you implement these changes and disable the shadow copy mechanism it will work well.


Ok, thanks a lot!
5 years ago
We had this issue after reinstalling our modules.  The first installation was fine, but the Plugin/bin folder kept hanging on to the old module dll after we reinstalled a newer version for upgrade.  The quick fix was to just push your Plugin dll into the root bin folder.  It will then use this dll instead of the shadow copy version or the Plugin/Module version and eventually it will copy it as the shadow copy (Plugins/bin) then you can remove the Plugin dll from the root if needed.  Hope this help someone.
5 years ago
I was having the issues as discussed here,
"Application startup exception: System.Exception: Plugin 'Seven Spikes Core'. Access to the path..."

My fix,
1. Go to IIS, Application Pool, add a pool called "No Managed Code" and select No Managed Code
2. Add an Web Application as normal, set application pool to "No Managed Code"
3. Directory browsing enabled
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.