Problem:
This can be caused when the entire GAPI files are copied from a DocuWare client and into PSIcapture's library folder. We do not use this DLL file, so this error message is populated:
8/14/2014 9:20:41 AM - Error - v5.1.1.10
ResolveAssemblyICSharpCode.SharpZipLib, Version=0.86.0.518, Culture=neutral, PublicKeyToken=1b03e6acf1164f73
Failed to load from path C:\Program Files (x86)\PSIGEN\Capture\Libraries\DocuWare\ICSharpCode.SharpZipLib.dll.
System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Program Files (x86)\PSIGEN\Capture\Libraries\DocuWare\ICSharpCode.SharpZipLib.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files (x86)\PSIGEN\Capture\Libraries\DocuWare\ICSharpCode.SharpZipLib.dll'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at PSIGEN.Capture.Application.AssemblyResolver.LoadFromPath(String originalName, String name, String path)
WRN: Assembly binding logging is turned OFF.
Solution:
It is safe to delete this file and the log alerts should stop occurring in PSIcapture.
To enable assembly bind failure logging, set the following registry value to 1.:
HKLM\Software\Microsoft\Fusion!EnableLog (DWORD)
Note: There is a performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value:
HKLM\Software\Microsoft\Fusion!EnableLog
Comments
Please sign in to leave a comment.