CODEWITHSUNDEEP
.netasp.netvisual-studio-2010
Bruno
Bruno

Reputation: 6449

Could not load file or assembly '' or one of its dependencies. An API call exited abnormally

I have a .NET App that I've recently Checked In to Team Foundation Server. Ever since I Checked it in, I get Access Denied to the App folder. I then give security permissions to the impersonated user and receive the error:

Could not load file or assembly 'PMD Image Upload' or one of its dependencies. An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT))

Upvotes: 25

Views: 25009

Answers (5)

sebpinski
sebpinski

Reputation: 111

The impersonate user should be given privileges to the solution files as well as the temp asp.net files for the solution, usually located in the following directory:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

Where "Framework" could be "Framework64" and "v4.0.30319" may be another .Net version number.

In some cases the folder is located in:

C:\Users\YOURUSERNAME\AppData\Local\Temp\Temporary ASP.NET Files

Upvotes: 8

user2111162
user2111162

Reputation: 1

<div id="divWindowMain">
   <asp:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server">
       <Services></Services>
   </asp:ScriptManagerProxy>
</div>

Upvotes: -1

Marco G&#246;stl
Marco G&#246;stl

Reputation: 151

I know this is pretty old, but if you need to impersonate on the webserver you also need to award the impersonated user the rights to create/modify the folder "Temporary ASP.NET Files" in Windows\Microsoft.NET\"TheUsedFrameworkVersion".

Upvotes: 15

s15199d
s15199d

Reputation: 7717

Bruno is correct. Disabling impersonation worked for me as well. If you don't have impersonate in your webconfig, and you're still having trouble. If you're running IIS 7.5 check your Application Pool. Sometimes it can be set to impersonate.

Look under [Advanced Settings > Process Model > Identity]

You'll want to set it to [ApplicationPoolIdentity].

Upvotes: 0

Bruno
Bruno

Reputation: 6449

Impersonate on the web.config was enabled for a user with no privileges on the debug machine. Commented out the impersonate and was able to debug the .NET app.

Upvotes: 34

Related Questions