Community
Showing results for 
Search instead for 
Do you mean 
Reply

Unpacking/Restoring Remote Database Error

New Member
Posts: 3
Country: United States

Unpacking/Restoring Remote Database Error

Trying to share Desktop ACT Database with my laptop – both have separately licensed ACT Premium 2008 (10.0) Version 10.0.3.182, Hotfix1.

 

Have a Quad Intel Chip and separate C: (programs) and E: (data) hard drives. The act dBase is on the C: Drive.

 

Have performed Database Maintenance steps from within Act and from actdiag. and have disabled Database sharing.

 

Have successfully built remote database and copied "*.RDB" file to laptop.

 

Once laptop unpacks and restores the *.RDB file, I get this message:

 

"The database you are opening must be updated TOA newer version of ACT!. (This may take several minutes.) Before updating the database, ensure a recent backup is available. Would you like to backup the database now?

Warning: Backups taken with this version of ACT! Cannot be restored to a previous version. To restore this version, contact Technical Support.

YES/NO"

 

Regardless of whether I answer Yes or No, the database starts to be updated and then shortly after that, a new message appears:

 

"Exceptions occurred while executing Db Schema Update Script,

Check the Errors in C:\Documents and Settings\All Users\Application Data\Sage Software, Inc.\ Act! By Sage\10.3.182.0\_ACTSchemaUpdateResultsMK20911200902240.txt"

and the text in that message is:

 

LOCAL DATETIME: 2009-09-11 02:35:32

SERVERNAME: MUNSEY-KANE2\ACT7

ENGINE EDITION: 4 Express Edition

PRODUCT VERSION: 9.00.3042.00 (SP2)

SERVER COLLATION: Latin1_General_CI_AS

------------------------------------------------------------------------------

SYNC ENABLED: True

SYNC ROLE: SUBSCRIBER

------------------------------------------------------------------------------

DATABASE: MK1_ACT_DBase

STATUS: ONLINE

CREATE VERSION: 611

RECOVERY MODEL: SIMPLE

DB COLLATION: Latin1_General_CI_AS

AUTO CLOSE: 1

AUTO SHRINK: 1

AUTO CREATE STATS: 1

AUTO UPDATE STATS: 1

TORN PAGE DETECT: 0

 

ProductVersion

--------------------------------

9.00.3042.00

Configuration option 'user instances enabled' changed from 0 to 0. Run the RECONFIGURE statement to install.

CURRENT BUILD: 10.01.0189.0004

UPDATE BUILD: 10.03.0182.0000

-------------------------------------------------------------

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

TraceFlag Status Global Session

--------- ------ ------ -------

8017 1 1 0

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

SETTING DATABASE COMPATIBILITY LEVEL...

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

create_date compatibility_level user_access_desc recovery_model_desc

----------------------- ------------------- ------------------------------------------------------------ ------------------------------------------------------------

2009-09-11 02:33:31.437 90 MULTI_USER SIMPLE

-------------------------------------------------------------

----------------------------------------------------------------

NOW DROPPING ALL SYNC UPDATE TRIGGERS... (PRIOR VERSION = 10.01.0189.0004)

STARTTIME: 2009-09-11 02:35:33

ENDTIME: 2009-09-11 02:35:42

 

SETTING CTL_LOCALSTRING DATA...

SETTING TBL_SYSLOCALCOLUMN DATA...

 

 

*** Upgrading database to Schema Version 10.02.0026.0000 at 2009-09-11 02:35:44 ***

Altering table TBL_SYSTABLE

Altering table TBL_SYSCOLUMN

Msg 2705, Level 16, State 4, Server MUNSEY-KANE2\ACT7, Line 3

Column names in each table must be unique. Column name 'ALIASNAME' in table 'dbo.TBL_SYSCOLUMN' is specified more than once.

PROCESSING ERROR OCCURRED IN BUILD 10.02.0026.0000!

Msg 50000, Level 15, State 1, Server MUNSEY-KANE2\ACT7, Line 82

WORK WAS ROLLED BACK - EXITING FROM UPDATE!

 

FOOTER ENTRY TRANCOUNT = 0

Msg 50000, Level 25, State 1, Server MUNSEY-KANE2\ACT7, Line 13

***** Update of database failed! Exiting from update!

Msg 2745, Level 16, State 2, Server MUNSEY-KANE2\ACT7, Line 13

Process ID 51 has raised user error 50000, severity 25. SQL Server is terminating this process.

 

The end result is an endless loop that repeats each of the preceding messages.

 

Any suggestions would be welcome.

Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: Unpacking/Restoring Remote Database Error

If you create a new remote and then unpack it on the same machine you created on (the host machine) instead of the remote, do you get the same errors?

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

New Member
Posts: 3
Country: United States

Re: Unpacking/Restoring Remote Database Error

Thanks for the question, Greig. Am away from host PC (with only my laptop) until 9/20.  I'll check and let you know on the 20th.