Custom add-on installation fails with access denied to add-on dll in modulesbin



I seem to have persistent problem in our test and prod environment. We have custom add-on created by customer and now they are unable to install new version or remove existing one because of access denied error from the add-on dll in modulesbin. Why? What is blocking the file or what special access rights should I set to files? I've tried adding full control to user running the app_pool and also for IUSR in a desperate moment.

Any idea?

Mar 05, 2014 13:53

Damn and now I found the reason: I had added the name of custom add-on to compilation/assemblies to tackle another problem we had with the add-on and that one line in web.config caused access denied. application pool process blocking dlls in assemblies or what?

Now I feel stupid - again. 

Mar 05, 2014 13:57
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.