Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Tom 713 posts 951 karma points
    Mar 03, 2016 @ 06:13
    Tom
    0

    7.0.1 -> 7.4.1 Upgrade Sadness - CAN'T UPGRADE

    Hi on the back of Sebastiaan's recent upgrade email we're having no end of pain trying to upgrade 7.0.1 -> 7.4.1

    While upgrading (we have made numerous attempts) we consistently get the error:

    ContentType with alias 'ContentPage' was added as a Composition to ContentType with alias 'Product', but there was a conflict on the following PropertyTypes: 'headerImageBackgroundClass'. PropertyTypes must have a unique alias across all Compositions in order to compose a valid ContentType Composition.

    I'm of the understanding that compositions came in after 7.0.1 so in trying to run migrations initially in the upgrade screens it is blowing up..

    Are we supposed to de-couple some doc type relationships before upgrading so that compositions can be created during the upgrade process and then recompose them removing conflicts after??

    Sorry it's driving us a bit nuts

  • Susanne 7 posts 29 karma points
    Mar 03, 2016 @ 07:04
    Susanne
    0

    Also trying to upgrade from 7.0.1 to 7.4.1 via NuGet.

    We cannot get past the first part of the installation screen, in the umbraco logs we see this error:

    2016-03-03 17:55:44,900 [P11712/D5/T14] ERROR     Umbraco.Core.Persistence.UmbracoDatabase - Database exception occurred
    System.Data.SqlClient.SqlException (0x80131904): Cannot find the object "umbracoUserLogins" because it does not exist or you do not have permissions.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at StackExchange.Profiling.Data.ProfiledDbCommand.ExecuteNonQuery() in c:\Code\github\SamSaffron\MiniProfiler\StackExchange.Profiling\Data\ProfiledDbCommand.cs:line 279
       at Umbraco.Core.Persistence.PetaPocoCommandExtensions.<>c__DisplayClass1.<ExecuteNonQueryWithRetry>b__0()
       at Umbraco.Core.Persistence.FaultHandling.RetryPolicy.ExecuteAction[TResult](Func`1 func)
       at Umbraco.Core.Persistence.Database.Execute(String sql, Object[] args)
    

    It looks like it is looking for a table that does not exist yet in the database? We have allowed permissions on the database.

    How can we get around this?

  • M T 35 posts 212 karma points
    Mar 03, 2016 @ 09:26
    M T
    0

    Looks like "umbracoUserLogins" is named wrong here's mine :-

     SELECT TOP 1000 [id]
          ,[userDisabled]
          ,[userNoConsole]
          ,[userType]
          ,[startStructureID]
          ,[startMediaID]
          ,[userName]
          ,[userLogin]
          ,[userPassword]
          ,[userEmail]
          ,[userLanguage]
          ,[securityStampToken]
          ,[failedLoginAttempts]
          ,[lastLockoutDate]
          ,[lastPasswordChangeDate]
          ,[lastLoginDate]
      FROM [....].[dbo].[umbracoUser]
    

    You could try renaming but the data could be out of sync elsewhere, 7.0 to 7.4 is a big jump. If you took backups i'd recommend rolling back to 7.0 and upgrading incrementally. 7.0 > 7.1 7.1 > 7.2, 7.2 -> 7.3, 7.3 >7.4

    regards m

  • Susanne 7 posts 29 karma points
    Mar 03, 2016 @ 22:20
    Susanne
    0

    Hi M,

    The table in our database is called umbracoUser as well, the schema mirrors what you have exactly. Which Umbraco version are you running?

    What seems to be strange is that the migrations themselves are referencing a table named umbracoUserLogins when we try to run the installer.

    Susanne

  • Tom 713 posts 951 karma points
    Mar 03, 2016 @ 22:39
    Tom
    0

    Thanks for the reply! trying incrementally this morning :)

  • Liam 1 post 71 karma points
    Apr 26, 2016 @ 05:35
    Liam
    0

    I had this issue when upgrading. It was caused by me incorrectly merging the web.config file.

    I let it overwrite the umbracoConfigurationStatus value in AppSettings to:

    <add key="umbracoConfigurationStatus" value="" />
    

    But it needs to remain as your current Umbraco version (before the upgrade) e.g.:

    <add key="umbracoConfigurationStatus" value="7.4.0" />
    

    When there is no value the installer doesn't know what version to upgrade from, so it runs older upgrade scripts which attempt to modify/delete the umbracoUserLogins table (which no longer exists)

Please Sign in or register to post replies

Write your reply to:

Draft