Community
Showing results for 
Search instead for 
Do you mean 
Reply

Sync errors following hitting 4gb limit and upgrade to sql 2005

Loyal Listener
Posts: 42
Country: United_Kingdom

Sync errors following hitting 4gb limit and upgrade to sql 2005

A similar error occured while using Act 2008 premium, but following advice from UK support the main machine was upgraded to Act 2010 sp1 hf1 and the existing database opened (SQL 2005 FULL SP3)

A brand new Windows 7 Business 32bit vm was used to host a remote database with Act 2010 premium sp1 hf1 the database imported with no errors a note was added to the user record and sync started. it failed with:

 

Sync processing error occurred in database object PRC_SYNC_PROCESS_SCHEMA querying data (UPDATE), table TBL_SYNCDB

 

How would you proceed?TIA
Paul
 note the database synched several times after the full version of sql 2005 sp3 was installed on Act premium 10.0.02 191 hf1, the above error occured after trying to delete a user on the server when the operation timed out. That user has since been deleted but remotes have been unable to sync, whether existing db's or newly created ones
TIA

Paul M Tate
Platinum Elite Contributor
Posts: 14,387
Country: Australia

Re: Sync errors following hitting 4gb limit and upgrade to sql 2005

What version of ACT! are you running now?

How big is the ADF file?

 

Have you tried running all the database repair options in ACTDIAG ... especially the schema repairs?

Loyal Listener
Posts: 42
Country: United_Kingdom

Re: Sync errors following hitting 4gb limit and upgrade to sql 2005

ACT! by Sage Premium 2010 Version 12.1.181.0, Hot Fix 1

adf = 3.5gb

ran all the options in ACT  2008 not yet in 2010 will run on 2010

 

not sure if relevant but a file created (2010_pmt_ActObjectCreationResults.txt)  I presume when the remote db was created has:

 

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.  --- several of these
*** Setting rights on procedures...
*** Setting rights on tables and views...
Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.PRC_UPD_USER_COLUMNACCESS'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.
Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.PRC_UPD_USER_COLUMNACCESS'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.

TIA

Paul M Tate