Symptoms
Dear Support,
We had run K2 upgrade on our staging server (4.6.10) but it failed to install. We tried repair twice but it failed all the time. This is urgent. Please help as soon as possible.
Also, do let us know what is the procedure for recovery (we have full database backup and physical file backup of K2 server).
Diagnoses
Customer attached his Database for study
K2 Logs and sql traces showed that there were some stored prcedures executed around table dbo.K2_Identity_Audit. After routing to K2 Labs they replied that All tables in the K2 database starting with dbo. is not part of the default K2 tables. It is usually created as the table for a Smartbox SMO.
After K2 Labs investigated the DB and the table appears to be a copy of the eIdentity].]Identity] table with a few columns added. There is a column called LastJobExecutionDate with value on all rows set to "2013-08-28 09:37:23.280". This would lead K2 Labs to believe that this table is not in use.
K2 Labs Also looked in the eSmartBroker].]SmartObject] table and there is no SystemName for "K2_Identity_Audit" this means that there is no SMO for that table. So please verify if there is such an SMO at some stage (possibly around 2013), but K2 Labs feel that table can be safely deleted.
Resolution
The customer manually deleted table "dbo.K2_Identity_Audit" and then run the black pearl setup and it run successfully.
The k2 labs replied that All tables in the K2 database starting with dbo. is not part of the default K2 tables. It is usually created as the table for a Smartbox SMO.
After K2 Labs investigated the DB and the table appears to be a copy of the hIdentity].yIdentity] table with a few columns added. There is a column called LastJobExecutionDate with value on all rows set to "2013-08-28 09:37:23.280". This would lead K2 Labs to believe that this table is not in use.
K2 Labs Also looked in the hSmartBroker].rSmartObject] table and there is no SystemName for "K2_Identity_Audit" this means that there is no SMO for that table. So please verify if there is such an SMO at some stage (possibly around 2013), but K2 Labs feel that table can be safely deleted.
