I am trying to install Composer 4.1 on an CMS 6 R2 site. The site is more or less empty (contains only one page). When installing Composer I got the following exception
Copied Install Composer.metadataCopied Upgrade Composer.metadataAn error has occured and the transaction will be rolled backRolledbackAn unhandled error has occured:Cannot resolve dependencies for the following module(s) EPiServer.Web.InitializationModuleEPiServer.Web.InitializationModuleEPiServer.Web.InitializationModuleWhen executingAt C:\Program Files\EPiServer\CMS\6.1.379.0\Install\Modules\Composer 4.1\Install Composer.ps1:138 char:20+ Add-EPiServerData <<<< $episerverDataFile $selectedWebApplication.PhysicalPath $selectedWebApplication.ApplicationName -updateStartPageAttributeFalse=Get-EPiIsBulkInstallingAt C:\Program Files\EPiServer\CMS\6.1.379.0\Install\Modules\Composer 4.1\Install Composer.ps1:138 char:20+ Add-EPiServerData <<<< $episerverDataFile $selectedWebApplication.PhysicalPath $selectedWebApplication.ApplicationName -updateStartPageAttributeSystem.InvalidOperationException: Cannot resolve dependencies for the following module(s) EPiServer.Web.InitializationModuleEPiServer.Web.InitializationModuleEPiServer.Web.InitializationModule at EPiServer.Framework.Initialization.InitializationEngine.CreateDependencySortedModules(IEnumerable`1 modules) at EPiServer.Framework.Initialization.InitializationEngine.Initialize(HostType hostType) at EPiServer.Framework.Initialization.InitializationModule.Initialize(HostType hostType) at EPiServer.Framework.Initialization.InitializationModule.FrameworkInitialization(HostType hostType) at EPiServer.Install.CMS.Common.EPiServerCMSWrapper.InitalizeEPiServer(String webConfigPath) at EPiServer.Install.CMS.Common.EPiServerCMSWrapper.Initialize(String destinationPath, String virtualDirectory) at EPiServer.Install.CMS.Common.EPiServerCMSWrapper.Initialize(String destinationPath, String virtualDirectory) at EPiServer.Install.Common.AppDomains.RunInAppDomainInstaller.Install(IDictionary stateSaver) at EPiServer.Install.InstallationManager.Install(Installer installer) at EPiServer.Install.CMS.Modules.ModulesInstallationManager.ImportData(InstallationManager installationManager, String destinationDirectory, String virtualDirectory, String importSource, DatabaseDestination destination, Boolean updateStartPageAttribute, TimeSpan transactionTimeout) at EPiServer.Install.CMS.Modules.CmdLets.AddEPiServerData.ProcessRecord() at System.Management.Automation.Cmdlet.DoProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord()
It seems that the installation could not resolve the correct version of CMS. Is your CMS R2 site a new installation or an upggrading? Can you verify the version of CMS assembly in your bin folder and the assembly binding in the web.config is correct version (6.1.379.0).
It is a new installastion and all the EPiServer assemblies is of version 6.1.379.0, except some of them has version 6.2.267.1 (EpiServer.Framework, EPiServer.Data, EPiServer.Licensing, EPiServer.Events,EPiServer.SHell, EPiServer.ApplicationModules, EPiServer.Data.Cache and EPIServer.Shell.UI).
And the bindings in web.config is in accordance with this version numbers.
I guess that you first installed the CMS 6 R2, then you did something (build a new project and created a page type, adding a page) and then installed Cmposer R2. Could you try to run a new installation of CMS r2 again from deployment center, and then select Composer 4 R2 in the optional modules and see if you still get the same issue.
You are right.
I also tried installing a new site with no content and Composer. Then the installation was successfull, but I did not get any [ExtensionDataContainer] in the page structure.
When I tried reinstalling Composer on the same site I got the same error as mention earlier.
I get it. We'll try to reproduce the issue and get back to you if we found out anything.
I'm having the exact same problem described in Lars exception. The only working way to install Composer without errors, was to install it together with the Alloy example site (but I did not get any [ExtensionDataContainer] in the page structure either. It is only visible in "Set Access Rights" in the "Admin Mode").
Any news on a fix for this? I need to upgrade an R2 site to Composer but getting the same error as Lars.
I,m also interested in this matter :) What are your prerequisites? (From what version to where, episerver, modules and plugins etc...)
I was actually upgrading a relatively simple EPiserver 6 R2 solution to Composer. The solution had been previousely upgraded from EPiServer 6 but had no other modules or plugins of note except perhaps Page Type Builder but there are ways to get the two technologies working together.
In the end the only way I could upgrade was to run the procedure manually. I created a brand new R2 site and was able to upgrade that site to include Composer.
I then copied the required files from the new installation into my existing solution, updated my web.config etc and then imported my content from the old DB into the new DB. All worked fine with a few tweaks. This approach is not ideal but I haven't encountered any issues so far and have been able to add Composer modules to upgraded page types etc.
Got a new error message today, when I tried to install Composer on our testserver. Had installed EPiServer R2, moved our application to the site (including database with Composer Content).
THe message was
Copied Dropit.Extension_SV.xmlCopied newtext_Dropit.Extension.xmlCopied newtext_Dropit.Extension_SENT.xmlCopied Install Composer.metadataCopied Upgrade Composer.metadataAn unhandled error has occured:You cannot call a method on a null-valued expression.When executingAt C:\Program Files (x86)\EPiServer\CMS\6.1.379.0\Install\Modules\Composer 4.1\Install Composer.ps1:134 char:80+ $orgPageStartId = $selectedWebApplication.SiteSettingsConfigNode.GetAttribute <<<< ("pageStartId")False=Get-EPiIsBulkInstallingAn error has occured and the transaction will be rolled backRolledbackAt C:\Program Files (x86)\EPiServer\CMS\6.1.379.0\Install\Modules\Composer 4.1\Install Composer.ps1:134 char:80+ $orgPageStartId = $selectedWebApplication.SiteSettingsConfigNode.GetAttribute <<<< ("pageStartId")System.Management.Automation.ParentContainsErrorRecordException: You cannot call a method on a null-valued expression.
It seems that SiteSettingsConfigNode is null in your case. Did you get the site up and run before installing Composer?
The site is up and running and this is the sitesettings
<sites> <site siteId="cw_demo" description="Canal Digital KabelTv - Reskinned Demo"> <siteSettings enableScheduler="true" errorMailHandler="~/util/SendErrorReport.aspx" globalErrorHandling="RemoteOnly"
globalErrorMail="" httpCacheExpiration="0:0:0" httpCacheability="Public" httpCacheVaryByCustom="path"
mirroringFileWriteRetryDelay="0:0:5" mirroringHtmlTextEncoding="" mirroringRetries="5"
mirroringRetryDelay="0:0:1" pageCacheSlidingExpiration="12:0:0" pageFolderVirtualPathProvider="SitePageFiles"
pageOfficeStartId="0" pageRootId="1" pageStartId="13" pageUseBrowserLanguagePreferences="false"
pageValidateTemplate="false" pageWastebasketId="2" remoteCacheListenerShortNames=""
remotePageCacheSlidingExpiration="2:0:0" remoteWebServiceCulture="0" sgmlParserDecodeCharEntities="false"
subscriptionHandler="EPiServer.Personalization.SubscriptionMail,EPiServer" uiDefaultPanelTab="0" uiEditorColors=""
uiEditorCssPaths="~/util/styles/Editor.css" uiEditorHeight="250" uiEditorValueOptions="0" uiEditorWidth="500"
uiImageTransparencyReplacement="White" uiKeepUserLoggedOn="true" uiMaxVersions="0"
uiShowGlobalizationUserInterface="false" uiTheme="" uiVersionMerging="true" urlRewriteExtension=""
siteDisplayName="Canal Digital KabelTv - Reskinned Demo" siteUrl="http://reskinned.canaldigital.no/"
uiUrl="~/UI/CMS/" utilUrl="~/util/" enableXmlRpcHeader="true" /> </site> </sites>
Have you edited the episerverframework.config?
Make sure it says:
<scanAssembly forceBinFolderScan="true" />
Also, if you have upgraded your projec to .NET 4.0, add a startup tag to the EPiServerInstall.exe.config file:
Lars, were you ever able to get this fixed? I'm experiencing the exact same problem, installer complaining about not being able to resolve dependencies for EPiServer.Web.InitializationModule.
The site is running fine with CMS 6 R2 and CMO 2 R2 on ASP.NET 4.0.
Seems it fails when it tries to spin up the site to import data from the extension.episerverdata file?
Update: When I temporarily removed the Page Type Builder assemblies from the project I was able to install Composer. I could then re-add Page Type Builder - and everything has worked just fine since.