Database to be upgraded states its on v16, and it should be v13

BlagoCuljak · October 7, 2025, 8:56am

I am trying to upgrade v13 to v16.

Is states faulty that current version is v16, and it’s not. After I do upgrade, my media nodes and blocklists, all fail to load with JSON errors.

This might be due to this version mismatch, and might not.

mistyn8 · October 7, 2025, 9:08am

The version reported in v16 upgrades seems to be wrong.. as the key there is for a v13…

BlagoCuljak · October 7, 2025, 9:11am

Hi, Mike, what key should I set in Database to resolve it as v13?

I get this kinda logs:

[10:53:28 INF] At {E261BF01-2C7F-4544-BAE7-49D545B21D68}
[10:53:28 INF] Execute AddEditorUiToDataType
[10:53:32 WRN] No migration data was found for the data editor split for data type Media Picker (Umbraco.MediaPicker - 1048). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:32 WRN] No migration data was found for the data editor split for data type Multiple Media Picker (Umbraco.MediaPicker - 1049). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:38 WRN] No migration data was found for the data editor split for data type Garantie - Upload document - Media Picker (Umbraco.MediaPicker - 10837). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:38 WRN] No migration data was found for the data editor split for data type Garantie - Upload Document - Media Picker (1) (Umbraco.MediaPicker - 10838). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:40 WRN] No migration data was found for the data editor split for data type SignUp - Image Block - Media Picker (Umbraco.MediaPicker - 10852). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:40 WRN] No migration data was found for the data editor split for data type Status - Profile Image Placeholder - Media Picker (Umbraco.MediaPicker - 10854). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:40 WRN] No migration data was found for the data editor split for data type Status - Profile Placeholder - Media Picker (Umbraco.MediaPicker - 10855). Please make sure you’re upgrading from the latest V13. The affected data type may not work correctly.
[10:53:46 INF] At {5A2EF07D-37B4-49D5-8E9B-3ED01877263B}
[10:53:46 INF] Execute AddEditorUiToDataType
[10:53:47 INF] At {6FB5CA9E-C823-473B-A14C-FE760D75943C}
[10:53:47 INF] Execute CleanUpDataTypeConfigurations
[10:53:48 INF] Configuration cleaned up for data type: Dropdown (id: -42, editor alias: Umbraco.DropDown.Flexible)
[10:53:48 INF] Configuration cleaned up for data type: Dropdown multiple (id: -39, editor alias: Umbraco.DropDown.Flexible)
[10:53:48 INF] Configuration cleaned up for data type: Homepage - Partner ID - Numeric (id: 1088, editor alias: Umbraco.Integer)
[10:53:48 INF] Configuration cleaned up for data type: Homepage - Search Tasks - Textbox (id: 1129, editor alias: Umbraco.TextBox)
[10:53:48 INF] Configuration cleaned up for data type: Homepage - Commission - Decimal (id: 7945, editor alias: Umbraco.Decimal)
[10:53:49 INF] Configuration cleaned up for data type: Blog - numberOfItemsPerPage - Decimal (id: 8259, editor alias: Umbraco.Decimal)
[10:53:49 INF] Configuration cleaned up for data type: Team - Textarea (id: 8298, editor alias: Umbraco.TextArea)
[10:53:49 INF] Configuration cleaned up for data type: Klus - Base rate - Decimal (id: 10387, editor alias: Umbraco.Decimal)
[10:53:49 INF] Configuration cleaned up for data type: Color Picker (id: 10833, editor alias: Umbraco.ColorPicker)
[10:53:49 INF] Configuration cleaned up for data type: Klus - Average Price - Decimal (id: 10845, editor alias: Umbraco.Decimal)
[10:53:49 INF] Configuration cleaned up for data type: Blog Article - Sticky CTA Task ID - Numeric (id: 11163, editor alias: Umbraco.Integer)
[10:53:49 INF] Configuration cleaned up for data type: Blog Article - Sticky CTA Task ID - Numeric (1) (id: 11182, editor alias: Umbraco.Integer)
[10:53:49 INF] Configuration cleaned up for data type: Blog Article - stickyCTATaskID - Textbox (id: 11351, editor alias: Umbraco.TextBox)
[10:53:49 INF] Configuration cleaned up for data type: Blog Article - stickyCTAText - Textbox (id: 11352, editor alias: Umbraco.TextBox)
[10:53:49 INF] Configuration cleaned up for data type: Blog Article - stickyCTATaskID - Textbox (1) (id: 11360, editor alias: Umbraco.TextBox)
[10:53:50 INF] Configuration cleaned up for data type: Blog Article - stickyCTATaskID - Textbox (2) (id: 11361, editor alias: Umbraco.TextBox)
[10:53:50 INF] Configuration cleaned up for data type: Blog Article - stickyCTATaskID - Textbox (3) (id: 11379, editor alias: Umbraco.TextBox)
[10:53:50 INF] Configuration cleaned up for data type: Team - Textarea (1) (id: 11547, editor alias: Umbraco.TextArea)
[10:53:50 INF] Configuration cleaned up for data type: Block list - Media Picker (id: 16049, editor alias: Umbraco.MediaPicker3)
[10:53:50 INF] Configuration cleaned up for data type: Homepage - Trustpilot stars image - Media Picker (id: 19224, editor alias: Umbraco.MediaPicker3)
[10:53:50 INF] Configuration cleaned up for data type: Homepage - Consumer App Mobile Image - Media Picker (id: 19225, editor alias: Umbraco.MediaPicker3)
[10:53:50 INF] Configuration cleaned up for data type: Homepage - Consumer App Desktop Image - Media Picker (id: 19226, editor alias: Umbraco.MediaPicker3)

I am upgrading from 13.10 version

mistyn8 · October 7, 2025, 9:23am

Last v13 db migration was still that 13.5.0 one Umbraco-CMS/src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPlan.cs at b4e97ea49f7f14e79f3fe2619cda4b1de3f0c5af · umbraco/Umbraco-CMS · GitHub

So your DB if it should still be a v13 would have the CC47C751-A81B-489A-A2BC-0240245DB687

First migration plan key in that log {E261BF01-2C7F-4544-BAE7-49D545B21D68}

github.com/umbraco/Umbraco-CMS

src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPlan.cs

b4e97ea49


      
          To<V_14_0_0.UpdateDefaultGuidsOfCreatedPackages>("{E073DBC0-9E8E-4C92-8210-9CB18364F46E}");
          To<V_14_0_0.RenameTechnologyLeakingPropertyEditorAliases>("{80D282A4-5497-47FF-991F-BC0BCE603121}");
          To<V_14_0_0.MigrateSchduledPublishesToUtc>("{96525697-E9DC-4198-B136-25AD033442B8}");
          To<NoopMigration>("{7FC5AC9B-6F56-415B-913E-4A900629B853}");
          To<V_14_0_0.MigrateDataTypeConfigurations>("{1539A010-2EB5-4163-8518-4AE2AA98AFC6}");
          To<NoopMigration>("{C567DE81-DF92-4B99-BEA8-CD34EF99DA5D}");
          To<V_14_0_0.DeleteMacroTables>("{0D82C836-96DD-480D-A924-7964E458BD34}");
          To<V_14_0_0.MoveDocumentBlueprintsToFolders>("{1A0FBC8A-6FC6-456C-805C-B94816B2E570}");
          To<NoopMigration>("{302DE171-6D83-4B6B-B3C0-AC8808A16CA1}");
          To<V_14_0_0.MigrateUserGroup2PermissionPermissionColumnType>("{8184E61D-ECBA-4AAA-B61B-D7A82EB82EB7}");
          To<V_14_0_0.MigrateNotificationCharsToStrings>("{E261BF01-2C7F-4544-BAE7-49D545B21D68}");
          To<V_14_0_0.AddEditorUiToDataType>("{5A2EF07D-37B4-49D5-8E9B-3ED01877263B}");
          // we need to re-run this migration, as it was flawed for V14 RC3 (the migration can run twice without any issues)
          To<V_14_0_0.AddEditorUiToDataType>("{6FB5CA9E-C823-473B-A14C-FE760D75943C}");
          To<V_14_0_0.CleanUpDataTypeConfigurations>("{827360CA-0855-42A5-8F86-A51F168CB559}");
          
          // To 14.1.0
          To<V_14_1_0.MigrateRichTextConfiguration>("{FEF2DAF4-5408-4636-BB0E-B8798DF8F095}");
          To<V_14_1_0.MigrateOldRichTextSeedConfiguration>("{A385C5DF-48DC-46B4-A742-D5BB846483BC}");
          
          // To 14.2.0

and then subsequent plan guids in those logs are just the migration plans running on your v13 db in the process of moving it up to v16…

But if you started a v16 upgrade and it failed somewhere after the log you’ve posted then if that’s the case you will have to restore your DB back to the previous v13 version from a backup (you can’t simply downgrade)

BlagoCuljak · October 7, 2025, 10:01am

@mike I have added your guid to umbracoKeyValue, and here is starting point for migations.
[11:56:31 INF] Acquiring MainDom.
[11:56:31 INF] Acquired MainDom.
[11:56:34 INF] Found AWS credentials for the profile default
[11:56:35 INF] Database upgrade started
[11:56:35 INF] Starting ‘Umbraco.Core.Premigrations’…
[11:56:35 INF] At origin
[11:56:35 INF] Execute UpdateToOpenIddictV5
[11:56:36 INF] At {76FBF80E-37E6-462E-ADC1-25668F56151D}
[11:56:36 INF] Execute AddGuidsToUserGroups
[11:56:36 INF] Executed DbCommand (96ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
SELECT 1
[11:56:36 INF] Acquiring an exclusive lock for migration application. See Migrations Overview - EF Core | Microsoft Learn for more information if this takes too long.
[11:56:36 INF] Executed DbCommand (91ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
DECLARE @result int;
EXEC @result = sp_getapplock @Resource = ‘__EFMigrationsLock’, @LockOwner = ‘Session’, @LockMode = ‘Exclusive’;
SELECT @result
[11:56:37 INF] Executed DbCommand (84ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
IF OBJECT_ID(N’[__EFMigrationsHistory]‘) IS NULL
BEGIN
CREATE TABLE [__EFMigrationsHistory] (
[MigrationId] nvarchar(150) NOT NULL,
[ProductVersion] nvarchar(32) NOT NULL,
CONSTRAINT [PK___EFMigrationsHistory] PRIMARY KEY ([MigrationId])
);
END;
[11:56:37 INF] Executed DbCommand (84ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
SELECT 1
[11:56:37 INF] Executed DbCommand (85ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
SELECT OBJECT_ID(N’[__EFMigrationsHistory]‘);
[11:56:37 INF] Executed DbCommand (85ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
SELECT [MigrationId], [ProductVersion]
FROM [__EFMigrationsHistory]
ORDER BY [MigrationId];
[11:56:37 INF] Applying migration ‘20240403140654_UpdateOpenIddictToV5’.
[11:56:37 INF] Executed DbCommand (177ms) [Parameters=, CommandType=‘Text’, CommandTimeout=‘30’]
EXEC sp_rename N’[umbracoOpenIddictApplications].[Type]‘, N’ClientType’, ‘COLUMN’;
…

mistyn8 · October 7, 2025, 10:21am

Not sure what you are asking.. but as mentioned I don’t think you can just revert the migration key in the DB and expect to get the same results..

As the data has already been transformed by the previous migration attempt..

I’d go back to a DB backup of the clean v13.10 db and try the v16 upgrade again.

Sorry I can’t be more help.

mistyn8 · October 8, 2025, 9:11am

PS noticed another post..

Steffen_HK · October 8, 2025, 12:32pm

Upgrading to 16.1.1 instead of 16.2 solved the issue for me.