Richly Chheuy
Aug 4, 2014
(1 votes)

For Those Who Had Issues Updating to Commerce 7.10

Last Friday, new updates were released for the Commerce NuGet packages. The version numbers are now 7.10.1. I am aware that many who tried to update to the older 7.10 packages were greeted with a new migration page which forced a database update. Unfortunately, it seemed that those who attempted to update to 7.10 got migration failures instead.

I am happy to note that the migration issues should be fixed in 7.10.1 and I was able to update a base Commerce 7.5 site with sample templates to 7.10.1. Via NuGet console, I installed EPiServer.Commerce and then ran “update-epidatabase” to get to the migration page on my Commerce site.


Migration completed. Yay!

Clicking on “Go to start page” should direct you to your newly updated 7.10.1 site.

Information specific to what’s new in Commerce 7.10 can be hard to find, so here’s some quick links to get you in the right direction:

[New in 7.10.0] An update may have one or more migration steps that need to be executed in order for the site to work correctly. If so, any request to the site will be redirected to a migration page. In order to access it you need to be part of the "CommerceAdmins" role. From there it is possible to run the migration steps and track the progress. Once all steps have been completed successfully the redirects will stop, and the site will be back to normal.

[New in 7.10.0] It is possible to have the migration started automatically during the sites initialization. That is done by adding an app setting called "AutoMigrateEPiServer" and setting the value to "true". However, until all steps have been completed, any requests will still be redirected to the migration page, where it is possible to track the progress.

Release Notes:

EPiServer.Commerce 7.10
EPiServer.Commerce.UI 7.10

Aug 04, 2014


Jeff Valdez
Jeff Valdez Aug 4, 2014 07:44 PM

Awesome! :)

Aug 5, 2014 12:46 PM


K Khan
K Khan Aug 5, 2014 03:10 PM

Much needed

K Khan
K Khan Aug 5, 2014 03:14 PM

I was not able to login in CommerecManager after Update I created a User Group in CommerecManager 'CommerceAdmins' and added that in commerce manager. After that I was able to login on commerce manager but getting following error


Server Error in '/' Application.

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'System.Web.Mvc.ViewPage'.

Source Error:

Line 1: <%@ page language="C#" inherits="System.Web.Mvc.ViewPage" %>
Line 2: <%@ import namespace="EPiServer.Commerce.UI.Models.Migrate" %>
Line 3: <%@ import namespace="EPiServer.Commerce.Internal.Migration" %>

Richly Chheuy
Richly Chheuy Aug 5, 2014 05:12 PM

Hi Khurram,

Thanks for raising that issue. I'll see if I can reproduce the issue. I was hoping it'd be smooth sailing after 7.10.1 :).

Richly Chheuy
Richly Chheuy Aug 6, 2014 08:46 PM

@Khurram Couldn't reproduce, we'd probably need a copy of your site and DB. Updated to 7.10.1 successfully, can login and access Commerce Manager.

Richly Chheuy
Richly Chheuy Aug 6, 2014 08:46 PM

@Khurram Couldn't reproduce, we'd probably need a copy of your site and DB. Updated to 7.10.1 successfully, can login and access Commerce Manager.

Viktor G
Viktor G Sep 8, 2014 10:35 AM


I got the same error as Khurram after my upgrade and I think the reason was that I first visited the commerce site before I had run the migration tool on the EPiServer site. After that I was always redirected to "/modules/Commerce/Migrate" when trying to access the manager site.


Please login to comment.
Latest blogs
Update on .NET 8 support

With .NET 8 now in release candidate stage I want to share an update about our current thinking about .NET 8 support in Optimizely CMS and Customiz...

Magnus Rahl | Oct 3, 2023

Adding Block Specific JavaScript and CSS to the body and head of the page

A common requirement for CMS implementations includes the ability to embed third party content into a website as if it formed part of the website...

Mark Stott | Oct 3, 2023

Performance optimization – the hardcore series – part 1

Hi again every body. New day – new thing to write about. today we will talk about memory allocation, and effect it has on your website performance....

Quan Mai | Oct 3, 2023 | Syndicated blog

Next level content delivery with Optimizely Graph

Optimizely introduced a new product called Optimizely Graph earlier this year. We were one of the first partners to adopt this new service in a...

Ynze | Oct 2, 2023 | Syndicated blog

IDX21323 - RequireNonce is true, Nonce was null

We have multiple clients configured with Azure Active Directory (Microsoft Entra) for requiring authentication when accessing their website. The...

David Drouin-Prince | Oct 1, 2023 | Syndicated blog

Minimum Detectable Effect in Optimizely Web Experimentation

Understanding Minimum Detectable Effect Minimum Detectable Effect (MDE) is a core statistical calculation in Optimizely Web Experimentation. In...

Matthew Dunn | Oct 1, 2023 | Syndicated blog