EPiServer 6 site not working after installing cms 7.5

Vote:

After installing EPiServer 7.5, one of my episerver 6 sites is failing to start with the error:

Could not load file or assembly 'EPiServer.Licensing, Version=7.5.373.4, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

The EPiServer 6 website has the correct version of the assembly in its bin folder (version 6.2.267.1) and in the web.config, the following is decalred:

My understanding is that with the binding redirect set like this in the config file, the site should correctly be using the dll from the bin folder.

Can anyone help?

Thanks,

Adam

#81343

Feb 14, 2014 12:58

Johan Björnfot

Vote:

My guess is that there is some other assembly of version 7.5 loaded into the AppDomain (if that assembly then references 7.5 version of EPiServer.Licensing you might get that problem).

Is it possible to have a Visual Studio attached to the site while starting, if so check in Debug\Windows\Modules and see if there is any 7.5 version of any EPiServer assembly loaded.

Otherwise check in the sites bin folder so there is no EPiServer 7.5 version assembly there or perhaps an assembly referencing a 7.5 assembly.

#81345

Feb 14, 2014 14:06

David Knipe

Vote:

Hi Adam

I have experienced a similar problem to this on other EPiServer assemblies on an EPiServer 6 R2 build. I found that I had to set "Specific Version" to true on each assembly that was experiencing the problem (it was on a Windows 8 machine). It seemed that the project was always trying to get the latest assembly version even though no 7.x assemblies were in the GAC.

I never had time to the bottom of the problem but hope it may be able to help you!

David

#81351

Feb 14, 2014 15:12

valdis

Vote:

From the exception actually it sounds that somebody else is requsting 7.5 version -> but got 6.2.X.X -> which is located in AppDomain. I would start from another end :) Enable FusionLog and check - you may see calling assembly.

If that fails and there could be - "Unknown library" or similar, I would enlist all dll files in bin folder with versions to check - maybe there is some alien requesting 7.5 version..

#81382

Feb 16, 2014 21:59

Vote:

Thanks for replies all.

When I attatched the debugger, I received a more helpfull stack trace showing the dll exception originating from the license check in the app initalization.

It then occured to me that for the EPiServer 6 site, I have re-used a license from a 7.5 site which was on my pc.. opps!

So because the site had a 7.5 liscence, EPiServer was trying to load the 7.5 licensing dll.

Put a correct v6 license into the site and it worked fine.

#81384

Feb 16, 2014 22:10

valdis

Vote:

So my intuition didn't fail :)

#81385

Feb 16, 2014 22:17