Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Mihir Ajmera 32 posts 145 karma points
    Sep 03, 2019 @ 07:32
    Mihir Ajmera
    0

    Content Migration Error From Umbraco version 7.14.0 to 8.1.0

    Hello All,

    I have a large scale content data available in the Umbraco 7.14.0 and it's around 12Lac+ entry available in the cmspropertyData table. As per new requirement, I try to update Umbraco version 7.14.0 to Umbraco 8.1+ version. For this, I set up all configuration, remove recycle bin entry, remove version history which requirement upgrade content migration in the Umbraco version 8.1.0.

    After, continue process on content migration which takes around 2 hr and getting me below error.

    The database failed to upgrade. ERROR: The database configuration failed with the following message: Cannot rename datatype alias "Umbraco.MediaPicker2" to "Umbraco.MediaPicker" because the target alias is already used.This is generally because when upgrading from a v7 to v8 site, the v7 site contains Data Types that reference old and already Obsolete Property Editors. Before upgrading to v8, any Data Types using property editors that are named with the prefix '(Obsolete)' must be migrated to the non-obsolete v7 property editors of the same type. Please check log file for additional information (can be found in '/App_Data/Logs/')

    So, anyone have any idea about how to solve this issue and do the process again with minimum time and migrate fully content without any error.

    Because. content was too large so every-time its take much time to process.

    Thanks in advance.

    Copy Link
  • Shaishav Karnani from digitallymedia.com 354 posts 1638 karma points
    Sep 03, 2019 @ 07:53
    Shaishav Karnani from digitallymedia.com
    0

    Hi Mihir,

    Your site was built on old version and seems to be migrated to v7.14. Therefore, it is using old Media Data Type. You need to upgrade old media to use new Media in v7.14 and if you are using any other Obsolete Data Type then please upgrade it too before moving to v8.

    If any data type that donot have matching with v8 data type for plugins then change it to label. So, that atleast you can move without any errors.

    Also I would suggest that before migrating you cleanup your database. So, that records get reduced. Old logs, old versions of content gets removed. Remove any item from Recycled bin.

    It's seems bit of work in your case given the volume.

    Do let me know how it goes?

    Cheers,

    Shaishav

    Copy Link
  • Jesper Ordrup 1019 posts 1528 karma points MVP
    Sep 25, 2022 @ 14:23
    Jesper Ordrup
    0

    Im upgrading an Umbraco 7.15.x to 8.18.15 and Im running into the same error:

    The database failed to upgrade. ERROR: The database configuration failed with the following message: 
Cannot rename datatype alias "Umbraco.MediaPicker2" to "Umbraco.MediaPicker" because the target alias is already used. 
This is generally because when upgrading from a v7 to v8 site, the v7 site contains Data Types that reference old and already Obsolete Property Editors. 
Before upgrading to v8, any Data Types using property editors that are named with the prefix '(Obsolete)' 
must be migrated to the non-obsolete v7 property editors of the same type.

    My problem is that none of the datatypes are marked as obsolete and there are no alternative editors.

    Im suspecting that my problem is a bit different. It might be that the property editor is actually the updated editor, but the alias is wrong.

    Is it possible to rename the alias Umbraco.MediaPicker2 to Umbraco.MediaPicker ?

    enter image description here

    Thanks

    Jesper

    Copy Link
  • Marc Goodson 2155 posts 14408 karma points MVP 9x c-trib
    Sep 25, 2022 @ 20:43
    Marc Goodson
    0

    Hi Jesper

    Can you go to 8.5 first?

    I don't think you can go direct to 8.15, at least not without the ProWorks package installed.

    I usually go to the latest 8.5.x version, as there was a bug (maybe this one) introduced in the migrations in 8.6

    Once you are on 8.5 you can 'go again' up to 8.15...

    regards

    Marc

    Copy Link
  • Jesper Ordrup 1019 posts 1528 karma points MVP
    Sep 26, 2022 @ 12:42
    Jesper Ordrup
    0

    Hi Marc,

    That's worth trying. I tried with ProWorks package and I think I've tried 8,5,x first also - but I could have fumbled and not done a clean take.

    I have to try again!

    Thanks Marc,
    Jesper

    Copy Link
  • Marc Goodson 2155 posts 14408 karma points MVP 9x c-trib
    Sep 26, 2022 @ 14:38
    Marc Goodson
    0

    Hi Jesper

    The other thing would be to install 'God Mode' package on the V7 site

    that will allow you to find any DataTypes still based on the MediaPicker property editor and not the MediaPicker2.. (the cool fancy udi one)...

    regards

    Marc

    Copy Link
  • Jesper Ordrup 1019 posts 1528 karma points MVP
    Sep 26, 2022 @ 14:48
    Jesper Ordrup
    0

    Thanks Marc,

    If the current migration (currently running) doesnt work ... fantastic package "God mode".

    best
    Jesper

    Copy Link
  • Jesper Ordrup 1019 posts 1528 karma points MVP
    Sep 28, 2022 @ 22:34
    Jesper Ordrup
    0

    Quick update. Came far .. but died. Reason was multiple old 3 part property editors. Realized in the end that time was running out and took a different approach.

    Dumping site site data as json files. Site frontend is running in nodejs w/sveltekit anyways. Later when there's time and budget - It will take me less time to create a import script for a brand new 10.x.

    And it will be clean. Upgraded sites almost always have issues/sideeffects

    Best
    Jesper

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 03, 2019 @ 08:42
    Mihir Ajmera
    0

    Hi Shaishav,

    I have no idea about upgrading old media type to new media type in v7.14 and Obsolete Data Type. can you share me any reference link so I can follow and do the appropriate process?

    My existing Umbraco version 7.14.0 which I need to upgrade 8.1+.

    I can`t identify the media type version so can you help me with this?

    Thanks.

    Mihir.

    Copy Link
  • Shaishav Karnani from digitallymedia.com 354 posts 1638 karma points
    Sep 03, 2019 @ 09:41
    Shaishav Karnani from digitallymedia.com
    1

    (Obsolete) Media Picker https://our.umbraco.com/Documentation/Getting-Started/Backoffice/Property-Editors/Built-in-Property-Editors/Media-Picker/old-media-picker

    It stores as ID or CSV where as (New) Media Picker stores values in UDI format.

    So, you need to convert any Document Type that uses (Obsolete) Media Picker to (New) Media Picker before migrating to v8. Can you check if you are using (Obsolete) data type in your project first?

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 03, 2019 @ 12:44
    Mihir Ajmera
    1

    Hi Shaishav,

    Thanks for the reference link.

    I check all existing data type of media picker, content picker etc which are starting with "(Obsolete)" prefix so I replace those data type with newly data type just like (Obsolete) Media picker to "Media Picker".

    After again run the migration process then its work continues and gives another "cmsMacro" table column "macroSource" not accept null value which I also resolved it.

    Currently, it gives me below error which I try to solve.

    The database failed to upgrade. ERROR: The database configuration failed with the following message:  Invalid cast from 'System.DateTime' to 'System.ValueTuple`2[[System.Nullable`1[[System.DateTime, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]], mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],System.Nullable`1[[System.DateTime, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]], mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]'.

    If you have any idea for above error then tell me so continue on next process for further migration?

    Thanks in advance.

    Copy Link
  • Steve Megson 151 posts 1024 karma points MVP c-trib
    Sep 03, 2019 @ 12:51
    Steve Megson
    2

    That looks like this bug, which was fixed in 8.1.2.

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 04, 2019 @ 06:44
    Mihir Ajmera
    0

    Hi Shaishav,

    I try with latest release version Umbraco 8.1.4 which I think it solves the above error but somehow it gives me another error in the database with Foreign key release issues created. Please refer below error

    The database failed to upgrade. ERROR: The database configuration failed with the following message: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_umbracoUser2NodeNotify_umbracoUser_id". The conflict occurred in database "umbracodb814", table "dbo.umbracoUser", column 'id'

    For this error, I checked the database entry of two tables and I got data from the Umbracouser table with Foreign key constraint so why this error come I don`t know.

    One thing I identify in the UmbracoUser table is with the latest Umbraco 8 Master Admin user created with -1(primary key) value and but in my case of Umbraco 7 admin user has 0(Primary key) value. So, I am not sure maybe this value changes effect to Foreign key relationship.

    If you have any idea about this then tell me so quick resolve and continue on the further process?

    Currently, I am stuck with this error your suggestion will be appreciated for the next process.

    Thanks in advance

    Copy Link
  • Steve Megson 151 posts 1024 karma points MVP c-trib
    Sep 04, 2019 @ 08:56
    Steve Megson
    100

    This does look like a bug. When the the superuser is moved to ID -1, umbracoUser2NodeNotify should be updated to reflect that.

    Here's the SQL the migration uses, with the missing update of umbracoUser2NodeNotify added. You should be able to run this before the migration to avoid the bug.

    umbracoUser set userLogin = userLogin + '__' where id=0

set identity_insert umbracoUser on;

insert into umbracoUser (id,
    userDisabled, userNoConsole, userName, userLogin, userPassword, passwordConfig,
    userEmail, userLanguage, securityStampToken, failedLoginAttempts, lastLockoutDate,
    lastPasswordChangeDate, lastLoginDate, emailConfirmedDate, invitedDate, 
    createDate, updateDate, avatar, tourData)    
select
    -1 id,
    userDisabled, userNoConsole, userName, substring(userLogin, 1, len(userLogin) - 2) userLogin, userPassword, passwordConfig,
    userEmail, userLanguage, securityStampToken, failedLoginAttempts, lastLockoutDate,
    lastPasswordChangeDate, lastLoginDate, emailConfirmedDate, invitedDate, 
    createDate, updateDate, avatar, tourData
from umbracoUser where id=0;

set identity_insert umbracoUser off;

update umbracoUser2UserGroup set userId=-1 where userId=0;
update umbracoNode set nodeUser=-1 where nodeUser=0;
update umbracoUserLogin set userId=-1 where userId=0;
update umbracoUser2NodeNotify set userId=-1 where userId=0;
update cmsPropertyData set userId=-1 where userId=0;

delete from umbracoUser where id=0;
    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 05, 2019 @ 04:47
    Mihir Ajmera
    0

    Hello Steve Megson,

    Thanks for the quick solution it works fine.

    After resolved above error I do the same process again for content migration I got below numbers of type errors.

    1. Skipping validation of configuration for data type {NodeId} : {EditorAlias}. Please ensure that the configuration is valid. The site may fail to start and / or load data types and run.","@l":"Warning","NodeId":11037,"EditorAlias":"Umbraco.RadioButtonList","SourceContext":"Umbraco.Core.Migrations.Upgrade.V_8_0_0.DataTypeMigration",
2. Skipping validation of configuration for data type {NodeId} : {EditorAlias}. Please ensure that the configuration is valid. The site may fail to start and / or load data types and run.","@l":"Warning","NodeId":16937,"EditorAlias":"Umbraco.DropDown.Flexible","SourceContext":"Umbraco.Core.Migrations.Upgrade.V_8_0_0.DataTypeMigration",
3. Could not find an editor with alias {EditorAlias}, treating as Label. The site may fail to boot and / or load data types and run.","@l":"Warning","EditorAlias":"Umbraco.FolderBrowser","SourceContext":"Umbraco.Core.Models.DataType"
4.  could not find parent id=7127.","@l":"Warning","SourceContext":"Umbraco.Web.PublishedCache.NuCache.ContentStore","ProcessId":45424,"ProcessName":"iisexpress","ThreadId":70,"AppDomainId":3,

    For above solution I follow one reference link (https://github.com/umbraco/Umbraco-CMS/commit/79159b684dabcbe8b54597691380bb17982285cf)

    and try to implement all property editor class in my App_Code folder and try to run the solution I got below error. enter image description here

    If you have any idea to resolve then tell me so I do next process.

    Thanks in advance.

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 05, 2019 @ 10:12
    Mihir Ajmera
    0

    Hello All,

    I upgrade Umbraco version 7.14.0 to 8.1.4 latest version during content migration I got the below error

    Could not find an editor with alias {EditorAlias}, treating as Label. The site may fail to boot and / or load data types and run.","@l":"Warning","EditorAlias":"Umbraco.FolderBrowser","SourceContext":"Umbraco.Core.Models.DataType","ProcessId":21492,"ProcessName":"iisexpress","ThreadId":134,"AppDomainId":3,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"DEV02","Log4NetLevel":"WARN ","HttpRequestNumber":1,"HttpRequestId":"0be8ec2e-e5b8-424e-9ac3-bbca0ca5faad"}

    when I check in the latest database table Umbraco datatype of Umbraco 8.1.4 then I identify "Umbraco.FolderBrowser" datatype property remove it.

    So, anyone has an idea about how to replace this data type with other so configured properly in the latest version of Umbraco.

    Thanks in advance

    Copy Link
  • Steve Megson 151 posts 1024 karma points MVP c-trib
    Sep 05, 2019 @ 10:36
    Steve Megson
    0

    I don't think you need to replace Umbraco.FolderBrowser with anything. It has effectively been replaced by the Child Items tab in Umbraco 8, so you can just remove the property.

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 06, 2019 @ 04:31
    Mihir Ajmera
    0

    Hi Steve Megson,

    As your suggestion, I remove the property from the data type and re-run the full content migration for only published data but still, I got the same error in the Umbraco version 8.1.4.

    Could not find an editor with alias {EditorAlias}, treating as Label. The site may fail to boot and / or load data types and run.","@l":"Warning","EditorAlias":"Umbraco.FolderBrowser","SourceContext":"Umbraco.Core.Models.DataType","ProcessId":21492,"ProcessName":"iisexpress","ThreadId":134,"AppDomainId":3,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"DEV02","Log4NetLevel":"WARN ","HttpRequestNumber":1,"HttpRequestId":"0be8ec2e-e5b8-424e-9ac3-bbca0ca5faad"}{"@t":"2019-09-05T09:38:13.2715601Z","@mt":"Skip item id=11225, both draft and published data are null.","@l":"Warning","SourceContext":"Umbraco.Web.PublishedCache.NuCache.ContentStore","ProcessId":21492,"ProcessName":"iisexpress","ThreadId":134,"AppDomainId":3,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"DEV02","Log4NetLevel":"WARN ","HttpRequestNumber":1,"HttpRequestId":"0be8ec2e-e5b8-424e-9ac3-bbca0ca5faad"}

    So any other idea you have then tell me so I can implement that solve the issues.

    Thanks in Advance

    Copy Link
  • Mihir Ajmera 32 posts 145 karma points
    Sep 23, 2019 @ 04:58
    Mihir Ajmera
    0

    Hello All,

    I do the full content migration process from Umbraco version 7.14.0 to the latest version 8.1.4. Almost all content migrate properly of multiple languages but during verify content data of one the content picker does not display as selected. When I try to add the content picker from the one existing content node value than its give me below type of errors in the back office.

    Possibly unhandled rejection: {"errorMsg":"Failed to retrieve entity data for ids 1059,umb://document/f26c944d992e401889ad59d2bf290603","data":{"Message":"An error has occurred.","ExceptionMessage":"Multiple actions were found that match the request: \r\nGetByIds on type Umbraco.Web.Editors.EntityController\r\nGetByIds on type Umbraco.Web.Editors.EntityController\r\nGetByIds on type Umbraco.Web.Editors.EntityController","ExceptionType":"System.InvalidOperationException","StackTrace":"   at System.Web.Http.Controllers.ApiControllerActionSelector.ActionSelectorCacheItem.SelectAction(HttpControllerContext controllerContext)\r\n   at System.Web.Http.Controllers.ApiControllerActionSelector.SelectAction(HttpControllerContext controllerContext)\r\n   at Umbraco.Web.WebApi.ParameterSwapControllerActionSelector.SelectAction(HttpControllerContext controllerContext) in d:\\a\\1\\s\\src\\Umbraco.Web\\WebApi\\ParameterSwapControllerActionSelector.cs:line 64\r\n   at System.Web.Http.ApiController.ExecuteAsync(HttpControllerContext controllerContext, CancellationToken cancellationToken)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__15.MoveNext()"},"status":500}

    I try to find out the solution with referring umbraco.controller.js and Umbraco API call in the back office which I identify during the call of below code 

    $scope.model.submit(model);

    Which I give me the above error. If you have any idea about to resolve this error then please help me. I am very stuck about this task.

    Doing numbers of R&D in the google also but no more support found to resolve content picker multiple actions found call.

    Thanks in advance

    Copy Link
  • Nurhak Kaya 53 posts 147 karma points MVP 3x c-trib
    Sep 26, 2022 @ 12:32
    Nurhak Kaya
    0

    Please check Marc Goodson's answer when doing your upgrades, otherwise, you'll most likely get stuck at some point.

    PS: you might still get stuck even if you follow Marc's advice but it is an important advice.

    https://our.umbraco.com/forum/umbraco-8/98873-content-migration-error-from-umbraco-version-7140-to-810#comment-340999

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft