Page 1 of 1

Need to upgrade site from 7.0.0 to GOLD

Posted: Wed Jul 20, 2016 6:55 am
by crizilla
looks like i need to upgrade 7.0.0 to 7.0.1 then 7.0.2 then 7.0.3 before I can then upgrade to GOLD. I've tried but no luck. Can someone help me? Desperate to get this done message me and we can work something out

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Wed Jul 20, 2016 7:31 am
by Katie
Hi there,

You can upgrade directly from 7.0.0 to 7.0.3, skipping the ones in-between. Make sure that you clean up the database as this can cause problems during the upgrade. We had a patch for version 7 that will take care of this. Here are those instructions.

http://help.ablecommerce.com/index.htm# ... enance.htm

I would focus on the upgrade from 7.0.0 to 7.0.3 first. Let me know if you are getting any errors.

Thanks
Katie

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Wed Jul 20, 2016 7:48 am
by crizilla
are you sure thats the right link? it says anonymous user maintenance?

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Wed Jul 20, 2016 7:54 am
by Katie
Yes, that is the page you need to review so that you can make sure your database is cleaned up before upgrading to Gold. There was an issue with maintenance and this patch will take care of it. Be sure to read the whole thing carefully though.

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Thu Jul 21, 2016 5:42 am
by crizilla
i upgraded to 70.03 then tried upgrading to Gold but im getting "The specified database is not a valid version. The upgrade only works on databases from AC7.0.3 or higher" error. How can I check the version of the database? I have no idea why its not 7.0.3

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Thu Jul 21, 2016 5:59 am
by Katie
When you upgrade version 7, you have to manually access the database upgrade scripts. Was this step completed without error?

1) Browse to the <installpath>/install/upgrade.aspx page to run the database script.

e.g. http://localhost/ac7/install/upgrade.aspx

2) Follow the on-screen instructions to complete the upgrade:

Type BACKUP in the space provided to confirm you understand.

Initiate the upgrade. When finished, you should receive confirmation.
You may also receive some information on changes made during the upgrade.

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Thu Jul 21, 2016 6:05 am
by crizilla
Yeah I went through that and got to the confirmation page. There were some SQL errors, though.

Errors occurred during database upgrade.

SQL: IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS WHERE TABLE_NAME = 'ac_TaxRuleGroups' AND CONSTRAINT_NAME = 'ac_TaxRuleGroups_PK') BEGIN alter table "ac_TaxRuleGroups" add constraint "ac_TaxRuleGroups_PK" primary key ("GroupId", "TaxRuleId") END

Error: Table 'ac_TaxRuleGroups' already has a primary key defined on it. Could not create constraint. See previous errors.

SQL: DROP TABLE ac_Orders

Error: Could not drop object 'ac_Orders' because it is referenced by a FOREIGN KEY constraint.

SQL: EXECUTE sp_rename N'Tmp_ac_Orders', N'ac_Orders', 'OBJECT'

Error: Error: The new name 'ac_Orders' is already in use as a OBJECT name and would cause a duplicate that is not permitted.

SQL: ALTER TABLE ac_Orders ADD CONSTRAINT ac_Orders_PK PRIMARY KEY CLUSTERED ( OrderId ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

Error: Table 'ac_Orders' already has a primary key defined on it. Could not create constraint. See previous errors.

SQL: IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS WHERE TABLE_NAME = 'ac_Kits' AND CONSTRAINT_NAME = 'ac_Kits_PK') BEGIN ALTER TABLE ac_Kits ADD CONSTRAINT ac_Kits_PK PRIMARY KEY (ProductId) END

Error: Table 'ac_Kits' already has a primary key defined on it. Could not create constraint. See previous errors.

Upgrade complete.

Re: Need to upgrade site from 7.0.0 to GOLD

Posted: Thu Jul 21, 2016 6:48 am
by Shopping Cart Admin
Hello,

This may be a result of some triggers in the old 7.0.0 database. Run the first query to see if there are any offending triggers, it there are results then run the second query to remove them. This needs to be done on a fresh restore of the 7.0.0 database.

----------------- show TRIGGERS query------------------------

SELECT
[so].[name] AS [trigger_name],
USER_NAME([so].[uid]) AS [trigger_owner],
USER_NAME([so2].[uid]) AS [table_schema],
OBJECT_NAME([so].[parent_obj]) AS [table_name],
OBJECTPROPERTY( [so].[id], 'ExecIsUpdateTrigger') AS [isupdate],
OBJECTPROPERTY( [so].[id], 'ExecIsDeleteTrigger') AS [isdelete],
OBJECTPROPERTY( [so].[id], 'ExecIsInsertTrigger') AS [isinsert],
OBJECTPROPERTY( [so].[id], 'ExecIsAfterTrigger') AS [isafter],
OBJECTPROPERTY( [so].[id], 'ExecIsInsteadOfTrigger') AS [isinsteadof],
OBJECTPROPERTY([so].[id], 'ExecIsTriggerDisabled') AS [disabled] FROM sysobjects AS [so] INNER JOIN sysobjects AS so2 ON so.parent_obj = so2.Id WHERE [so].[type] = 'TR'

----------------- REMOVE TRIGGERS query------------------------

DECLARE @SQLCmd nvarchar(1000)
DECLARE @Trig varchar(500)
DECLARE @sch varchar(500)

DECLARE TGCursor CURSOR FOR

SELECT ISNULL(tbl.name, vue.name) AS [schemaName]
, trg.name AS triggerName
FROM sys.triggers trg
LEFT OUTER JOIN (SELECT tparent.object_id, ts.name
FROM sys.tables tparent
INNER JOIN sys.schemas ts ON TS.schema_id = tparent.SCHEMA_ID)
AS tbl ON tbl.OBJECT_ID = trg.parent_id LEFT OUTER JOIN (SELECT vparent.object_id, vs.name
FROM sys.views vparent
INNER JOIN sys.schemas vs ON vs.schema_id = vparent.SCHEMA_ID)
AS vue ON vue.OBJECT_ID = trg.parent_id

OPEN TGCursor
FETCH NEXT FROM TGCursor INTO @sch,@Trig WHILE @@FETCH_STATUS = 0 BEGIN

SET @SQLCmd = N'DROP TRIGGER [' + @sch + '].[' + @Trig + ']'
EXEC sp_executesql @SQLCmd
PRINT @SQLCmd

FETCH next FROM TGCursor INTO @sch,@Trig END

CLOSE TGCursor
DEALLOCATE TGCursor