Log4Net strong naming issue...

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
6/4/2009 1:16:26 AM
Gravatar
Total Posts 16

Log4Net strong naming issue...

 OS: Win 2k3

DB: MySQL

Ver: Latest from SVN

 

I am trying to get a fresh installation working.  I am getting this error:

Server Error in '/valleyview' Application.

Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821' could not be loaded.


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

Stack Trace:


[FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
mojoPortal.Business.AppKeepAliveTask..cctor() +0

[TypeInitializationException: The type initializer for 'mojoPortal.Business.AppKeepAliveTask' threw an exception.]
mojoPortal.Business.AppKeepAliveTask..ctor() +0
mojoPortal.Web.Global.Application_Start(Object sender, EventArgs e) +274

 

Please help.  Have you seen this before?  

 

Thanks,

David

6/4/2009 5:27:44 AM
Gravatar
Total Posts 18439

Re: Log4Net strong naming issue...

Assuming you alreadtydid a full Rebuild Solution, I would copy the log4net.dll from the _libs folder and paste it into Web/bin overwriting the old one there.

Hope it helps,

Joe 

6/5/2009 12:39:00 AM
Gravatar
Total Posts 16

Re: Log4Net strong naming issue...

 I have done a couple rebuilds and re-deployments, still no joy.

The log4net.dll file that is in the bin folder states that it is for the .net framework 1.0

http://picasaweb.google.com/lh/photo/pHt21xUh7Dh9Zz09t0YC1A?authkey=Gv1sRgCNu2xonD_L-p5QE&feat=directlink

 

The log4net.dll file that is in the _lib folder states that it is for the .net framework 2.0

http://picasaweb.google.com/lh/photo/2fzrG0_CIROvbr5IE7XhbQ?authkey=Gv1sRgCNu2xonD_L-p5QE&feat=directlink

 

Neither files work.  Both give me the same "manifest definition does not match..." error.

 

Can you confirm what version mojoPortal should be using?  These same file work when I access them locally (via IIS in vista) but once I upload them to my hosting company (HostMySite.com) I get this error.

 

Thanks for your help.

David

 

6/5/2009 4:03:59 AM
Gravatar
Total Posts 18439

Re: Log4Net strong naming issue...

Hi David,

It should use the newer one from the _libs folder, copy the one from the _libs folder into the Web/bin and if it gives trouble then also copy it into the mojoPortal.Business/bin/Release (and /Debug). Then rebuild the solution, verify it works locally. Then package a relase using UnleashIt

http://www.mojoportal.com/deploymentfromwindows.aspx

Also if there is an old DotNetOpenId.dll in your bin, delete it, its no longer used.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.