The database failed to upgrade. ERROR: The database configuration failed with the following message: 'FK_umbracoRedirectUrl_umbracoNode_uniqueID' is not a constraint. Could not drop constraint.
I have checked my database and indeed this constraint does not exist. I have tried creating it myself using the following SQL:
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_umbracoRedirectUrl_umbracoNode_uniqueID". The conflict occurred in database "NesspointUmbraco", table "dbo.umbracoNode", column 'uniqueId'.
I also have this problem, unable to go from 8.14.1 to 8.15.0 or 8.15.1.
ERROR: The database configuration failed with the following message:
'FK_umbracoRedirectUrl_umbracoNode_uniqueID' is not a constraint.
Could not drop constraint.
ALTER TABLE umbracoRedirectUrl WITH NOCHECK
ADD CONSTRAINT FK_umbracoRedirectUrl_umbracoNode_uniqueID CHECK (contentKey <> '') ;
The installation seems to go over this problem, but shows another problem:
The database failed to upgrade. ERROR: The database configuration failed with the following message:
An explicit DROP INDEX is not allowed on index 'umbracoNode.IX_umbracoNode_UniqueId'.
It is being used for UNIQUE KEY constraint enforcement.
Seems, as if the Upgrade to 8.15.x has some severe flaws.
EDIT: I only see now, that @Sam tried the same thing and failed as well.
Thanks, this worked for me too. Here is the exact SQL I used:
ALTER TABLE umbracoRedirectUrl WITH NOCHECK
ADD CONSTRAINT FK_umbracoRedirectUrl_umbracoNode_uniqueID CHECK (contentKey <> '') ;
ALTER TABLE umbracoNode
DROP CONSTRAINT IX_umbracoNode_UniqueId
I added the constraint like shown above in my first post. Don't add the constraint the same way it was originally intended, because it will block a following DROP INDEX statement.
I removed the Index IX_umbracoNode_UniqueId of the umbracoNode table manually.
To recap the Solution: If you execute the following lines in SSMS, the database update continues without errors.
ALTER TABLE umbracoRedirectUrl WITH NOCHECK
ADD CONSTRAINT FK_umbracoRedirectUrl_umbracoNode_uniqueID CHECK (contentKey <> '') ;
ALTER TABLE umbracoNode
DROP CONSTRAINT IX_umbracoNode_UniqueId
Cant upgrade from Umbraco 8.14.1 to 8.15.1
When I try to upgrade I get the following error:
I have checked my database and indeed this constraint does not exist. I have tried creating it myself using the following SQL:
This also gives an error:
Any help would be greatly apprciated.
Hello,
Please read the below article, It's may help you.
https://www.gitmemory.com/issue/umbraco/Umbraco-CMS/10693/881426531
I have the same problem but from version 8.9.1 to 8.15.1, getting the same error as mentioned above.
I have the same problem from 8.10.2 to 8.15.1.
We also have this exact problem updating from 8.13.0 to 8.15.1.
Same when updating from 8.8.0 to 8.15.1
Edit: Tried updating to 8.10 - worked
Updated to 8.12 - worked
Updated to 8.14 - worked
Updated to 8.15 or 8.15.1 - I get the above constraint error.
DB is Azure, with no custom class code/routing.
I also have this problem, unable to go from 8.14.1 to 8.15.0 or 8.15.1.
Same error here upgrading from 8.13.0 to 8.15.1
Same here 8.14.1 -> 8.15.2. Any insights?
I created a fake constraint like that:
The installation seems to go over this problem, but shows another problem:
Seems, as if the Upgrade to 8.15.x has some severe flaws.
EDIT: I only see now, that @Sam tried the same thing and failed as well.
Thanks, this worked for me too. Here is the exact SQL I used:
This worked for me. Had the same error trying to upgrade from 8.13 to 8.16. Thank you!
That's how I managed the upgrade:
I added the constraint like shown above in my first post. Don't add the constraint the same way it was originally intended, because it will block a following DROP INDEX statement.
I removed the Index
IX_umbracoNode_UniqueIdof the umbracoNode table manually.After that the upgrade completed.
This solution worked for me aswell, thank you!
@Patrik: Glad to hear that!
Same with 8.14.3 to 8.16..
To recap the Solution: If you execute the following lines in SSMS, the database update continues without errors.
is working on a reply...