Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

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


  • Keith Donnell 82 posts 187 karma points
    Oct 10, 2016 @ 15:34
    Keith Donnell
    0

    Issue updating from v1.14.1 to v2.1

    I am having the same issue described here: https://our.umbraco.org/projects/collaboration/merchello/merchello/77468-unable-to-upgrade-to-200201

    The only thing I have to add is that I got this error immediately when attempting to install the 2.1 package (https://our.umbraco.org/FileDownload?id=16322) through the umbraco dashboard. After cleaning/rebuilding the solution, I get this error on any page I visit.

    The only help I saw in the above forum post was to set the merchelloConfigurationStatus setting to "1.14.1" so as to retrigger the upgrade, however my merchelloConfigurationStatus was already (unchanged) set to 1.14.1.

    Any ideas?

    Exception is: Invalid column name 'author'. Invalid column name 'internalOnly'.

    enter image description here

    Copy Link
  • Rusty Swayne 1655 posts 4993 karma points c-trib
    Oct 10, 2016 @ 16:31
    Rusty Swayne
    0

    That would indicate that the 2.0.0 migration is not triggering for some reason.

    Can you confirm that you database has a merchNote table?

    Copy Link
  • Keith Donnell 82 posts 187 karma points
    Oct 10, 2016 @ 17:57
    Keith Donnell
    0

    Hello Rusty and thanks for your prompt reply.

    The merchNote table exists in our DB. The schema is as follows:

    CREATE TABLE [dbo].[merchNote](
    [pk] [uniqueidentifier] NOT NULL,
    [entityKey] [uniqueidentifier] NOT NULL,
    [entityTfKey] [uniqueidentifier] NOT NULL,
    [message] [ntext] NULL,
    [updateDate] [datetime] NOT NULL,
    [createDate] [datetime] NOT NULL,
 CONSTRAINT [PK_merchNote] PRIMARY KEY CLUSTERED 
(
    [pk] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO
    Copy Link
  • Rusty Swayne 1655 posts 4993 karma points c-trib
    Oct 10, 2016 @ 21:06
    Rusty Swayne
    100

    It looks like it's failing on the 2.0.0 update - try adding the two fields manually after which the table should look like

    CREATE TABLE [dbo].[merchNote](
    [pk] [uniqueidentifier] NOT NULL,
    [entityKey] [uniqueidentifier] NOT NULL,
    [entityTfKey] [uniqueidentifier] NOT NULL,
    [author] [nvarchar](255) NULL,
    [message] [ntext] NULL,
    [internalOnly] [bit] NOT NULL,
    [updateDate] [datetime] NOT NULL,
    [createDate] [datetime] NOT NULL,
 CONSTRAINT [PK_merchNote] PRIMARY KEY CLUSTERED 
(
    [pk] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

    Once the two fields have been added try running the Migration again (refresh).

    Copy Link
  • Keith Donnell 82 posts 187 karma points
    Oct 11, 2016 @ 15:58
    Keith Donnell
    0

    I reverted the source updates, added the two columns to the merchNote table, and then re-applied the package in the Umbraco dashboard, and everything appears to have worked (no more errors at least). I will let you know in a new thread if we have any more issues with the upgrade.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft