We are running AppDynamics.Agent.Coordinator 4.2.8. When this service is running, we get this error.
The file is present in the GAC and the Fusion logs show:
<meta http-equiv="Content-Type" content="charset=unicode-1-1-utf-8"><!-- saved from url=(0015)assemblybinder: --><html><pre>
*** Assembly Binder Log Entry (8/30/2017 @ 9:24:49 PM) ***
The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Running under executable c:\windows\system32\inetsrv\w3wp.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: DisplayName = System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
(Fully-specified)
LOG: Appbase = file:///C:/somesite/IIS/test-site.com/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = 448f9594
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\somesite\IIS\test-site\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: GAC Lookup was unsuccessful.
ERR: No codebases found to download from.
ERR: Unrecoverable error occurred during pre-download check (hr = 0x80070002).
Is this the same issue as referenced in : https://community.appdynamics.com/t5/NET-Agent-Installation/Could-not-load-file-or-assembly-Newtonso...
I looked at the release notes for 4.3.1, but did not see a resolved issue specifically for GAC access issues.
Thank you!
Raunak,
We were able to resolve the issue by upgrading the agent to 4.3.
Thanks for getting back to us.
Sean
Hi,
Can you try adding <add-assembly-reference enabled="false" /> section at your config.xml located at C:\ProgramData\AppDynamics\DotNetAgent\Config
Your config.xml will look like following ( content in bold needs to be added). Once you add this section please recycle Agent Coordinator Service and instrumented section
<app-agents>
<profiler>
<add-assembly-reference enabled="false" />
</profiler>
....
....
....
</app-agents>
Let us know if this does not resolve the issue.
Thanks,
Raunak
Raunak,
We were able to resolve the issue by upgrading the agent to 4.3.
Thanks for getting back to us.
Sean