Upgrade 13.7.0 to 16.2.0

Questions
,
1

I have an Umbraco Cloud solution running Umbraco 13.7.0
I want to upgrade to 16.2.0 (actually want to upgrade to v17 when it comes out, but I thought upgrading to 16 now would save time later).

I have backed up the DB from the Umbraco Cloud, and “restored” it locally in my SQL Server.
I have installed a clean Umbraco 16.2.0 solution locally, and pointed it at my new local database.

When I run the solution I get the following error, which I have no idea what it means. Anyone know?

Umbraco.Cms.Core.Exceptions.BootFailedException: An error occurred while running the unattended upgrade.
The database configuration failed with the following message: LockObject with id=-345 does not exist.

2

Just to make sure, I really would upgrade Umbraco 13 to the latest version first.

1 Like
3

Thanks for the reply. You mean update the running Live environment to CMS 13.10.0, backup the DB again, and try my local upgrade to 16.2.0?

So I tried that locally - installed a clean Umbraco 13.10.0, pointed it at my local database (backed up from the 13.7.0 Live db). Now I get error:

Umbraco.Cms.Core.Exceptions.BootFailedException: An error occurred while running the unattended upgrade.
The database configuration failed with the following message: The migration plan does not support migrating from state “{1A8835EF-F8AB-4472-B4D8-D75B7C164022}”

4

Are you sure you didn’t accidentally try to upgrade to Umbraco 15+ on the database you are using? The GUID of that migration state seems to come from Umbraco 15+.

5

Yes, if I restart the local Umbraco installation (this time using a default sqlite db) I can start the backoffice:

image
image256×289 6.82 KB

6

Hi,

There is a known issue with the migration when upgrading the database from 13.x to 16.2.0

Try to upgrade to 16.1.1 instead and it should work.

See the Github Issue for more information: Error upgrading from Umbraco 13 to 16: LockObject with id=-344 does not exist. · Issue #20037 · umbraco/Umbraco-CMS · GitHub

1 Like
7

Thanks for the info. I could indeed upgrade to 16.1.1

1 Like
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.