|
| |
| |
|
Re: The Sync client Often prompt "The files XXXXXXXXXX was ignored because it is newer than your database."
Posted: 10 May 06 3:15 PM
|
buy naltrexone no prescription buy low dose naltrexone online read where to buy low dose naltrexone fiogf49gjkf0d Originally posted by Kener Liu
The Sync client Often prompt "The files XXXXXXXXXX was ignored because it is newer than your database." Which reason? How to resolve? |
|
Kener,
Simiply put, you need to create and attach a new remote database for the user onto their machine.
What has happened is the remote user is still updating the old database on his/her machine and is trying to apply TEFs to the database. Any updates to the main databse will not be synced to the user because the keybase on the users old database is lower then the current keybase. |
|
|
|
Re: The Sync client Often prompt "The files XXXXXXXXXX was ignored because it is newer than your database."
Posted: 11 Jun 08 6:40 PM
|
Hi there,
I also get this message, but it remains even after I cut and attached a new remote database. The remote client is in a timezone GMT+8 while the server is GMT+2. Might that have any bearing?
I was under the impression that the database version is determined by the prefix only, but it seems the prefix somehow stays the same on the remote client even after the new remote database was cut and attached. Could it be that there is an indicator I have to change somewhere on the remote? |
|
|
|
Re: The Sync client Often prompt "The files XXXXXXXXXX was ignored because it is newer than your database."
Posted: 12 Jun 08 8:48 AM
|
Take a look at Resolution ID: 459360 in the Sage SalesLogix Knowledge base.
It's possible the "new" db actually "merged" with the old db on the remote. Nobody knows exactly how/why this happens.. but it has happend occasionally.
The fix is listed in the kb article: - basically: a - Force a full sync cycle manually (remote and main) b - Cut a new remote db (make sure that sync - or any other db activity is NOT happening) c - Delete ALL tefs with the incorrect keybase from all locations (including archives) d - MANUALLY detach the remote db and delete it (or move it) e - MANUALLY attach the new remote db f - Open the remote client to see that you can log in.. g - Manually force a sync on teh main and remote
-- RJLedgert - rjlSystems "...Customer First..." |
|
|
| |
| |
| |
| |
|