Community
Showing results for 
Search instead for 
Do you mean 
Reply

Can't upgrade my Act 8 DB to Act 2008

New Member
Posts: 1
Country: FRANCE

Can't upgrade my Act 8 DB to Act 2008

I have upgrad my ACT8 intallation to Act10 (French version) on Windows XP pro SP2

When i open my ACT8 DB in Act10, the upgrading beging and is stop and Act10 said to see the contain of this file :

 

    LOCAL DATETIME: 2008-05-14 22:18:01
       SERVERNAME: ACER-19B694409A\ACT7
   ENGINE EDITION: 4  Express Edition
  PRODUCT VERSION: 9.00.3042.00 (SP2)
 SERVER COLLATION: Latin1_General_CI_AS
------------------------------------------------------------------------------
     SYNC ENABLED: False
        SYNC ROLE:
------------------------------------------------------------------------------
         DATABASE: DimTel10
           STATUS: ONLINE
   CREATE VERSION: 611
   RECOVERY MODEL: SIMPLE
     DB COLLATION: Latin1_General_CI_AS
       AUTO CLOSE: 0
      AUTO SHRINK: 1
AUTO CREATE STATS: 1
AUTO UPDATE STATS: 1
 TORN PAGE DETECT: 1
 
Configuration option 'user instances enabled' changed from 0 to 0. Run the RECONFIGURE statement to install.
 CURRENT BUILD: 08.02.0080.0000
  UPDATE BUILD: 10.01.0189.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                                         
----------------------- ------------------- ------------------------------------------------------------ ------------------------------------------------------------
2008-05-14 20:38:39.460                  90 MULTI_USER                                                   SIMPLE                                                      
-------------------------------------------------------------
----------------------------------------------------------------
NOW DROPPING ALL SYNC UPDATE TRIGGERS... (PRIOR VERSION = 08.02.0080.0000)
STARTTIME: 2008-05-14 22:18:04
  ENDTIME: 2008-05-14 22:18:15
 
SETTING CTL_LOCALSTRING DATA...
SETTING TBL_SYSLOCALCOLUMN DATA...
 
 
*** Upgrading database to Schema Version 09.00.0002.0000 at 2008-05-14 22:18:17 ***
Altering table TBL_CONTACT
   setting metadata...
 
*** Upgrading database to Schema Version 09.00.0003.0000 at 2008-05-14 22:18:19 ***
Creating table TBL_SYSCOLUMN_ACL
   applying foreign keys...
   setting metadata...
 
*** Upgrading database to Schema Version 09.00.0006.0000 at 2008-05-14 22:18:20 ***
Re-creating table TBL_SYSCOLUMN_ACL
Altering table TBL_GROUPQUERY
 
*** Upgrading database to Schema Version 09.00.0007.0000 at 2008-05-14 22:18:21 ***
Altering table TBL_COMPANYCONTACT_MAP
Altering table TBL_EVENTLOGTYPE
Creating table TBL_PASSWORDHISTORY
   setting metadata...
Dropping Column Constraints for table :
  Column Constraint TBL_USER.TBL_USER_ISALLOWDEVICESYNC_DEF
Dropping Column Constraints for table :
  Column Constraint TBL_USER.TBL_USER_ISALLOWACCOUNTINGLINK_DEF
Altering table TBL_USER
  Adding columns...
   setting metadata...
 
*** Upgrading database to Schema Version 09.00.0012.0000 at 2008-05-14 22:18:23 ***
Altering table CTL_DBCONFIG
Altering table TBL_PREFERENCE (Password Policies)
 
*** Upgrading database to Schema Version 09.00.0020.0000 at 2008-05-14 22:18:23 ***
Altering table TBL_EVENTLOGTYPE
Altering table TBL_SYSCOLUMN (Last E-mail)
 
*** Upgrading database to Schema Version 09.00.0027.0000 at 2008-05-14 22:18:23 ***
Altering table TBL_HISTORYTYPE (E-mail Attachments)
Altering table TBL_HISTORY (E-mail Attachments)
Altering table CTL_DBCONFIG (COPYDATA METHOD)
Altering table TBL_SYSDOMAIN_SYSOPERATOR
 
*** Upgrading database to Schema Version 09.00.0032.0000 at 2008-05-14 22:18:26 ***
Creating table TBL_SYSTABLEDOMAIN
  loading data...
Dropping Column Constraints for table :
  Column Constraint TBL_SYSTABLE.TBL_SYSTABLE_TABLEDOMAIN_DEF
Altering table TBL_SYSTABLE
  dropping old column...
  adding new column...
  setting TBL_SYSTABLEDOMAIN metadata...
  setting TBL_SYSTABLE metadata...
  indexing TBL_SYSTABLE table...
  applying foreign key...
 
*** Upgrading database to Schema Version 09.00.0033.0000 at 2008-05-14 22:18:26 ***
Altering table TBL_SYSCOLUMN
  setting metadata...
 
*** Upgrading database to Schema Version 09.00.0053.0000 at 2008-05-14 22:18:27 ***
Altering table TBL_USER
  setting metadata...
 
*** Upgrading database to Schema Version 09.00.0058.0000 at 2008-05-14 22:18:27 ***
Altering table TBL_HISTORY (*.IMA E-mail Attachments)
 
*** Upgrading database to Schema Version 09.00.0093.0000 at 2008-05-14 22:18:27 ***
Converting Read-Only Columns...
 
*** Upgrading database to Schema Version 09.00.0100.0000 at 2008-05-14 22:18:28 ***
Creating table TBL_LOGONHISTORY
  setting metadata...
  setting indexes and keys...
Altering table TBL_USER
  setting metadata...
 
*** Upgrading database to Schema Version 09.00.0104.0000 at 2008-05-14 22:18:28 ***
Altering table TBL_PICKLIST
 
*** Upgrading database to Schema Version 09.00.0116.0000 at 2008-05-14 22:18:28 ***
Altering table TBL_ATTACHMENT
Altering table TBL_SYSCOLUMN (Metadata)
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
Altering table TBL_SYSTABLE (Metadata)
 
*** Upgrading database to Schema Version 09.00.0145.0000 at 2008-05-14 22:18:35 ***
Altering table CTL_SYNCDBMAPINFO
Altering table CTL_SYNCDBMAPINFO_HISTORY
   setting metadata...
 
*** Upgrading database to Schema Version 09.00.0532.0000 at 2008-05-14 22:18:35 ***
Adding ACT! BUSINESS LINKS tables
  applying ACT! BUSINESS LINKS indexes...
Altering table TBL_SYNCDB
Dropping Column Constraints for table :
  Column Constraint TBL_SYNCDB.TBL_SYNC_TYPENUM_DEF
  Column Constraint TBL_SYNCDB.TBL_SYNCDB_TYPENUM_CHK
Creating table TBL_SYNCDBTYPE
  adding entries to table TBL_SYNCDBTYPE
  adding ABL and TBL_SYNCDBTYPE Foreign Keys...
Adding new Datatype XML...
Adding new entries for TBL_SYSTABLEDOMAIN
  setting ABL TABLE metadata...
  setting ABL COLUMN metadata...
  setting ABL KEY/INDEX metadata...
 
*** Upgrading database to Schema Version 09.00.0535.0000 at 2008-05-14 22:18:37 ***
Dropping table CTL_ABL_QUEUEMGR
Dropping FK Constraints against table :
  Foreign Key Constraint CTL_SYNC_DEVICETABLE.SYNC_DEVICETABLE_SYNCDB_TYPENUM_FK
  Foreign Key Constraint TBL_SYNCDB.SYNCDB_TYPENUM_FK
Dropping Constraints on table TBL_SYNCDBTYPE:
  Key Constraint TBL_SYNCDBTYPE.TBL_SYNCDBTYPE_PK
Altering table TBL_SYNCDBTYPE
  re-populating TBL_SYNCDBTYPE table...
  adding TBL_SYNCDBTYPE Foreign Keys...
  setting Column metadata...
  setting Key metadata...
Altering table TBL_SYSCOLUMN (Metadata)
Creating table CTL_SYNCSETTYPE
  populating CTL_SYNCSETTYPE...
Altering table TBL_SYNCSET
  setting TYPENUM values...
Dropping Column Constraints for table :
  Column Constraint TBL_SYNCSET.TBL_SYNCSET_ISDEVICESYNCSET_DEF
  setting Table metadata...
  setting Column metadata...
  setting Key metadata...
 
*** Upgrading database to Schema Version 09.00.0538.0000 at 2008-05-14 22:18:39 ***
Altering table CTL_ABL_DBCONFIG
  setting Column metadata...
 
*** Upgrading database to Schema Version 09.00.0543.0000 at 2008-05-14 22:18:39 ***
Dropping FK Constraints against table :
Dropping Constraints on table CTL_ABL_DBMAPPING:
  Key Constraint CTL_ABL_DBMAPPING.ABL_DBMAPPING_ACT_COLUMNID_FK
  Key Constraint CTL_ABL_DBMAPPING.ABL_DBMAPPING_DBID_FK
  Key Constraint CTL_ABL_DBMAPPING.CTL_ABL_DBMAPPING_PK
Altering table CTL_ABL_DBMAPPING
Altering table CTL_ABL_LINK
 
*** Upgrading database to Schema Version 09.00.0553.0000 at 2008-05-14 22:18:39 ***
Altering table CTL_ABL_LINK
  creating Index...
  setting Column metadata...
  setting Keys metadata...
 
*** Upgrading database to Schema Version 09.01.0038.0000 at 2008-05-14 22:18:40 ***
Altering table TBL_FEATURESET
  setting Column metadata...
  setting indexes and keys...
Altering table TBL_PERMISSION
  setting Column metadata...
  setting indexes and keys...
Altering table TBL_ROLE
  setting Column metadata...
  setting indexes and keys...
 
*** Upgrading database to Schema Version 09.01.0067.0000 at 2008-05-14 22:18:40 ***
Interogating Device Syncsets...
Msg 8152, Level 16, State 13, Server ACER-19B694409A\ACT7, Line 135
String or binary data would be truncated.
The statement has been terminated.
Msg 50000, Level 16, State 1, Server ACER-19B694409A\ACT7, Line 143
ERROR UPDATING ALL USER SYNCSET NAMES
Msg 50000, Level 25, State 1, Server ACER-19B694409A\ACT7, Line 193
ROLLING BACK DEVICE SYNCSET FIX
Msg 2745, Level 16, State 2, Server ACER-19B694409A\ACT7, Line 193
Process ID 63 has raised user error 50000, severity 25. SQL Server is terminating this process.

 

 

 

Thanks for any suggestions,

 

FRB