Copied to clipboard

Flag this post as spam?

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


  • Jeroen Breuer 4908 posts 12265 karma points MVP 4x admin c-trib
    Feb 02, 2022 @ 10:58
    Jeroen Breuer
    0

    The migration plan does not support migrating from state.

    Hello,

    A small team at our company is currently trying some new things with Umbraco. Since the project is only used for experimenting we have a shared database.

    One of the team members upgraded the project to Umbraco 9.2. I can see the database has been upgrade because when I check the umbracoKeyValue table it has the following data:

    Key Umbraco.Core.Upgrader.State+Umbraco.Core

    Value ad3d3b7f-8e74-45a4-85db-7ffad57f9243

    By checking the UmbracoPlan GUID you can see this GUID is for the 9.2 upgrade: https://github.com/umbraco/Umbraco-CMS/blob/v9/contrib/src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPlan.cs#L271

    The developer upgraded to 9.2, but somehow the NuGet packages didn't get upgraded. So the database thinks it's on 9.2, but dlls are still on 9.1.1.

    I upgraded the NuGet packages to 9.2, but somehow it still tries to run the migration. I've got screenshots, but I can't upload them because our gives an error. So here is the text:

    Screen 1

    Detected current version (ad3d3b7f), which needs to be upgraded to 9.2.0 (ad3d3b7f). To compare versions and read a report of changes between versions, use the View Report button below.

    Screen 2

    The database failed to upgrade. ERROR: The database configuration failed with the following message: The migration plan does not support migrating from state "ad3d3b7f-8e74-45a4-85db-7ffad57f9243". Please check log file for additional information (can be found in '~/umbraco/Logs')

    I've checked the dlls in the bin folder and they are on 9.2 now.

    Can I somehow skip the migration? I don't need it to run again.

    Jeroen

  • Corné Hoskam 80 posts 587 karma points MVP 2x c-trib
    Feb 02, 2022 @ 12:35
    Corné Hoskam
    0

    Hi Jeroen,

    Have you tried removing the KeyValue from the database table, and re-running the migration? Looking at the code it doesn't seem like a exciting migration!

    https://github.com/umbraco/Umbraco-CMS/blob/8eb3ef65f686619d09af478bd6fd563fc90580b2/src/Umbraco.Infrastructure/Migrations/Upgrade/V_9_2_0/AddDefaultForNotificationsToggle.cs
    

    Kind regards,

    Corné

  • Jeroen Breuer 4908 posts 12265 karma points MVP 4x admin c-trib
    Feb 02, 2022 @ 12:56
    Jeroen Breuer
    0

    Hi Corne,

    Yes I already tried that. It gives the same error. By removing the value from the table it doesn't know what the current version is so it doesn't know what it needs to upgrade.

    Since something might have gone wrong with the upgrade I also tried upgrading to Umbraco 9.3-RC, but it gives the same exception:

    Screen 1:

    Detected current version (ad3d3b7f), which needs to be upgraded to 9.3.0-rc (0828f206). To compare versions and read a report of changes between versions, use the View Report button below.

    Screen 2:

    The database failed to upgrade. ERROR: The database configuration failed with the following message: The migration plan does not support migrating from state "AD3D3B7F-8E74-45A4-85DB-7FFAD57F9243". Please check log file for additional information (can be found in '~/umbraco/Logs')

    I thought this would work because it tries to upgrade from 9.2 to 9.3 RC which is supported by the migrations.

    Jeroen

  • Jeroen Breuer 4908 posts 12265 karma points MVP 4x admin c-trib
    Feb 02, 2022 @ 13:03
    Jeroen Breuer
    0

    Hi Corne,

    This is the error I get when the NuGet packages are upgraded to 9.2 and the row is removed from the KeyValue table:

    The database failed to upgrade. ERROR: The database configuration failed with the following message: Version 9.2.0+763cb70e677ac0c85557b19b5df09eccfa1b9dfb does not support migrating from 9.2.0+763cb70e677ac0c85557b19b5df09eccfa1b9dfb. Please verify which versions support migrating from 9.2.0+763cb70e677ac0c85557b19b5df09eccfa1b9dfb. Please check log file for additional information (can be found in '~/umbraco/Logs')

    Jeroen

  • Jeroen Breuer 4908 posts 12265 karma points MVP 4x admin c-trib
    Feb 02, 2022 @ 13:25
    Jeroen Breuer
    100

    Hello,

    I found the solution. The problem was a wrong value in umbracoKeyValue table. Probably because I did some editing in the table the values didn't match anymore.

    Here is the current value:

    Key Umbraco.Core.Upgrader.State+Umbraco.Core

    Value {AD3D3B7F-8E74-45A4-85DB-7FFAD57F9243}

    It's very important that { } is also there. Otherwise it's not a match.

    So if anyone ever runs into the same issue.

    1. Check what the current version is in the UmbracoPlan code. The GUID value in the umbracoKeyValue (Umbraco.Core.Upgrader.State+Umbraco.Core) table should be in there.
    2. Make sure that your NuGet packages and dlls are the same version as that of the version you find in step 1.
    3. If the versions don't match you can do a NuGet upgrade. Make sure you don't delete or manually change the value in the umbracoKeyValue table. They need an exact match.

    So this problem can happen if the database is further ahead in version than your local environment (which can happen with a shared db). It will try to run a migration from 9.2 to 9.1.1 which it can't find.

    Jeroen

  • Cedeste 37 posts 129 karma points
    May 31, 2023 @ 12:46
    Cedeste
    0

    Do you happen to know what the value should be for 11.1. or 11.2?

  • Pierre Bourgeois 1 post 71 karma points
    Jan 20, 2023 @ 19:10
    Pierre Bourgeois
    0

    Hello,

    I'm running into a very similar problem trying to upgrade from 9.2.0 to 10.3.2.

    We have 4 environnements: DEV, INTEGRATION, STAGING and Production. All with Umbraco 9.3.2.

    First I upgraded from Localhost, published and transfered the published folder to DEV. The upgrade in DEV went smoothly. From DEV, I transferred the files to INTEGRATION. Again all went well.

    INTEGRATION to STAGE went sour. I ran into this problem :

    enter image description here

    I don't need to upgrade to 9.2.0 ! I'm already in 9.2.0. I need to go to 10.3.2

    Then :

    enter image description here

    Any help would be appreciated. Thank you.

  • Steffen Hornbæk Nielsen 43 posts 134 karma points
    May 31, 2023 @ 12:55
    Steffen Hornbæk Nielsen
    0

    Hi Pierre,

    Can you look in the database table umbracoKeyValue and see what state the GUID maches to? Might be a plugin that needs upgrade to the newest 9.x version.

    I encountered the same problem with forms, where i had to upgrade forms to the newest version of 9.x.x before i could upgrade to 10.x.x.

  • Cedeste 37 posts 129 karma points
    May 31, 2023 @ 12:58
    Cedeste
    0

    the umbracoKeyValue table shows

    Umbraco.Core.Upgrader.State+Umbraco.Core {BB3889ED-E2DE-49F2-8F71-5FD8616A2661}

    Umbraco.Web.PublishedCache.NuCache.Serializer MessagePack

    UmbracoAnalyticsLevel Basic

    I don't have any plugins installed - it's a very basic installation.

  • Steffen Hornbæk Nielsen 43 posts 134 karma points
    May 31, 2023 @ 13:00
    Steffen Hornbæk Nielsen
    0

    What about the stage DB and state AD3D3B7F-8E74-45A4-7FFAD57F9243 ?

  • Cedeste 37 posts 129 karma points
    May 31, 2023 @ 13:06
    Cedeste
    0

    Which table would that be located in?

  • Jamie Attwood 201 posts 494 karma points c-trib
    Jul 28, 2023 @ 17:58
    Jamie Attwood
    0

    I am running into the same issue migrating a database from 8.18 to 12.0.1

    I have a fresh 12 installation and trying to use the database from v8.18.

    Getting the error:

    The database configuration failed with the following message: The migration plan does not support migrating from state "{03482BB0-CF13-475C-845E-ECB8319DBE3C}".
    

    Looking in the migration plans here: https://github.com/umbraco/Umbraco-CMS/blob/v9/contrib/src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPlan.cs

    looking into the umbracoKeyValue table I see {03482BB0-CF13-475C-845E-ECB8319DBE3C} which is the correct state of the database for 8.18.

    Unattended installs are set to true but still seeing this failure.

    Are there migrations from 8-12? or do I need to do another upgrade step?

    Any help appreciated!

  • Jamie Attwood 201 posts 494 karma points c-trib
    Aug 01, 2023 @ 20:57
    Jamie Attwood
    0

    And yeah, I was looking at v9 migration plans so I am guessing I need minimum 8-10 and then 10-12 upgrade.

  • Cedeste 37 posts 129 karma points
    Aug 07, 2023 @ 17:05
    Cedeste
    0

    I ended up having to install another version and copy the key value from the new install to my install, and it fixed the issue.

    I'm afraid my versions were newer, so I don't have any advice on the jump that you have. Hopefully, someone else can ring in.

  • Ian Bennett 2 posts 22 karma points
    Dec 04, 2023 @ 15:48
    Ian Bennett
    0

    I'm in the same place and wondering if you had to go 8-9 and then to 12 or straight to 12?

    Thanks for your help

  • Jamie Attwood 201 posts 494 karma points c-trib
    Dec 04, 2023 @ 16:03
    Jamie Attwood
    1

    I had to go highest V8 -> Highest V10 -> Current V12.

    I now maintain a bare-bones v10 project just to handle the migrations. Just point your v10 at the v8 DB, run the upgrade and then point your v12 to the V10 DB and you should be good to go.

    Hope that helps.

    Jamie

  • Ian Bennett 2 posts 22 karma points
    Dec 04, 2023 @ 16:05
    Ian Bennett
    0

    That's great, thanks for the pointer

  • Eranga Wijethunga 31 posts 172 karma points
    5 days ago
    Eranga Wijethunga
    0

    This is great, Worked for me

  • Brandon Osborne 38 posts 161 karma points c-trib
    Jan 22, 2024 @ 19:33
    Brandon Osborne
    0

    I encountered this error unexpectedly on a website that hadn't been upgraded or even changed in months. After reading through lots of posts, I found that in my instance, deleting the offending record from the umbracoKeyValue table remedied the problem.

  • andrew shearer 506 posts 653 karma points
    Mar 11, 2024 @ 23:47
    andrew shearer
    0

    really unfortunate that Umbraco hasn't retained all of the internal migrations that allow going from 8 to 13 in one go. We've had to go via 10 i.e. 8 to 10 to 13 😞

Please Sign in or register to post replies

Write your reply to:

Draft