All geek questions in one place

Failed to load file or assembly <My compiled dll>, Culture = neutral, PublicKeyToken = null or one of its dependencies. Access denied

I know this was asked before, but the answer was a temporary hack.

We already have a website that runs on our servers in real time, and we just made some updates and deployed. Inside JIT works, and the site works. When the next application pool is updated, we get the following error from the web server (IIS6).

Failed to load file or assembly "OurBusinessObjectsAssemblyName, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = null or one of its dependencies. Access is denied.

As an answer to the previous question, the proposed reloading of the dll library in question causes a rebuild, and the site works again, but a subsequent reload of the application pool causes the same problem. What causes this? The web server works with many other sites, so I don’t think there is a problem with the permissions with asp.net temporary files and have already checked this, they seem fine.

+3
source share
3 answers

I had the same problem - this concerns the rights in the temporary ASP.NET folder (C: \ WINDOWS \ Microsoft.NET \ Framework \ v2.0.50727 \ Temporary ASP.NET Files) - make sure that the user is working, since your application has rights to create and modify files in this folder, and not just read rights.

+1

. . , ?

+1

I had the same problem. This was not permission for the temporary directory or the bin directory. It turned out to be my AV module, which included access protection. As soon as I disabled this and the registry entries were again made by the ASP.NET user, everything worked again.

0
source

Source: https://habr.com/ru/post/1711571/

More articles:


All Articles