We have moved to GitHub Issues
Created by Simon Justesen 17 May 2017, 11:26:25 Updated by Sebastiaan Janssen 06 Jun 2017, 11:32:32Tags: Backport Unscheduled
Relates to: U4-9993
I've been trying to upgrade an 7.1 installation to 7.6.1. The install fails due to missing columns in the database (checked with a fresh 7.6.1 install)
Solved some of the errors by manually adding these columns to the db: Column: uniqueID, type: uniqueIdentifier, not null in in table UmbracoPropertyTypeGroup Column: typeUniqueId, type: uniqueIdentifier, not null in table UmbracoRelationType:
Now I'm getting this error, which i'm unable to fix: The database failed to upgrade. ERROR: The database configuration failed with the following message: The index 'IX_umbracoNodeUniqueID' is dependent on column 'uniqueID'. ALTER TABLE ALTER COLUMN uniqueID failed because one or more objects access this column.
Would it be possible to send your database using WeTransfer? If so, you can send it to: firstname.lastname@example.org
@sebastiaan Yes, I'll do that right away
Cool got it, seems like you might be missing things that were added as early as 6.0.0? Has this site been upgraded from 6.0.0 at least?
That's kind of weird, because it has never been on the 6.0-branch (we sorta skipped Umbraco 6 because it wouldn't work within the db restrictions of our host at that time, so we stayed on Umbraco4/MySQL until we decided to use MSSQL). We built it on a fresh 7.0 db as far as I can recall.
No worries, good to know! Which exact version 7.1 are you on currently please?
@sebastiaan Good :) Umbraco version 7.1.0 assembly: 1.0.5206.24609
@sebastiaan if it helps, we are having the exact same problem with 7.2.8. Will try scripting the index, dropping & re-creating.
I had the exact same same problem with and upgrade from 7.2.8 as well (Including missing the uniqueID & typeUniqueId columns). As a quick work around I was able to make create a script of the existing [IX_umbracoNodeUniqueID] Index, delete the index, upgrade and then re-create it. No problems yet, but very early days still.
@dinc5150 tried same, but had another error, which said to check the logs in the ...\App_Data\Logs folder, but there was no error logged, the logging level was set to error. Will restore a backup & try again later.
Confirmed. Cause is: an old migration is using a DTO object to insert some content, but that DTO has been complemented with more columns in a later migration. So when the old migration runs, it tries to write to fields that don't exist (yet). Can be solved by using a temp DTO in the old migration. Looking into it...
Good stuff, removed the
EnableSqlTrace and merged, this works great now for older sites and also still works for newer upgraders.
@sebastiaan Did this fix make it into the nuget release for 7.6.3? I'm upgrading a 7.2.8 umbraco site to 7.6.3, but it fails with the following error.
2017-06-05 13:34:14,009 [P4480/D19/T43] ERROR Umbraco.Web.Install.Controllers.InstallApiController - Installation step DatabaseUpgrade failed. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Umbraco.Web.Install.InstallException: The database failed to upgrade. ERROR: The database configuration failed with the following message: The index 'IX_umbracoNodeUniqueID' is dependent on column 'uniqueID'. ALTER TABLE ALTER COLUMN uniqueID failed because one or more objects access this column. }
Just curious about this as well. trying to upgrade from 7.1.6 to 7.6.3 and received the following: Error during installation
The database failed to upgrade. ERROR: The database configuration failed with the following message: The index 'IX_umbracoNodeUniqueID' is dependent on column 'uniqueID'. ALTER TABLE ALTER COLUMN uniqueID failed because one or more objects access this column. Please check log file for additional information (can be found in '/App_Data/Logs/UmbracoTraceLog.txt')
Also having this issue. Upgrading from 7.0.1 (assembly: 1.0.5095.27251) to 7.6.3 via NuGet.
Anyone able to offer the following information? -ETA on when this fix will make it into a release. -Latest version that does not have this issue (I assume 7.6.0?)
The fix has been merged into 7.6.3 yes. And tested OK. Which is annoying, because apparently, it was not really a fix. Looking into it & re-opening this issue.
We cannot really reopen this issue as it was due in 7.6.3. Discussion moving over to U4-9993.
Backwards Compatible: True
Affected versions: 7.6.1
Due in version: 7.6.3
Sprint: Sprint 60