New to umbraco. I ran an upgrade from SQL CE to a SQL Azure instance using the SQLCEToolbox and export db command. The command ran fine and said exported. I check the azure db and tables / data is present.
I spin up the site locally and got hit with an 'upgrade now' page.
I hit the continue and hit an error immediately
The database failed to upgrade. ERROR: The database configuration failed with the following message: An explicit DROP INDEX is not allowed on index 'umbracoNode.IXumbracoNodeUniqueID'. It is being used for UNIQUE KEY constraint enforcement. Please check log file for additional information (can be found in '/AppData/Logs/UmbracoTraceLog.txt')
I check the trace log and its the same error along with a bunch of columns not in the current schema including things like
databasefirewallrules, id, databasefirewallrules, name, databasefirewallrules, startipaddress, databasefirewallrules, endipaddress, databasefirewallrules, createdate, databasefirewallrules, modifydate, cmsPropertyData, dataDecimal, cmsPropertyTypeGroup, uniqueID, umbracoDeployChecksum, id, umbracoDeploy Checksum, entityType, umbracoDeployChecksum, entityGuid, umbracoDeployChecksum, entityPath, umbracoDeployChecksum, localChecksum, umbracoDeployChecksum, compositeChecksum, umbracoDeployDependency, sourceId, umbracoDeployDependency, targetId, umbracoDeployDependency, mode, umbracoServer, isMaster, cmsPropertyTypeGroup, parentGroupId...
If I just script out a drop/create on the UmbracoNodeUniqueID, will that solve the issue?
ALTER TABLE [dbo].[umbracoNode] DROP CONSTRAINT [IX_umbracoNodeUniqueID]
GO
/****** Object: Index [IX_umbracoNodeUniqueID] Script Date: 4/15/2016 10:30:58 AM ******/
ALTER TABLE [dbo].[umbracoNode] ADD CONSTRAINT [IX_umbracoNodeUniqueID] UNIQUE NONCLUSTERED
(
[uniqueID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
GO
I had this issue and ran the following script against a backup database I had before upgrading to umbraco 7.5.11.
SELECT t.name AS tablename,
SCHEMANAME(schemaid) AS schemaname,
c.name AS columnname
FROM sys.tables AS t
INNER JOIN sys.columns c ON t.OBJECTID = c.OBJECTID
WHERE c.name LIKE '%parentGroupId%'
ORDER BY schemaname, table_name;
This gave me:
cmsPropertyTypeGroup dbo parentGroupId
I then opened the cmsPropertyTypeGroup table in the designer and added the missing column:
parentGroupId int Allow Nulls is checked
upgrade error 7.3 to 7.4.x
New to umbraco. I ran an upgrade from SQL CE to a SQL Azure instance using the SQLCEToolbox and export db command. The command ran fine and said exported. I check the azure db and tables / data is present.
I hit the continue and hit an error immediately
The database failed to upgrade. ERROR: The database configuration failed with the following message: An explicit DROP INDEX is not allowed on index 'umbracoNode.IXumbracoNodeUniqueID'. It is being used for UNIQUE KEY constraint enforcement. Please check log file for additional information (can be found in '/AppData/Logs/UmbracoTraceLog.txt')
If I just script out a drop/create on the UmbracoNodeUniqueID, will that solve the issue?
Argh...
YSOD - Invalid column name 'parentGroupId'.
I updated my web.config to the following:
Advice appreciated. (why do I do these things on Fridays... )
Did you ever get a resolution to this - having the same problem now.
I honestly don't remember. If I had to guess I probably just created the column. Sorry. It has been a long time. Why not upgrade to. 7.5.6?
I had this issue and ran the following script against a backup database I had before upgrading to umbraco 7.5.11.
SELECT t.name AS tablename, SCHEMANAME(schemaid) AS schemaname, c.name AS columnname FROM sys.tables AS t INNER JOIN sys.columns c ON t.OBJECTID = c.OBJECTID WHERE c.name LIKE '%parentGroupId%' ORDER BY schemaname, table_name;
This gave me: cmsPropertyTypeGroup dbo parentGroupId
I then opened the cmsPropertyTypeGroup table in the designer and added the missing column: parentGroupId int Allow Nulls is checked
Now working as expected.. I hope!
is working on a reply...