Fails to run unattended upgrade on SQLite database

[bjarnef]

Which Umbraco version are you using?

16.3.1

Bug summary

After pull of v16.3.1 upgrade on Umbraco Cloud (from v16.2.0) to local environment, I can't boot the site because of the following:

Umbraco.Cms.Core.Exceptions.BootFailedException: An error occurred while running the unattended upgrade.\nThe database configuration failed with the following message: SQLite Error 19: 'UNIQUE constraint failed: umbracoNode.uniqueId'.

{"@t":"2025-10-21T14:09:38.3402590Z","@mt":"Connection ID \"{ConnectionId}\", Request ID \"{TraceIdentifier}\": An unhandled exception was thrown by the application.","@l":"Error","@x":"Umbraco.Cms.Core.Exceptions.BootFailedException: Boot failed: Umbraco cannot run. See Umbraco's log file for more details.\n\n-> Umbraco.Cms.Core.Exceptions.BootFailedException: An error occurred while running the unattended upgrade.\nThe database configuration failed with the following message: SQLite Error 19: 'UNIQUE constraint failed: umbracoNode.uniqueId'.\n Please check log file for additional information (can be found in 'LoggingSettings.Directory')\n\n-> Umbraco.Cms.Core.Exceptions.UnattendedInstallException: An error occurred while running the unattended upgrade.\nThe database configuration failed with the following message: SQLite Error 19: 'UNIQUE constraint failed: umbracoNode.uniqueId'.\n Please check log file for additional information (can be found in 'LoggingSettings.Directory')\r\n   at Umbraco.Cms.Core.Exceptions.BootFailedException.Rethrow(BootFailedException bootFailedException)\r\n   at Umbraco.Cms.Web.Common.Middleware.BootFailedMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)\r\n   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n   at SixLabors.ImageSharp.Web.Middleware.ImageSharpMiddleware.Invoke(HttpContext httpContext, Boolean retry)\r\n   at Umbraco.Forms.Web.HttpModules.ProtectFormUploadRequestsMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)\r\n   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n   at Umbraco.Cms.Api.Management.Middleware.BackOfficeAuthorizationInitializationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)\r\n   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n   at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware.InvokeAsync(HttpContext context)\r\n   at Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware.InvokeAsync(HttpContext context)\r\n   at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()","@tr":"8e1d4dc8083bd77dabcc50635940716d","@sp":"917974c36ba4168f","ConnectionId":"16068843493543379801","TraceIdentifier":"8000035a-0005-df00-b63f-84710c7967bb","EventId":{"Id":2,"Name":"ApplicationError"},"SourceContext":"Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer","RequestId":"8000035a-0005-df00-b63f-84710c7967bb","RequestPath":"/","ProcessId":27540,"ProcessName":"iisexpress","ThreadId":4,"ApplicationId":"7c10f8137e71d03f1f6c383c78d7b5c177e90eed","MachineName":"LAPTOP-BF","Log4NetLevel":"ERROR"}

Specifics

No response

Steps to reproduce

Run upgrade from 16.2.0 to 16.3.1 using SQLite database.

Expected result / actual result

No response

[github-actions]

Hi there @bjarnef!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[bjarnef]

I have the following {A917FCBC-C378-4A08-A36C-220C581A6581} for Umbraco.Core.Upgrader.State+Umbraco.Core in umbracoKeyValue table:

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

Line 128 in caeb345

To<V_16_3_0.AddRichTextEditorCapabilities>("{A917FCBC-C378-4A08-A36C-220C581A6581}");

And it has {5ECCE7A7-2EFC-47A5-A081-FFD94D9F79AA} from latest pre migration:

Umbraco-CMS/src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPremigrationPlan.cs

Line 75 in caeb345

To<V_16_2_0.AddDocumentUrlLock>("{5ECCE7A7-2EFC-47A5-A081-FFD94D9F79AA}");

So it seems it fails somewhere in MigrateMediaTypeLabelProperties migration in SQLite database:

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

Line 129 in caeb345

To<V_16_3_0.MigrateMediaTypeLabelProperties>("{FB7073AF-DFAF-4AC1-800D-91F9BD5B5238}");

https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Infrastructure/Migrations/Upgrade/V_16_3_0/MigrateMediaTypeLabelProperties.cs

[bjarnef]

For now I am using LocalDB on local environment instead:

"Deploy": {
  "Settings": {
    "PreferLocalDbConnectionString": true
  }
}

[AndyButland]

Run upgrade from 16.2.0 to 16.3.1 using SQLite database.

This doesn't seem to be enough to replicate it. I've tried doing this upgrade starting with e clean 16.2, and don't see the problem.

It there any chance to see a copy of the 16.2 database either before or after it has failed to boot please?

If not, or actually perhaps better as a first step, could you query it to see what's found on these statements please?

select * from umbracoNode where id = -104
select * from umbracoNode where id = -105
select * from umbracoNode where uniqueId = '5EB57825-E15E-4FC7-8E37-FCA65CDAFBDE'
select * from umbracoNode where uniqueId = 'BA5BDBE6-AB3E-46A8-82B3-2C45F10BC47F'

[bjarnef]

@AndyButland can I invite you to the Umbraco Cloud project, so you can try reproduce?

[AndyButland]

Sure, thanks. But I think I would need your local 16.2 database that you are upgrading when you pull, as I would only be able to do a clean clone of your Cloud project which wouldn't be replicating the problem. So could you first try those queries please?

[bjarnef]

@AndyButland I don't get a record for the first two, but a record for each of the last two commands:

select * from umbracoNode where uniqueId = '5EB57825-E15E-4FC7-8E37-FCA65CDAFBDE'

select * from umbracoNode where uniqueId = 'BA5BDBE6-AB3E-46A8-82B3-2C45F10BC47F'

I have invited you to the Umbraco Cloud project.
Perhaps you can try cloning development environment using SQLite db, and see if you can reproduce?

[AndyButland]

OK, thanks. So I think what's going on is that the update on your Could environment has created the new data types, generating .uda files for Deploy, and when you have restored locally Deploy created them from the .uda files. However it's done so with different integer IDs.

So when the CMS migration runs it doesn't find the expected integer IDs and tries to create these items again.

I think the issue is that we shouldn't be relying on integer IDs for the CMS migration check if these data types already exist.

[AndyButland]

Fixed via #20604 for 16.3.3 (I think we should patch this, as it's a regression from 16.2) and 17.0.