Community
Showing results for 
Search instead for 
Do you mean 
Reply

Synchronization fails

rsg
New Member
Posts: 1
Country: United States

Synchronization fails

We have ACT 2008 (10.0.3.182 Hotfix 1) installed on a Windows 2008 Server fileserver and also on several PCs as well as a laptop which has a remote database.  We recently installed this new server and moved the database to it using the procedure that is supposed to preserve the synchronization (disassociated the database on old server, etc.).

 

All permissions have been set for access and the folder in which the database resides is in a shared folder with inherited all access rights.  Everyone can access the database on the new server just fine, but the laptop user cannot sync his remote database any more.

I have disabled the firewall on the server and his laptop and have verified thru the cmd netstat that his laptop does indeed open a connection to port 65100, which is normally "listening", so I see a connection there.

The database is set to accept incoming syncs and it is set as the publisher database.

His synch settings have been changed to reflect the *new* server name instead of the old and the port is correct at 65100.

 

The sync log is as follows:

 

======== SYNC SESSION - 8/25/2009 11:27:16 AM ========

[ Info | 8/25/2009 11:27:16 AM ]Message: Synchronization started.
[ Info | 8/25/2009 11:27:16 AM ]Message: Server object created.
[ Info | 8/25/2009 11:27:16 AM ]Message: Checking if schema changes are available for sync.
[ Info | 8/25/2009 11:27:18 AM ]Message: Server establishing synchronization with remote database: CM
[ Info | 8/25/2009 11:27:18 AM ]Message: Server generated remote sync session identifier: bcf1ca2a-26a4-464c-81cd-a505e9eae0ae:<CM>
[ Info | 8/25/2009 11:27:20 AM ]Message: Checking if data changes are available for sync.
[ Info | 8/25/2009 11:27:27 AM ]Message: Server initialized database send session: 205
[ Info | 8/25/2009 11:27:33 AM ]Message: Server initialized.
[ Error | 8/25/2009 11:27:38 AM ]Message: Synchronization completion failed. 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 anybody help me with this? 

Moderator
Posts: 4,395
Country: USA

Re: Synchronization fails

Try running database maintenance from actdiag.

 

Database Rebuild and Repair Procedures