I am stuck with one asp.net error. My application work fine on development and test environemnt. But on production it give me following error:
Could not load file or assembly 'someProject' or one of its dependencies. Access is denied.
I am stuck with one asp.net error. My application work fine on development and test environemnt. But on production it give me following error:
Could not load file or assembly 'someProject' or one of its dependencies. Access is denied.
Go to Sysinternals and download Process Monitor: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Then start it up, filter thread and registry actions away. Clear contents. Run your app and get the error, and then stop the collection in process monitor. Now search for an ACCESS DENIED status, and you'll be able to see the exact file that's causing troubles, as well as the user account trying to get access.
Just delete the bin folder and then agian copy it. Now, it is working...
Give full permissions to the running user or group (like MACHINE\users group or DOMAIN\domain users) in
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
Use your target .net version number instead of v4.0.30319 if it's other than .net 4.0.
In my case by changing application pool identity from applicationpoolidentity to network service it works.
Check that the server user has access to the directory where your assemblies are located.
After deploying a new Web API project to our web farm, one of our web servers was malfunctioning and giving the error:
Could not load file or assembly 'Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Access is denied.
It turns out the folder hosting the Web API site was missing permissions for IIS_IUSRS
. Adding the user with Read
, Read & execute
, and List folder contents
permissions fixed the issue.
Sounds like an incorrectly configured server.
First, verify that the assembly does indeed exist.
Second, verify that your worker process account has access to it.