When it comes to upgrading Umbraco are we able to jump from latest LTS of 13 (13.14) to the latest V17.3.5?
When I try the upgrade fails with:
The database failed to upgrade. ERROR: The database configuration failed with the following message: LockObject with id=-344 does not exist.
I have two different Umbraco sites but both have the same error. Do we need to update each individual version 14,15,16 to 17?
From what it said here: Upgrade Details | CMS | Umbraco Documentation
My impression was upgrade is supported from LTS major versions so I thought jumping from latest V13 to latest V17 would be ok?
Hi @deanparkr ,
*Take a database backup before running anything *
Jumping directly from 13.14 to 17.x is supported, you don’t need to step through every major version in between.
What you’re hitting is a known bug. When the migration runs RebuildDocumentUrls (a step introduced in the v15 migration chain), it tries to acquire a write lock on records that haven’t been inserted into umbracoLock yet at that point in time. The lock records for DocumentUrls and LongRunningOperations are introduced later in the plan, but the migration needs them earlier — classic ordering issue.
The GitHub issue tracking it is here: https://github.com/umbraco/Umbraco-CMS/issues/20037 and the workaround is in the comments there. The exact SQL is referenced in the issue comments by Andy Butland from the core team, it’ll get you past this.
This was fixed in 16.3.0, so you’d hope v17.3.5 had inherited it, but clearly something still causes this to surface on certain upgrade paths from v13. Worth commenting on that GitHub issue if you can confirm it’s still reproducible on 17.3.5 specifically.
Either way, the workaround gets you moving and the upgrade should complete cleanly after that. Same applies to both of your sites.
4 Likes