Community
Showing results for 
Search instead for 
Do you mean 
Reply

Database conversion issue when converting from 2008 to 2011

New Member
Posts: 1
Country: Germany

Database conversion issue when converting from 2008 to 2011

I am attempting to upgrade my ACT from 2008 to 2011. Software installed fine and I can open demo database BUT it will not convert my 2008 database. It errors out and I get a "schema" error message. The ActSchemaUpdateResults.txt file shows that many files converted succesfully then I get this - 

 

Creating index TBL_ADDRESS_IF702..
Creating index TBL_EMAIL_IF700..
Creating index TBL_PHONE_IF702..
Altering table TBL_OPPORTUNITY (NAME)
Creating table TBL_PRODUCTSERVICE
Creating index TBL_PRODUCTSERVICE_IF7...
Creating index TBL_PRODUCTSERVICE_IE1...
Creating table TBL_OPPORTUNITY_PRODUCTSERVICE
  Alter the product_service table to implement calculated columns...
  Dropping Trigger TBL_OPPORTUNITY_PRODUCT_TRIU1
  Updating TBL_OPPORTUNITY_PRODUCT DiscountPrice...
  Updating TBL_OPPORTUNITY_PRODUCT ExtendedAmt...
  loading OPPORTUNITY_PRODUCT records into PRODUCTSERVICE...
  loading OPPORTUNITY_PRODUCTSERVICE association records...
PROCESSING ERROR OCCURRED IN BUILD 12.00.0148.0000.
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 486
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
Msg 207, Level 16, State 1, Server VS36873A\ACT7, Line 18
Invalid column name 'LOCALSTRINGID'.
***********************
SETTING TABLE METADATA at 2011-08-27 10:49:33.840
***********************
PROCESSING ERROR OCCURRED ADDING SYSTABLE INFO FOR CTL_ABL_ACTIVITY
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 31
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
***********************
SETTING COLUMN METADATA at 2011-08-27 10:49:35.900
***********************
PROCESSING ERROR OCCURRED ADDING SYSCOLUMN INFO FOR ABL_ACTIVITYID on CTL_ABL_ACTIVITY
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 62
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
PROCESSING ERROR OCCURRED ADDING SYSCOLUMN INFO FOR COMPANYID ON VWT_COMPANY_ACCESS
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 35
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
PROCESSING ERROR OCCURRED ADDING SYSCOLUMN INFO FOR OPPORTUNITYID ON VWT_OPPORTUNITY_STAGE_PROCESS
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 31
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
***********************
SETTING KEY METADATA at 2011-08-27 10:49:36.700
***********************
PROCESSING ERROR OCCURRED ADDING SYSTABLEKEY INFO FOR XPKABL_ACTIVITY on CTL_ABL_ACTIVITY
Msg 50000, Level 16, State 1, Server VS36873A\ACT7, Line 22
WORK WAS ROLLED BACK - EXITING FROM UPDATE!
***********************
DONE SETTING KEY METADATA at 2011-08-27 10:49:36.823
***********************
 
FOOTER ENTRY TRANCOUNT = 0
Msg 50000, Level 25, State 1, Server VS36873A\ACT7, Line 19
***** Update of database failed!  Exiting from update!
Msg 2745, Level 16, State 2, Server VS36873A\ACT7, Line 19
Process ID 52 has raised user error 50000, severity 25. SQL Server is terminating this process.

 

I have used ACTDiag to run all the database tools - check reindex, check schema etc and all are fine, but I still get the same errormsg.

I am updated from ACT! by Sage 2008 (10.0) Version 10.0.2.191 to Sage ACT! Pro 2011 Version 13.1.111.0, Hotfix 1

OS is WIN 2008 R2 SP1

 

I WOULD APPRECIATE ANY HELP

Copper Contributor
Posts: 48
Country: Canada

Re: Database conversion issue when converting from 2008 to 2011

I don't know if it's any help but I have run into issues with MS SQL when updating a user database. The system requirement says 1 gig of RAM but I found that although the demo database converted fine, an actual database would crash the updater every time. I found that I had to have over 2 gig of ram free before I could successfully do any updating through MS SQL.

Sorry, I don't have the error logs handy but I can remember that the errors were seldom the same even if I just re-ran the update process with no changes. (I ended up installing ACT on a clean system with 8 gigs of RAM, updating the database, then copying it back to the target system.)

I don't know how much memory you have on your system or how large the database in question is.

Hope this helps.

Copper Super Contributor
Posts: 78
Country: Australia

Re: Database conversion issue when converting from 2008 to 2011

Get a copy of your original 2008 database. Open it up in ACT! 2009, to get it updated to that version, then try with 2011.  If you don't have ACT! 2009, try ACT! 2010. ACT! 2011 uses SQL2008R2, all earlier versions used 2005.

 

Basically go like this ACT! 2008 -> 2009 ->2011. The other thing is to download ACTDiag V14 from here, and use it to attach the database and run the ACTDiag checks again.

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Database conversion issue when converting from 2008 to 2011

Does your database contain custom fields called 'Territory' or 'Region'?  If yes, this can cause a schema error along with the 50000 error message.  If this is your situation, you can resolve it by opening the database in ACT! 2008 and renaming the fields (ex: Region1) or contact our Database Services for assistance (no charge for this particular service).  To contact our Database Services group, visit the following web page: Database Services

 

Here is an article with information about the schema/50000 error: KB Article 27837

Greg Martin
Sage