Loading...

All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Ticket #283 (closed question: fixed)

Opened 6 years ago

Last modified 6 years ago

after installation through the deployment center I get an error

Reported by: erol.yavuz@… Owned by: permagne@…
Priority: blocker Component: 404Handler
Keywords: error 404handler Cc:

Description

The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

1) The export 'BVNetwork.FileNotFound.CustomRedirects.CustomRedirectInitialization (ContractName="EPiServer.Framework.IInitializableModule")' is not assignable to type 'EPiServer.Framework.IInitializableModule'.

Resulting in: Cannot set import 'EPiServer.Framework.Initialization.InitializationEngine.Modules (ContractName="EPiServer.Framework.IInitializableModule")' on part 'EPiServer.Framework.Initialization.InitializationEngine'.
Element: EPiServer.Framework.Initialization.InitializationEngine.Modules (ContractName="EPiServer.Framework.IInitializableModule") --> EPiServer.Framework.Initialization.InitializationEngine

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.ComponentModel.Composition.CompositionException: The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

1) The export 'BVNetwork.FileNotFound.CustomRedirects.CustomRedirectInitialization (ContractName="EPiServer.Framework.IInitializableModule")' is not assignable to type 'EPiServer.Framework.IInitializableModule'.

Resulting in: Cannot set import 'EPiServer.Framework.Initialization.InitializationEngine.Modules (ContractName="EPiServer.Framework.IInitializableModule")' on part 'EPiServer.Framework.Initialization.InitializationEngine'.
Element: EPiServer.Framework.Initialization.InitializationEngine.Modules (ContractName="EPiServer.Framework.IInitializableModule") --> EPiServer.Framework.Initialization.InitializationEngine

Attachments

26-3-2012 12-46-59.jpg (757.4 KB) - added by erol.yavuz@… 6 years ago.

Change History

Changed 6 years ago by erol.yavuz@…

comment:1 follow-up: ↓ 2 Changed 6 years ago by permagne@…

Hi,
the issue here is most likely that you are running .net 4.0.
Have a look at this article: http://world.episerver.com/Articles/Items/EPiServer-CMS-60-now-supporting-ASPNET-40/

Make sure that what is specified at point 6 is correct:

If you when developing a site in Visual Studio 2010, need to add a reference to System.ComponentModel.Composition, make sure that you use the version of that which is included in the EPiServer installation (for CMS 6.0 the version number is "2009.26.8.0"), and not the one installed with .NET 4. In Visual Studio, the referencing can be done by following these steps:

  1. Unload the project in VS 2010 by right-clicking on the project and choose “Unload project”.
  2. Right click on the project again and select “Edit project”.
  3. Locate the line : <Reference Include=”System.ComponentModel.Composition” /> and change it to:
<Reference Include="System.ComponentModel.Composition" >
<HintPath><location of episerver bin> \System.ComponentModel.Composition.dll</HintPath>
</Reference>

Most of these changes will be made automatically if you upgrade your solution using the Visual Studio 2010 upgrade functionality – but you need to do them manually to upgrade a running production environment.

comment:2 in reply to: ↑ 1 Changed 6 years ago by erol.yavuz@…

I do have one question though. I thought this package would give me a multi-language solution. But as soon as I create a dutch language file (site is in dutch and English) it will show me the error in dutch, even if I’m on the English site. Is that the correct behavior of this plugin?

comment:3 Changed 6 years ago by permagne@…

  • Type changed from defect to question

I am not sure what you mean - which error is displayed in dutch?
The 404 handler is not language specific.

comment:4 Changed 6 years ago by erol.yavuz@…

The content of the error page should differ depending on which language version of the site you are looking at. So:

  • viewing the english version --> english error (from the english language XML file)
  • viewing the dutch version --> dutch error (from the dutch language XML file)

Now I get only content from the dutch language XML. Even when I'm in the English branch.

comment:5 Changed 6 years ago by kianoush.eshaghi@…

  • Priority changed from major to blocker

I have done the workaround which is described above, but it didn't help. I had no problem to run my EPiServer CMS6 R2 on .Net Framework v4.0, I have gotten the error after installation of 404Handler 2.2 on my EPi project. What is wrong here?

I have read that the current 404Handler has not been tested on .Net Framework V4.0. Is there some incompatibility problem?

Notice: In the workaround above there is a hint that System.ComponentModel.Composition.dll should have the version number "2009.26.8.0", but the CMS dll on my PC under C:\Program Files (x86)\EPiServer\Framework\6.2.267.1\bin has the version number "2009.22.10.0"

comment:6 Changed 6 years ago by kianoush.eshaghi@…

  • Owner changed from permagne@… to kianoush.eshaghi@…
  • Status changed from new to assigned

comment:7 Changed 6 years ago by kianoush.eshaghi@…

  • Owner changed from kianoush.eshaghi@… to permagne@…

comment:8 Changed 6 years ago by permagne@…

  • Status changed from assigned to closed
  • Resolution set to fixed

Erol: unfortunately, this is not the case. Only one language is supported at the current version.
Kianoush's error is addressed in ticket #284. Closing this one.

Note: See HelpUser/Tickets for help on using tickets.