log4net not logging and throwing error

不想你离开。 提交于 2019-12-08 12:00:09

问题


I have been using log4Net to write in a text file when there is any exception in my web service, this was working but today it started to throw error.

System.Web.Services.Protocols.SoapException: Server was unable to

process request. ---> System.TypeInitializationException: The type initializer for.. threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=b32731d11ce58905' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=b32731d11ce58905'

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].

If you have any inputs on this stack info, pls. share it.


回答1:


Did you change the code, or did this just start happening?

I've seen this error occur when the target processor architecture was mismatched. Did you change that by any chance?

If this isn't the case, and you have Windows SDK installed, you can use the Fusion Log Viewer to view assembly binding logs. The utility should be installed on your machine.



来源:https://stackoverflow.com/questions/7099068/log4net-not-logging-and-throwing-error

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!