An error occurred while starting the application

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
5 years ago
Zyje_sobie wrote:

Yes... basically the root cause is that for some unknown reason, file permissions are ignored (at random) when copying the dll's from the plugins director to the bin directory.  It doesn't seem to have anything to do with unsafe vs. safe dll's, etc.

In all our 4.0 and 4.1 deployments, we suppress the shadow copy. Anytime we need to put a plugin update in now, we copy the dlls both to the plugin and the plugin/bin folder and we have just removed all the shadow copy code.

Looking back at this issue, I don't even think it's a nopCommerce problem given that the failure occurs using the System.IO namespace. (eg. for 4.0 installations it fails in PluginManager when trying to delete the current file - File.Delete(shadowCopiedPlug.FullName); on a application pool reset.  Given that, it feels like this is more of a .net / OS type error - not nopCommerce.  

The average failure rate before we made changes was measured to be about 20%. So on a normal IIS application pool recycle, there is an 80% chance the line will not fail, but of course when the 20% chance comes up, only a manual app pool recycle brings the site back from its 500 state.

I am curious if anyone is seeing this in Win 2016 IIS / IIS 10 environment.
5 years ago
hezyz wrote:
it can be everything

go to web.config change stdoutLogEnabled to true

and check the log file for the specific error

1. make sure the \logs\stdout exist, if not create it
2. make sure there are read and write permissions

p.s.
I had to restart the server for the log file to generate


it's helpful and saved me, thank you!
4 years ago
In my case I was trying to deploy on a shared hosting. My application was published on 32 bit server was running 64bit pool by default. So i contacted the server guys and told them the whole story. It was a quick fix on there end and application starting running.

Hope it helps someone.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.