Don't miss out Virtual Happy Hour this Friday (April 26).

Try our conversational search powered by Generative AI!

Upgrade version 5 R2 to version 6.0 - error

Vote:
 

When i try to upgrade version 5 R2 to version 6.0 i have this error.

An unhandled error has occured:
Cannot resolve dependencies for the following module(s)
EPiServer.Web.InitializationModule
EPiServer.Web.InitializationModule
When executing


At C:\Program Files (x86)\EPiServer\CMS\6.0.530.0\Upgrade\System Scripts\Upgrad
e Site (SqlServer).ps1:489 char:26
+     Upgrade-EPiDdsIdentities  <<<< $wizard.SelectedApplication

=
Get-EPiIsBulkInstalling
An error has occured and the transaction will be rolled back
Rolledback

At C:\Program Files (x86)\EPiServer\CMS\6.0.530.0\Upgrade\System Scripts\Upgrade Site (SqlServer).ps1:489 char:26
+     Upgrade-EPiDdsIdentities  <<<< $wizard.SelectedApplication
System.InvalidOperationException: Cannot resolve dependencies for the following module(s)
EPiServer.Web.InitializationModule
EPiServer.Web.InitializationModule
   at EPiServer.Framework.Initialization.InitializationEngine.CreateDependencySortedModules(IEnumerable`1 modules)
   at EPiServer.Framework.Initialization.InitializationEngine.Initialize(HostType hostType)
   at EPiServer.Framework.Initialization.InitializationModule.StaticInitialization(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.Upgrade.CMS5.UpgradeDdsIdentitiesCmdlet.ProcessRecord()
   at System.Management.Automation.Cmdlet.DoProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()

Can anybody help me.

Thank you.

#64197
Dec 12, 2012 18:22
Vote:
 

Check which .NET Framework version Deployment Center is running on and try changing it between 2.0 and 4.0.

http://world.episerver.com/Blogs/Paul-Smith/Dates1/2011/3/Upgrading-CMS-6-R1-sites-compiled-against-NET-40/

Also try changing the app pool to 32-bit mode and see if the 5 R2 site is still running. Deployment Center runs in 32-bit mode and this will be sort of like a pre check that it will be able to "run" the site internally.

Can the environment successfully run both 5 R2 and 6 R1 (other) sites?

#64250
Dec 14, 2012 13:15
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.