Community
Showing results for 
Search instead for 
Do you mean 
Reply

After moving Main database from Windows 2003 server to PC Sync Error

Accepted Solution Solved
Copper Contributor
Posts: 5
Country: Australia
Accepted Solution

After moving Main database from Windows 2003 server to PC Sync Error

We have recently move away from a larger company into a new.  We have moved our Act! 2010 database (back up and restore) from a windows 2003 server to a Windows XP PC.  I can now log into the database and have share it between PC's, we have a total of 6 licenses and all the PC ones are working fine. 

 

We also have two laptop users with two remote databases.  We have been able to change the machine name and location correctly, so the laptops can now connect to the main.

The sync looks like it is progressing correctly, however when the checking for errors set is performed I get the Error message , as below from both Laptop databases.

 

[ Error | 26/05/2011 4:23:16 PM ]Message: Synchronization has failed. Server Error Description: Setuser failed because of one of the following reasons: the database principal 'dbo' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

 

Can someone give me some assistance on where my issue is.  Many Thanks Rachel

 


Accepted Solutions
Solution
Accepted by topic author Rachel_C
‎09-25-2015 03:20 AM
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: After moving Main database from Windows 2003 server to PC Sync Error

Hello Rachel,

Welcome to the ACT! Online Community!

 

When moving an ACT! database that has remote databases syncing to it, unfortunately using the backup/restore process will strip out the remote sync information.  The database has to be moved manually (basically copy/paste) and then the host computer name updated on the remote.  You can verify if the remotes are still being tracked by the main database through the Tools > Synchronization Panel > Manage Database option.

 

You'll have to decide which is the best 'next step', depending on how long it has been since you moved the database and how many changes may have been made in that time.

 

Option 1: If you still have access to the original database files (old company server), you can copy them onto your new host pc and get the sync working with the original remotes.  However; any changes you have made to the existing database on the new host will have to be exported into the newly copied database.

 

Option 2: Create new Remote databases.  After restoring the remotes on the laptops, you can then import the original remote databases into the new remotes.  It is recommended that you backup the original remotes and restore them on the host computer to import directly into the main database before creating the new remotes (to cut down on information that will have to sync).

 

Here are some articles that may help explain the processes:

- How to move an ACT! database and retain synchronization: KB Article 19817

- Best practices for import/export from database to database: KB Article 17539

- How to create a remote database: KB Article 14116

 

 

Greg Martin
Sage

View solution in original post


All Replies
Solution
Accepted by topic author Rachel_C
‎09-25-2015 03:20 AM
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: After moving Main database from Windows 2003 server to PC Sync Error

Hello Rachel,

Welcome to the ACT! Online Community!

 

When moving an ACT! database that has remote databases syncing to it, unfortunately using the backup/restore process will strip out the remote sync information.  The database has to be moved manually (basically copy/paste) and then the host computer name updated on the remote.  You can verify if the remotes are still being tracked by the main database through the Tools > Synchronization Panel > Manage Database option.

 

You'll have to decide which is the best 'next step', depending on how long it has been since you moved the database and how many changes may have been made in that time.

 

Option 1: If you still have access to the original database files (old company server), you can copy them onto your new host pc and get the sync working with the original remotes.  However; any changes you have made to the existing database on the new host will have to be exported into the newly copied database.

 

Option 2: Create new Remote databases.  After restoring the remotes on the laptops, you can then import the original remote databases into the new remotes.  It is recommended that you backup the original remotes and restore them on the host computer to import directly into the main database before creating the new remotes (to cut down on information that will have to sync).

 

Here are some articles that may help explain the processes:

- How to move an ACT! database and retain synchronization: KB Article 19817

- Best practices for import/export from database to database: KB Article 17539

- How to create a remote database: KB Article 14116

 

 

Greg Martin
Sage