Hello Everyone,
I am new to umbraco and been trying install it in my project using Nuget (Umbraco 7.5.10) for the first time. I am using VS2015 and SQL 2008 R2. My project is an Empty Web Application(MVC). During installation, I always encounter 'invalid column name uniqueID' error. After going through the log, I understand the error is been encountered in BusinessLogic.
Kindly help me out to solve this or if anyone knows any link where the solution is already provided, kindly let me know.
Just posting this so, anybody stuck with the same issue finds it useful.
The problem was that back end libraries were upgraded while .Net package was updated. But db also needs some corresponding changes. Ideally .Net upgrade should update the tables before trying to fetch data and parse it. However that's not the case and hence we have to do it manually.
Here's the script i ran to add "uniqueId" column in a couple of tables, where the backend expects them.
ALTER TABLE [dbo].[cmsPropertyType]
Add UniqueID uniqueidentifier NOT NULL DEFAULT (NEWID()) WITH VALUES
ALTER TABLE [dbo].[cmsPropertyTypeGroup]
Add uniqueID uniqueidentifier NOT NULL DEFAULT (NEWID()) WITH VALUES
Invalid uniqueID error
Hello Everyone, I am new to umbraco and been trying install it in my project using Nuget (Umbraco 7.5.10) for the first time. I am using VS2015 and SQL 2008 R2. My project is an Empty Web Application(MVC). During installation, I always encounter 'invalid column name uniqueID' error. After going through the log, I understand the error is been encountered in BusinessLogic.
Kindly help me out to solve this or if anyone knows any link where the solution is already provided, kindly let me know.
Thanks.
Hello Everyone,
I have solved the issue. Thanks to the new release (7.5.11). Also I have used SQL Server 2012 instead of SQL Server 2008 R2.
Hi Monalisa,
I'm getting the same error while i was upgrading umbraco from 7.2.8 to 7.5.11.
Did you do a fresh installation? Or what was your strategy for upgrade?
Thanks,
Hi,
Just posting this so, anybody stuck with the same issue finds it useful.
The problem was that back end libraries were upgraded while .Net package was updated. But db also needs some corresponding changes. Ideally .Net upgrade should update the tables before trying to fetch data and parse it. However that's not the case and hence we have to do it manually.
Here's the script i ran to add "uniqueId" column in a couple of tables, where the backend expects them.
Hope this helps!
is working on a reply...