U4-10080 - Upgrade from 7.2.8 to 7.6.3 timeout, upgrade keeps running indefinitely

Created by Matija Grcic 29 Jun 2017, 18:51:20 Updated by Marcin Zajkowski 06 Mar 2018, 08:18:28

I've upgraded Umbraco from 7.2.8 (https://our.umbraco.org/contribute/releases/728/) to 7.6.3 (https://our.umbraco.org/contribute/releases/763/) per https://our.umbraco.org/documentation/getting-started/setup/upgrading/version-specific.

Apart from slight issues with the IX_umbracoNodeUniqueID which I managed to solve by applying the https://github.com/umbraco/Umbraco-CMS/pull/2001/commits/33f76d25f7bed97594647822065b58e91b60e8d7 all was fine.

The problem is that the upgrade process stops at the following lines and nothing is logged to the UmbracoTraceLog file after

2017-06-29 19:22:20,088 [P21076/D28/T96] INFO Umbraco.Core.Persistence.Migrations.MigrationRunner - Executing sql statement 560: CREATE TABLE [umbracoLock] ([id] INTEGER NOT NULL, [value] INTEGER NOT NULL, [name] NVARCHAR(64) NOT NULL)

2017-06-29 19:22:20,091 [P21076/D28/T96] INFO Umbraco.Core.Persistence.Migrations.MigrationRunner - Executing sql statement 561: ALTER TABLE [umbracoLock] ADD CONSTRAINT [PK_umbracoLock] PRIMARY KEY CLUSTERED ([id])

2017-06-29 19:22:28,578 [P21076/D28/T96] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-06-29 19:22:28,579 [P21076/D28/T96] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms) 2017-06-29 19:22:28,579 [P21076/D28/T96] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IParameterEditor 2017-06-29 19:22:28,582 [P21076/D28/T96] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IParameterEditor (took 2ms)

What did you expect to happen?

I've expected an error logged or exception thrown.

What actually happened?

Upgrade process keeps running indefinitely NOTE: I've tried increasing the timeout in the connection string.

Any help would be appreciated.


Matija Grcic 29 Jun 2017, 21:28:51

Never mind, you can delete this. Managed to find the issue and after a 3 hours upgrade process it's now done.

Marcin Zajkowski 06 Mar 2018, 08:18:28

@mgrcic what was the issue then? One of our clients is experiencing exactly the same problem. Would love to hear your thoughts and steps made to fix it.

Priority: Normal

Type: Bug

State: Submitted


Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:


Story Points: