How can I enable Assembly binding logging

Question

I m getting   Could not load file or assembly  Bla  or one of its dependencies  An attempt was made to load a program with an incorrect format    A portion of the detailed info says    WRN  Assembly binding logging is turned OFF  To enable assembly bind failure logging  set the registry value  HKLM Software Microsoft Fusion EnableLog   DWORD  to 1  Note  There is some performance penalty associated with assembly bind failure logging  To turn this feature off  remove the registry value  HKLM Software Microsoft Fusion EnableLog     So  thinking this may give me some insight in why I m getting the error above  maybe the next YSOD would contain more explicit information about exactly why it s failing   I navigated to that location in the registry  but there is no such key that I can see  What it does have is    Fusion       Default    value not set      GACChangeNotification      NativeImagesIndex      PublisherPolicy   What am I missing

User · Answer

Per pierce jason s answer above  I had luck with   Just create a new DWORD 32  under the Fusion key  Name the DWORD to LogFailures  and set it to value 1  Then restart IIS  refresh the page giving errors  and the assembly bind logs will show in the error message

User · Answer

Instead of Creating New Application Pool You can go to your  Existing application Pool- Right click Advance setting- Enable 32-bit Application-----Set to TRUE

User · Answer

If you sometimes run different versions of your application  make sure you delete  Bla  from the application bin directory if the version running doesn t need it

User · Answer

Create a new Application Pool Go to the Advanced Settings of this application pool Set the Enable 32-Bit Application to True Point your web application to use this new Pool

User · Answer

Just create a new DWORD 32  under the Fusion key  Name the DWORD to EnableLog  and set it to value 1  Then restart IIS  refresh the page giving errors  and the assembly bind logs will show in the error message

User · Answer

A good place to start your investigation into any failed binding is to use the  quot fuslogvw exe quot  utility  This may give you the information you need related to the binding failure so that you don t have to go messing around with any registry values to turn binding logging on  Fuslogvw MSDN page The utility should be in your Microsoft SDKs folder  which would be something like this  depending on your operating system   quot C  Program Files  x86  Microsoft SDKs Windows v SDK version A Bin FUSLOGVW exe quot   Run this utility as Administrator  from Developer Command Prompt  as Admin  type FUSLOGVW a new screen appears  Go to Settings to and select Enable all binds to disk also select Enable custom log path and select the path of the folder of your choice to store the binding log   Restart IIS   From the FUSLOGVW window click Delete all to clear the list of any previous bind failures  Reproduce the binding failure in your application  In the utility  click Refresh  You should then see the bind failure logged in the list   You can view information about the bind failure by selecting it in the list and clicking View Log   The first thing I look for is the path in which the application is looking for the assembly  You should also make sure the version number of the assembly in question is what you expect

User · Answer

When I had the same problem I fixed it by deleting the existing key snk in that project and adding a new key

User · Answer

This error comes for me in windows application while calling server dll from client  After system restart it works fine

User · Answer

For me the  Bla  file was System Net http dll which was missing from my BIN folder  I just added it and it worked fine  Didn t change any registry key or anything of that sort

[registry] How can I enable Assembly binding logging?

Examples related to registry

Examples related to regedit

Examples related to assemblybinding

Examples related to ysod