Community
Showing results for 
Search instead for 
Do you mean 
Reply

Database (update) conversion error

New Member
Posts: 2
Country: USA

Database (update) conversion error

Going from 2010 product to 2012 iteration, and recieve the following error, and output log;

(I have skipped the middle of the log, and abbreviated somewhat).

My question is what should be my next course of action? {poop or go blind?}

 

Error Message: TBL_LOGONHISTORY_SYNC_TRI: Processing error occured in Sync Trigger TBL_LOGONHISTORY_SYNC_TRI, Table TBL_LOGON HISTORY - No LUDID value in CTL_SYNCTABLE. The transaction ended in the trigger. The batch has been aborted.

 

Log entry stream flowwos:

 

Changed database context to 'All5old1'.Setting Database Compatibility Level...  Local Datetime: 2013-01-16 15:23:33 Servername: GHSALES\ACT7 Engine Edition: 4  Express Edition (64-bit) Product Version: 10.50.2500.0 (SP1) Server Collation: Latin1_General_CI_AS ------------------------------------------------------------------------------ Sync Enabled: False Sync Role: ------------------------------------------------------------------------------ Database: All5old1 Status: ONLINE Create Version: 661  Configuration option 'user instances enabled' changed from 0 to 0. Run the RECONFIGURE statement to install.-------------------------------------------------------------  Current Build: 12.10.0165.0002  Update Build: 14.1.97.0 ------------------------------------------------------------- Setting Database Auto_Shrink To OFF...---------------------------------------------------------------- Setting Previous Schema Values: 12.10.0165.0002 TO 14.1.97.0DBCC execution completed. If DBCC printed error messages, contact your system administrator. DBCC execution completed. If DBCC printed error messages, contact your system administrator. Dropping indexes and constraints starting... 2013-01-16 15:23:33 Dropping triggers, starting ... 2013-01-16 15:23:39 Dropping Tables, starting... 2013-01-16 15:23:41 Creating Tables, starting... 2013-01-16 15:23:41Creating Table CTL_BI_CALENDARDATE_DIMCreating Table CTL_BI_COMPANY_DIMCreating Table CTL_BI_CONTACT_DIMCreating Table CTL_BI_GEOGRAPHY_DIMCreating Table CTL_BI_GROUP_DIMCreating Table CTL_BI_HISTORY_FACTCreating Table CTL_BI_HISTORYTYPE_DIMCreating Table CTL_BI_INDUSTRY_DIMCreating Table CTL_BI_OPPORTUNITY_DIMCreating Table CTL_BI_OPPORTUNITY_FACTCreating Table CTL_BI_OPPORTUNITYSTATUS_DIMCreating Table CTL_BI_USER_DIMCreating Table CTL_WF_COMPLETEDSCOPECreating Table CTL_WF_INSTANCESTATECreating Table TBL_CONTACT_SOURCECreating Table TBL_HISTORYTYPE_GROUPCreating Table TBL_HISTORYTYPE_SUPERGROUPCreating Table TBL_SYSATTACHMENTCreating Table TBL_WORKFLOW_ARCHIVECreating Table TBL_WORKFLOW_QUEUECreating Table TBL_WORKFLOW_SUBSCRIPTIONCreating Table TBL_WORKFLOWDEFCreating Table TBL_WORKFLOWDEF_ACL Adding calculated fields, starting... 2013-01-16 15:23:42 Altering table TBL_OPPORTUNITY (DAYSOPEN)Altering table TBL_PRODUCTSERVICE (DISCOUNTTYPE) Table modifications - Adds, Deletes, etc. 2013-01-16 15:23:42 Altering DESCRIPTION on table CTL_DBCONFIG   Adding column on CTL_SYNCDBMAP_SESSION ...   Adding column on CTL_SYNCDBMAP_SESSION ...Altering table CTL_PROVIDERVIEW Altering table CTL_SYNCSETTYPE Altering table CTL_SYSTABLEORDER Altering table TBL_ACCESSOR_ACTIVITYAltering table TBL_ACTIVITY Altering table TBL_ACTIVITYTYPE Altering table TBL_ATTACHMENT Altering table TBL_COMPANYAltering table TBL_CONTACT_CONTACTAltering table TBL_GROUPAltering table TBL_HISTORYTYPEAltering table TBL_PREFERENCE Altering table TBL_PRODUCTAltering table TBL_SYSDATATYPEAltering table TBL_SYSTABLE Modifying obsolete datatypes Object removals - procedures, views, etc. Setting Ctl_Abl_Connectortype Data...2013-01-16 15:23:45 Setting Ctl_Localstring Data...2013-01-16 15:23:45 Setting Syncsettype Data...2013-01-16 15:23:45 Setting Activity Priority Data...2013-01-16 15:23:45 Setting Eventlog Type Data...2013-01-16 15:23:45 Setting Folder Data...2013-01-16 15:23:45 Setting Preference Data...2013-01-16 15:23:45 Setting Role Data...2013-01-16 15:23:45 Setting SyncDbtype Data...2013-01-16 15:23:45 Setting Sysconstant Data...2013-01-16 15:23:46 Setting Sysdomain Data...2013-01-16 15:23:46 Setting Sysdatatypes...2013-01-16 15:23:46 Setting Featureset Data...2013-01-16 15:23:46 Setting Sysentity Data...2013-01-16 15:23:46 Setting Tbl_Syslocalcolumn Data...2013-01-16 15:23:46 Setting Sysoperator Data...2013-01-16 15:23:46 Setting Sysdomain Sysoperator Data...2013-01-16 15:23:46 Setting SystableDomain Data at 2013-01-16 15:23:46.120 Setting Sysvalue Data...2013-01-16 15:23:46 Setting Sysvalue Usage Data...2013-01-16 15:23:46 Setting Permission data at 2013-01-16 15:23:46 Setting Permission Depend Data...2013-01-16 15:23:46 Setting Historytype_Supergroup Data...2013-01-16 15:23:46 Setting Historytype_group Data...2013-01-16 15:23:46 Setting Historytype data...2013-01-16 15:23:46Creating views Creating functions and viewsCreating View VWX_USERCreating View VWX_TEAMCreating View VWX_RESOURCECreating View VWX_ACCESSORCreating View VWX_CONTACT_USER_ENUMCreating View VWX_GROUP_USER_ENUMCreating View VWX_COMPANY_USER_ENUMCreating View VWX_OPPORTUNITY_USER_ENUMCreating View VWX_WORKFLOWDEF_USER_ENUMCreating View VWX_PERMISSIONINFOCreating View VWX_ROLEINFOCreating View VWX_ROLE_PERMISSION_MATRIXCreating View VWX_USERPERMISSIONCreating view VWT_OPPORTUNITY_STAGE_PROCESSCreating view VWT_WORKFLOW_ARCHIVECreating view VWT_WORKFLOWDEF_ACCESSCreating view VWT_OPPORTUNITY_ACCESSCreating view VWT_COMPANY_ACCESSCreating view VWT_GROUP_ACCESSCreating View VWT_CONTACT_ACCESSCreating view VWT_SECONDARY_CONTACTCreating view VWT_COMPANY_BUSINESSLINKCreating view VWT_CONTACT_BUSINESSLINK Running DBRights... The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. *** Setting rights on procedures...  ...................

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

skip

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Executing stored procedures, round two...2013-01-16 15:24:42.660 Rebuild sync table order 2013-01-16 15:24:42.660Rebuild table relation 2013-01-16 15:24:44.257Rebuild table keys for foreign keys2013-01-16 15:24:45.237PRC_UPD_OLEDBFIELDS Starttime: 2013-01-16 15:24:49.250Rebuild v1 table functions 2013-01-16 15:24:50.127 The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. The number of orphaned users fixed by updating users was 0. The number of orphaned users fixed by adding new logins and then updating users was 0. *** Setting rights on procedures...Rebuild v1 table views 2013-01-16 15:24:54.543User Column Access 2013-01-16 15:24:54.783 *********** Schema Update failed ************** *********** Exception message follows ********* System.Data.SqlClient.SqlException: PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO CREATE/ALTER BASE FUNCTION FNR_CONTACT PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE FUNCTION METADATA FOR FNR_CONTACT PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED EXECUTING STATEMENT IF (SELECT OBJECT_ID('dbo.FNR_GROUPQUERY')) IS NOT NULL INSERT INTO #CREATETYPE VALUES ('dbo.FNR_GROUPQUERY','ALTER') ELSE INSERT INTO #CREATETYPE VALUES ('dbo.FNR_GROUPQUERY','CREATE'); The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO CREATE/ALTER BASE FUNCTION FNR_GROUPQUERY PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE FUNCTION METADATA FOR FNR_GROUPQUERY PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED EXECUTING STATEMENT IF (SELECT OBJECT_ID('dbo.FNR_HISTORYTYPE')) IS NOT NULL INSERT INTO #CREATETYPE VALUES ('dbo.FNR_HISTORYTYPE','ALTER') ELSE INSERT INTO #CREATETYPE VALUES ('dbo.FNR_HISTORYTYPE','CREATE'); The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO CREATE/ALTER BASE FUNCTION FNR_HISTORYTYPE PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE FUNCTION METADATA FOR FNR_HISTORYTYPE PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED EXECUTING STATEMENT IF (SELECT OBJECT_ID('dbo.FNR_ACCESSOR_ACTIVITY')) IS NOT NULL INSERT INTO #CREATETYPE VALUES ('dbo.FNR_ACCESSOR_ACTIVITY','ALTER') ELSE INSERT INTO #CREATETYPE VALUES ('dbo.FNR_ACCESSOR_ACTIVITY','CREATE'); The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN  ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO CREATE/ALTER BASE FUNCTION FNR_ACCESSOR_ACTIVITY PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE FUNCTION METADATA FOR FNR_ACCESSOR_ACTIVITY PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED EXECUTING STATEMENT IF (SELECT OBJECT_ID('dbo.FNR_ADDRESS')) IS NOT NULL INSERT INTO #CREATETYPE VALUES ('dbo.FNR_ADDRESS','ALTER') ELSE INSERT INTO #CREATETYPE VALUES ('dbo.FNR_ADDRESS','CREATE'); The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED WHEN INSERTING FUNCTION COLUMN METADATA. PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO CREATE/ALTER BASE FUNCTION FNR_ACCESSOR_DELEGATE PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE FUNCTION METADATA FOR FNR_ACCESSOR_DELEGATE PRC_REPORT_MAKE_OLEDBFUNCTIONS: ERROR OCCURRED TRYING TO REMOVE NON-EXISTENT OLEDB FUNCTIONS. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. OleDB Functions 2013-01-16 15:24:55.050    at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)    at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)

Schema Update failed.

 

 

 

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Database (update) conversion error

Hello Gkhobbs3,

Welcome to the Sage ACT! Online Community!

 

First you will want to attempt to update the 2010 Demo database, if it updates successfully it is an indication of a database specific issue.  If it also fails, the installation of Microsoft SQL may be damaged (need to be reinstalled).

 

Expecting the 2010 demo conversion to be successful, use the steps in the article to perform maintenance on your main database: KB Article 13790

Greg Martin
Sage
New Member
Posts: 2
Country: USA

Re: Database (update) conversion error

Thank you Sir! Will advise how it goes.