I know this has been covered before.

I am setting up a new Remote Office and can seam to get SLX to Sync correctly. I am receive the message above.I found a earlier post that says to do the following

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 the main and remote

Which I have done with the same message about files being ignored. I have even deleted the Remote Office and recreated it and then cut a new Database and I still can't get it to Sync.

Any Ideas?

Thanks

Marc

After you execute the Sync Cycles, and before you cut the new Remote DB, make sure that you also delete the files from the Outfiles and Archives that match the Site Code.

There are 2 parts that identify any remote Database, the Site Code and the Kay Base.

As you cut newer versions of the Database, if you choose not to change the Site Code, the Key Base is increased.

For Example, my Site Code is ABCD and my Key Base is now A5 (meaning that I have cut 6 versions of my DB - it starts at A0).

Now, lets say I cut a new version of my Remote and don't apply it. Now the Sync Server is going to be sending files with a Key Base of A6, which the Remote Database will reject stating that they are "newer than your database".

So, the solution is to make sure that your remote has the latest version of the Database. This is why the Instructions to solve this issue indicate to Cut a new Remote and manually attach it, to verify that the Remote's Key Base matches the value that is stored on the Server.

According to the Server at the Main site it is sending files for Key Base A0. How can I verify what Key Base the remote system is looking for?