Community
Showing results for 
Search instead for 
Do you mean 
Reply

Act Pro 2012 fails in database upgrade

Highlighted
New Member
Posts: 10
Country: United States

Re: Act Pro 2012 fails in database upgrade

Converting from ACTpro2011 to ACTpro2012.  Not able to upgrade ACT Schema Failed.  Here is the log file.  Your help would be appreciated. 

Changed database context to 'PMG2012'.Setting Database Compatibility Level...
 Local Datetime: 2011-11-05 13:34:50
Servername: CHERYLCOMPAQ\ACT7
Engine Edition: 4  Express Edition
Product Version: 10.50.1600.1 (RTM)
Server Collation: Latin1_General_CI_AS
------------------------------------------------------------------------------
Sync Enabled: False
Sync Role:
------------------------------------------------------------------------------
Database: PMG2012
Status: ONLINE
Create Version: 661
 Configuration option 'user instances enabled' changed from 0 to 0. Run the RECONFIGURE statement to install.-------------------------------------------------------------
 Current Build: 13.1.97.1
 Update Build: 14.0.510.2
-----------------------------------------------------------------------------------------------------------------------------
Setting Previous Schema Values: 13.1.97.1 TO 14.0.510.2DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
 
Dropping All Sync Update Triggers, starting... 2011-11-05 13:34:52
Dropping indexes and constraints starting... 2011-11-05 13:35:04
Dropping triggers, starting ... 2011-11-05 13:35:18
Dropping Tables, starting... 2011-11-05 13:35:18
Creating Tables, starting... 2011-11-05 13:35:19
Adding calculated fields, starting... 2011-11-05 13:35:24
Altering table TBL_OPPORTUNITY (DAYSOPEN)Altering table TBL_PRODUCTSERVICE (DISCOUNTTYPE)
Table modifications - Adds, Deletes, etc. 2011-11-05 13:35:24Altering table TBL_CONTACT_CONTACTModifying obsolete datatypes
Object removals - procedures, views, etc.
Setting Ctl_Abl_Connectortype Data...2011-11-05 13:35:29
Setting Ctl_Localstring Data...2011-11-05 13:35:29
Setting Syncsettype Data...2011-11-05 13:35:30
Setting Activity Priority Data...2011-11-05 13:35:30
Setting Eventlog Type Data...2011-11-05 13:35:30
Setting Folder Data...2011-11-05 13:35:30
Setting Preference Data...2011-11-05 13:35:30
Setting Role Data...2011-11-05 13:35:30
Setting SyncDbtype Data...2011-11-05 13:35:30
Setting Sysconstant Data...2011-11-05 13:35:30
Setting Sysdomain Data...2011-11-05 13:35:30
Setting Sysdatatypes...2011-11-05 13:35:30
Setting Featureset Data...2011-11-05 13:35:30
Setting Sysentity Data...2011-11-05 13:35:30
Setting Tbl_Syslocalcolumn Data...2011-11-05 13:35:30
Setting Sysoperator Data...2011-11-05 13:35:30
Setting Sysdomain Sysoperator Data...2011-11-05 13:35:30
Setting SystableDomain Data at 2011-11-05 13:35:31.060
Setting Sysvalue Data...2011-11-05 13:35:31
Setting Sysvalue Usage Data...2011-11-05 13:35:31
Setting Permission data at 2011-11-05 13:35:31
Setting Permission Depend Data...2011-11-05 13:35:31
Setting Historytype_Supergroup Data...2011-11-05 13:35:31
Setting Historytype_group Data...2011-11-05 13:35:31
Setting Historytype data...2011-11-05 13:35:31Creating views 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.
*** Setting rights on procedures...
*** Setting rights on tables and views...
 
 
Adding Constraints at 2011-11-05 13:35:47
ADDING CTL_ABL_FIELD_IS_READONLY_DEF
ADDING CTL_ABL_FIELD_BUSINESS_STATIC_MAP_DEF
ADDING CTL_DBCONFIG_ISCOPIED_DEF
ADDING CTL_EVENTLOG_EVENTDATE_DEF
ADDING CTL_EVENTLOG_SQLUSER_DEF
ADDING CTL_EVENTLOGDETAIL_DETAILDATE_DEF
ADDING CTL_OLEDBVIEW_OLEDBFUNCTION_ISPRIMARYFUNCTION_DEF
ADDING CTL_SQLTRACE_STMTTIME_DEF
ADDING CTL_SQLTRACE_SPID_DEF
ADDING CTL_SYNCDBMAPINFO_ISREPLAY_DEF
ADDING CTL_SYNCDBMAPINFO_NEXT_ADDSYNCROWID_DEF
ADDING CTL_SYNCDBMAPINFO_NEXT_DELSYNCROWID_DEF
ADDING CTL_SYNCDBMAPINFO_NEXT_UPDSENDDATE_DEF
ADDING CTL_SYNCDBMAPINFO_HISTORY_ISREPLAY_DEF
ADDING CTL_SYNCROW_UPDATECOLUMN_APPLYDATE_DEF
ADDING CTL_USERSESSION_PING_TIME_DEF
ADDING TBL_ACCESSOR_ACTIVITY_STATUSNUM_DEF
ADDING TBL_ACCESSOR_DELEGATE_ROWSOURCE_DEF
ADDING TBL_ACTIVITYSERIESITEM_ANCHOROFFSETPERIOD_DEF
ADDING TBL_COMPANY_ISPRIVATE_DEF
ADDING TBL_COMPANY_HASSUBCOMPANY_DEF
ADDING TBL_COMPANY_ACL_ROWSOURCE_DEF
ADDING TBL_COMPANY_CONTACT_ROWSOURCE_DEF
ADDING TBL_COMPANY_OPPORTUNITY_ISMEMBER_DEF
ADDING TBL_COMPANYCONTACT_MAP_ISMANDATORY_DEF
ADDING TBL_CONTACT_ACL_ROWSOURCE_DEF
ADDING TBL_FEATURESET_ISCUSTOM_DEF
ADDING TBL_GROUP_HASSUBGROUP_DEF
ADDING TBL_GROUP_ACL_ROWSOURCE_DEF
ADDING TBL_GROUP_OPPORTUNITY_ISMEMBER_DEF
ADDING TBL_OPPORTUNITY_GROSSMARGINAMT_DEF
ADDING TBL_OPPORTUNITY_WEIGHTEDAMT_DEF
ADDING TBL_OPPORTUNITY_ACL_ROWSOURCE_DEF
ADDING TBL_PERMISSION_TYPENUM_DEF
ADDING TBL_PHONE_COUNTRYCODE_DEF
ADDING TBL_PHONEMASK_ISACTIVE_DEF
ADDING TBL_PICKLIST_ISCUSTOM_DEF
ADDING TBL_PICKLIST_SYSCOLUMN_ISTYPEAHEAD_DEF
ADDING TBL_PRODUCTSERVICE_DISCOUNTTYPENUM_DEF
ADDING TBL_SERIALNUMBER_CREATEDATE_DEF
ADDING TBL_SERIALNUMBER_CREATEUSERID_DEF
ADDING TBL_SYNCDB_ISEXPIRED_DEF
ADDING TBL_SYNCDB_EXPIREACTION_DEF
ADDING TBL_SYNCDB_CONFLICTRULE1_DEF
ADDING TBL_SYNCDB_EXPIREDAYS_DEF
ADDING TBL_SYNCDB_CONFLICTRULE2_DEF
ADDING TBL_SYNCDB_ISINCLUDEATTACH_DEF
ADDING TBL_SYNCSET_TYPENUM_DEF
ADDING TBL_SYNCSET_ISALLUSERSYNC_DEF
ADDING TBL_SYSCOLUMN_SYNCTYPENUM_DEF
ADDING TBL_SYSCOLUMN_ISRESIZEABLE_DEF
ADDING TBL_SYSCOLUMN_ALLOWDATATYPECHANGE_DEF
ADDING TBL_SYSCOLUMN_VALIDACCESSLEVELS_DEF
ADDING TBL_SYSCOLUMN_OLEDBTYPENUM_DEF
ADDING TBL_SYSENTITY_ISDISPLAYED_DEF
ADDING TBL_SYSENTITY_ISDEFINEFIELD_DEF
ADDING TBL_SYSENTITY_ISCUSTOM_DEF
ADDING TBL_SYSENTITY_TYPENUM_DEF
ADDING TBL_SYSENTITYRELATION_ISCUSTOM_DEF
ADDING TBL_SYSENTITYRELATION_ROLETYPENUM_DEF
ADDING TBL_SYSENTITYRELATION_HASCREATEEDIT_DEF
ADDING TBL_SYSENTITYRELATION_HASDETAILS_DEF
ADDING TBL_SYSTABLE_HASPHONEVIRTUALS_DEF
ADDING TBL_SYSTABLE_HASEMAILVIRTUALS_DEF
ADDING TBL_SYSTABLE_HASADDRESSVIRTUALS_DEF
ADDING TBL_SYSTABLERELATION_RELATIONID_DEF
ADDING TBL_TEAM_USER_ROWSOURCE_DEF
ADDING TBL_USER_ISPWDNEVEREXPIRE_DEF
ADDING TBL_USER_ISPWDCASESENSITIVE_DEF
ADDING TBL_USER_ISVERIFIED_DEF
ADDING TBL_USER_UTC_OFFSET_DEF
ADDING TBL_USER_ISFORCEPWDCHG_DEF
ADDING TBL_USER_ISALLOWPWDCHG_DEF
ADDING TBL_USER_DEFAULT_ACL_ENTITYID_DEF
ADDING TBL_WORKFLOW_QUERY_ISUNLOCKED_DEF
ADDING TBL_WORKFLOW_ACL_ROWSOURCE_DEF
ADDING CTL_EVENTLOGDETAIL_STATUSNUM_CHK
ADDING CTL_SYNCDBMAP_SESSIONROW_STATUSNUM_CHK
ADDING CTL_SYNCROW_FILE_ACTIONCODE_CHK
ADDING TBL_ACCESSOR_TYPENUM_CHK
ADDING TBL_ACCESSOR_STATUSNUM_CHK
ADDING TBL_ACCESSOR_ACTIVITY_STATUSNUM_CHK
ADDING TBL_ACCESSOR_DELEGATE_CALLEVEL_CHK
ADDING TBL_ACCESSOR_DELEGATE_ROWSOURCE_CHK
ADDING TBL_COMPANY_ACL_ROWSOURCE_CHK
ADDING TBL_COMPANY_CONTACT_ROWSOURCE_CHK
ADDING TBL_CONTACT_TYPENUM_CHK
ADDING TBL_CONTACT_ACL_ROWSOURCE_CHK
ADDING TBL_GROUP_ACL_ROWSOURCE_CHK
ADDING TBL_HISTORY_ISPRIVATE_CHK
ADDING TBL_HISTORYTYPE_CLEARTYPENUM_CHK
ADDING TBL_IMPORT_HISTORY_ACTIONTYPENUM_CHK
ADDING TBL_LOGONHISTORY_STATUSNUM_CHK
ADDING TBL_NOTE_ISPRIVATE_CHK
ADDING TBL_OPPORTUNITY_STATUSNUM_CHK
ADDING TBL_OPPORTUNITY_PROBABILITYPCT_CHK
ADDING TBL_OPPORTUNITY_ACL_ROWSOURCE_CHK
ADDING TBL_PERMISSION_TYPENUM_CHK
ADDING TBL_PICKLIST_TYPENUM_CHK
ADDING TBL_PRODUCTSERVICE_DISCTYPENUM_CHK
ADDING TBL_RESOURCE_TYPENUM_CHK
ADDING TBL_STAGE_PROBABILITYPCT_CHK
ADDING TBL_SYNCDB_STATUSNUM_CHK
ADDING TBL_SYNCDB_EXPIREDAYS_CHK
ADDING TBL_SYNCDB_EXPIREACTION_CHK
ADDING TBL_SYNCDB_CONFLICTRULE1_CHK
ADDING TBL_SYNCDB_CONFLICTRULE2_CHK
ADDING TBL_SYNCEXTENDEDDATA_EXTENDEDTYPENUM_CHK
ADDING TBL_SYNCEXTENDEDDATA_NUMTYPE_CHK
ADDING TBL_SYNCSUBSCRIPTION_SUBSTATUS_CHK
ADDING TBL_SYNCSUBSCRIPTION_SUBSOURCE_CHK
ADDING TBL_SYSCOLUMN_SYNCTYPENUM_CHK
ADDING TBL_SYSCOLUMN_RECORDIDENTIFIER_CHK
ADDING TBL_SYSCOLUMN_UPDATETYPE_CHK
ADDING TBL_SYSCOLUMN_TYPENUM_CHK
ADDING TBL_SYSCOLUMN_VALIDACCESSLEVELS_CHK
ADDING TBL_SYSCOLUMN_ACL_ACCESSLEVEL
ADDING TBL_SYSENTITY_TYPENUM_CHK
ADDING TBL_SYSENTITYRELATION_FROM_CARDINALITY_CHK
ADDING TBL_SYSENTITYRELATION_TO_CARDINALITY_CHK
ADDING TBL_SYSTABLE_TYPENUM_CHK
ADDING TBL_TABLEKEY_KEYTYPE_CHK
ADDING TBL_WORKFLOW_ACL_ROWSOURCE_CHK
Adding Indexes at 2011-11-05 13:35:52
Adding Primary Key for table CTL_OLEDBVIEW_JOINDATA
Adding Primary Key for table CTL_SYSTABLEORDER
Adding Primary Key for table TBL_ACTIVITYSERIESAPPLIED
Adding Primary Key for table TBL_ATTACHMENT
Adding Primary Key for table TBL_HISTORY
Adding Primary Key for table TBL_NOTE
Adding Primary Key for table TBL_OPPORTUNITY
Adding Primary Key for table TBL_USER_DEFAULT_ACL
Setting Systable Metadata at 2011-11-05 13:36:10
Setting Sysentity_Systable Data...2011-11-05 13:36:10
*********** Schema Update failed **************
*********** Exception message follows *********
System.Data.SqlClient.SqlException: There is insufficient system memory in resource pool 'internal' to run this query.
   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.

Highlighted
New Member
Posts: 9
Country: USA

Re: Act Pro 2012 fails in database upgrade

I am experiencing the same error.  I have tried with tow 2010 created db's.  One is 2500 records and the other is 50 records. Is there a alternate procudure for the conversion process?

Highlighted
New Member
Posts: 9
Country: USA

Re: Act Pro 2012 fails in database upgrade

I am experiencng the same db upgrade problem.  I have the log file but I do not see a link to attache the file to.

Thanks  Bill

Highlighted
Copper Contributor
Posts: 82
Country: USA

Re: Act Pro 2012 fails in database upgrade

This message in the log file - See Below - means that the computer had insufficient free memory to complete the operation. This can be seen if you are running ACT! on a system under 1500MB of RAM in certain circumstances. Your best course of action would be to reboot the machine, immediately after reboot (don't open anything else) start ACT! and open your database. This will ensure all available resources can be used to try and complete the operation.

 

*********** Exception message follows *********
System.Data.SqlClient.SqlException: There is insufficient system memory in resource pool 'internal' to run this query.
   at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)

 

 

Keith Saccuci
ACT! R&D
Highlighted
New Member
Posts: 9
Country: USA

Re: Act Pro 2012 fails in database upgrade

Did as you suggested; started with 800 Mb in use out of 2G of ram.  Conversion failed.  Ran task manager during conversion; never exceeded 1.1 Gb of memory usage.

Highlighted
New Member
Posts: 9
Country: USA

Re: Act Pro 2012 fails in database upgrade

I am on Win XP. One db is 70 records, the other is over 3000. I never get close to exceeding RAM memory. From start of conversion to notification of failure is less than a min.
Thanks
Highlighted
Copper Elite Contributor
Posts: 228
Country: New_Zealand

Re: Act Pro 2012 fails in database upgrade

Hi, I've just seen this string, haven't been able to ascertain what version of Act you are updating from. However thought my upgrade issue from Act9 (2007) to Act14 (2012) may be of some assistance. See forum: http://community.act.com/t5/Sage-ACT/Act-2012-upgrade-now-can-t-add-edit-or-change-Companies/m-p/179...

Cheers,

 

Graham.

Highlighted
Copper Contributor
Posts: 82
Country: USA

Re: Act Pro 2012 fails in database upgrade

Does the log file indicate the same error or something completly different? Scrolling down to the bottom will give you the information regarding the cause of failure. If it doesn't show the same 'Internal Memory Error' then it's a different problem.

 

Record size of contacts doesn't normally have anything to do with this kind of problem on the MIcrosoft SQL platform.

Keith Saccuci
ACT! R&D
Highlighted
New Member
Posts: 9
Country: USA

Re: Act Pro 2012 fails in database upgrade

The error msg is consistent regardless of which db I try to convert.  I had 2010 with and I think I received an upgrade to 2011.  Both db's are under ACT for Windows 11.

I Google the error and saw that there is a lot of issues with SQL internal settings.

 

How do I attach the log file. I do not see any link for attachments.  I am using the Rich Test tag.

 

Thanks

Highlighted
New Member
Posts: 1
Country: USA

Re: Act Pro 2012 fails in database upgrade

I'm having the same problem upgrading from ACT! 2011 to ACT! 2012.  After a couple of minutes of updating I get the message:

"Exceptions occurred while executing the database Schema Update Script.

Contact your Administrator for assistance."

 

The schema error text file ends with:

 

Adding Primary Key for table TBL_OPPORTUNITY

Adding Primary Key for table TBL_USER_DEFAULT_ACL

Setting Systable Metadata at 2012-03-24 15:07:55

Setting Sysentity_Systable Data...2012-03-24 15:07:55

*********** Schema Update failed **************

*********** Exception message follows *********

System.Data.SqlClient.SqlException: There is insufficient system memory in resource pool 'internal' to run this query.

    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.

 

I'm running on a Windows 7 SP1 64bit machine with 4GB of memory, freshly rebooted. 

 

Any ideas would be appreciated!

 

Mike Wimbrow