Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ACT 6 - Sync packet intended for another database

Status
Not open for further replies.

JohnBlight

Technical User
Jan 22, 2007
4
GB
We're running ACT 6.03, with a master database and several distributed databases. When a new distributed database runs its first sync to pick up a packet containing all records from the master database, a message is displayed claiming the packet is meant for another database, and specifying that database's name. It will be the name of one of the other distributed databases. We can choose to accept it.

Does this behaviour suggest a problem? Presumably, the sync packet has some embedded information identifying a database. If so, where does this information come from?

Any suggestions would be appreciated.
 
It doesn't always mean a problem if it's like this error
But, it can also suggest you have not set up your remote database correctly wither thrie oen correct UniqueID and may be damaging your database from that sync setup.

What is the process you use to create the new remote database?

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust
For ACT! by Sage and ACT! for Lotus Notes
 
Thanks for the reply, Mike.

We synchronise through shared folders. We create a distributed database by saving an empty copy of the master database, assigning the 'My Record' by specifying the user's contact record.

It hasn't seemed to have caused any problems, as the system of a master database and several distributed databases seems to have been working as expected.

It would just be useful to know the reason for the observation.
 
To be honest it's been a few years since i've seen it, and can't remember the cause. From the records I have, it shouldn't be a problem as long as you created an empty copy that should have it's own UniqueID.

I always like to recommend that you make sure you have your backups and maintenance down consistently, like the sync itself... one way to keep this reliable is to use a product like AutoAdmin II -

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust
For ACT! by Sage and ACT! for Lotus Notes
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top