Migration Issues after epi 8 upgrade

November Happy Hour will be moved to Thursday December 5th.

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / Customized Commerce 13 and earlier versions /

Migration Issues after epi 8 upgrade

Azhar Mahmood

Vote:

We are currently testing epi 8.x upgrade and have come accross some database issues.

1. Contact migration was not completed "even though" it gave a success message. We ended up correcting issues with sql scripts.

2. There were some dups created in [CatalogItemSeo] table by migration, after removing the dups, the issu was resolved.

3. Commerce Manager site is breaking when you open a product/variation for editing with teh followign exception. Is it possible to identify the scripts that are executed during migration, after site comes up first time post epi 8 upgrade? I fear that there could

Server Error in '/' Application.
________________________________________
Sequence contains more than one element
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.InvalidOperationException: Sequence contains more than one element

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.

Stack Trace: 

[InvalidOperationException: Sequence contains more than one element]
   System.Linq.Enumerable.Single(IEnumerable`1 source) +397
   Mediachase.Web.Console.Common.ManagementHelper.SelectListItem(DropDownList list, String value, IEqualityComparer`1 comparer) +363
   Mediachase.Commerce.Manager.Core.MetaData.MetaControls.DicSingleValueControl.BindData() +1120
   Mediachase.Commerce.Manager.Core.MetaData.MetaControls.DicSingleValueControl.DataBind() +43
   Mediachase.Commerce.Manager.Core.MetaData.EditTab.CreateMetaControls(MetaClass metaClass, Dictionary`2 metaObjects, String defaultLanguage) +871
   Mediachase.Commerce.Manager.Core.MetaData.EditTab.DataBind() +491
   Mediachase.Commerce.Manager.Catalog.Tabs.EntryOverviewEditTab.BindMetaForm() +231
   Mediachase.Commerce.Manager.Catalog.Tabs.EntryOverviewEditTab.Page_Load(Object sender, EventArgs e) +274
   System.Web.UI.Control.LoadRecursive() +116
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Control.LoadRecursive() +206
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2718

________________________________________
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34249

#123713

Jul 16, 2015 23:19

Azhar Mahmood

Vote:

Hello,

Can anyone please take a look at #3 above and provide some insight, so we can take care of the duplicate rows. Right now we cannot open any product from within commerce manager. I will appreciate if you can also shed some light on "what exactly Migration "post epi 8 upgrade", does, so we can handle it better in production deployment.

Thanksk for your help again.

Azhar

#131386

Jul 22, 2015 16:12

Quan Mai

Vote:

Hi,

Sorry for the late reply, but I think the issue with Commerce Manager was because you forgot to delete the Apps virtual folder in IIS.

Regards.

#131520

Jul 29, 2015 11:13

Azhar Mahmood

Vote:

Thanks for the response Quan.

Actually we host Commerce Manager site on a searpate server ("not the one that hosts frontend websites"). So we never created a virtual directory for it. But the issue is not consistent, we don't have it in integrated DEV environment, but it happens in staging but IE works jsut fine everywhere.

But my other biggest concern is "What does migration do to data". I am talking about the migration page that pops up when you fireup the site first time after episerver 8 upgrade. Is there any of knowing, "which sql scripts or strred procedures are executed, during migration"?

Thanks,

Azhar

#131529

Jul 29, 2015 16:34

Quan Mai

Vote:

By default, CM created by Deployment Center (7.5) will have an Apps virtual directory in IIS - and after you upgrade to later version, it's required to delete that. It's not what you created manually.

The only way you can have a peek view into what is processing and use a reflector and look into EPiServer.Commerce.Internal.Migration.dll, but we do many things there- APIs, sql scripts,... to ensure the data is updated correctly, if necessary. If you get an error in the migration - I would suggest to contact our support service. I suspect it might be a configuration error, but until we can see what went wrong and why, I can't say anything for sure.

Regards.

#131531

Jul 29, 2015 16:41

Please login to post a reply