Upgrading Umbraco 6.1.6 site with uBlogsy to Umbraco 7.0.2
I have just upgraded an Umbraco 6.1.6 site with uBlogsy to Umbraco 7.0.2. All seemed to go well and all my document types and templates etc are present. But when selecting a document type I get this error
I have not been using nuget that much myself (Frontend guy very keen on Sublime text) so I'm not sure if it can sometimes play tricks on you.
But in context of using nuget for upgrading Umbraco 7 I've seen that people have had some issues. But seems it all comes down to remembering to delete the Client Dependency cache afterwards. So I think it should be a workable approach.
Upgrading Umbraco 6.1.6 site with uBlogsy to Umbraco 7.0.2
I have just upgraded an Umbraco 6.1.6 site with uBlogsy to Umbraco 7.0.2. All seemed to go well and all my document types and templates etc are present. But when selecting a document type I get this error
[SqlException (0x80131904): Invalid column name 'propertyEditorAlias'.] System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +1789294 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5340642 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +244 System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +1691 System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +61 System.Data.SqlClient.SqlDataReader.get_MetaData() +90 System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +377 System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) +1421 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) +177 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +53 System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +137 System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +81 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +143 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +147 umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteReader(String commandText, SqlParameter[] parameters) +68 umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) +1
I was just wondering if anyone could point me in the right direction.
I tried to go directly to 7.1.4 but had a few more issues so decided to be a bit more gradual in my approach.
Hi Stephen
What steps have you taken to upgrade currently? Have you consulted the upgrade documentation etc. ?
Cheers, Jan
Hi Jan,
Thanks for the reply.
Yes I have done this a few times now.
I am going to attempt this again now from my current 6.2.1 site I now have and see how I get on.
I am using nuget btw. Would you advise to use this for the upgrade or do it manually?
Hi Stephen
I have not been using nuget that much myself (Frontend guy very keen on Sublime text) so I'm not sure if it can sometimes play tricks on you.
But in context of using nuget for upgrading Umbraco 7 I've seen that people have had some issues. But seems it all comes down to remembering to delete the Client Dependency cache afterwards. So I think it should be a workable approach.
/Jan
is working on a reply...