issue when upgrade Kentico 10 to 11

Jirayu Assawajindakun asked on June 27, 2019 05:03

Dear Kentico Team
I have a problem after Upgrade K10 to K11 by

1. Run API Change VS2017 by console
2.Run Upgrade_10_0_11_0.exe
3.Install the upgrade procedure


and then Show all successfully. when I test site, Now show error message below:
Could not load file or assembly 'CMS.Base, Version=10.0.0.0, Culture=neutral, PublicKeyToken=834b12a258f213f9' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) pls help Thank.

Image Text

Correct Answer

Jirayu Assawajindakun answered on June 27, 2019 08:54

Thank for all Feedback,
Now still Work fine after add some code in web.config like this

Image Text

0 votesVote for this answer Unmark Correct answer

Recent Answers


Brenden Kehren answered on June 27, 2019 05:07

Roll your upgrade back to your v10 instance and DO NOT run the API change process. Run the upgrade via the KIM then open the upgraded project in Visual Studio and build the project. Resolve your errors from there.

Most likely the API Change program caused some problems. Doing upgrades for the last 9 years, we've found it's easiest to resolve the issues you have with your custom code after you've ran the upgrade procedure vs. using the tool Kentico provides.

0 votesVote for this answer Mark as a Correct answer

Jirayu Assawajindakun answered on June 27, 2019 05:44

Thank for Feedback.

But I had been retrying to Install Upgarde without API Change and build my project.
It still show the same error like topic post. Can you help me please.

0 votesVote for this answer Mark as a Correct answer

Dmitry Bastron answered on June 27, 2019 06:21

After installing the upgrade check your project referencies, Lib and Bin folders if they contain CMS.* libraries of 10 version. If so just delete these referencies / libraries. This should help.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on June 27, 2019 14:51

Adding those dependent assemblies is NOT necessary and will only cause further problems down the road. You most likely have a wrong reference in your project. Take a look in the file system and find out what version of the DLLs are in your project. Navigate to:

..\<project root>\CMS\bin

and look at any of the CMS.xxx.dll files properties for the version number. You most likely have the wrong version dll referenced in your project. Remove those old/bad references and add in the new dll references, then remove those web.config entries.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.