The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
"Junk" TEF files
Posted: 24 Oct 07 2:50 PM
|
We are utilizing the Sync Report provided by Mike Spragg and sporadically we get users marked as non synching for a month or so. When I do check their TEF in the outgoing folder, I usually find one or few files that are a month old and the rest of files are 2 days old at most, which is of course screwing up the report since it looks at the oldest file date.
SAGE’s tech suggested that it happens when user's KeyBase changes, but some users that we have an issue with have an A1 keybase, so obviously this is not the case.
Has anyone else encountered a "junk" TEFs issue?
|
|
|
|
Re: "Junk" TEF files
Posted: 25 Oct 07 3:12 AM
|
| Have you opened them to see what's in them ? Most odd they're not being collected by SyncClient. |
|
|
|
Re: "Junk" TEF files
Posted: 25 Oct 07 8:18 AM
|
| I have looked inside a few, nothing particular. No pattern, nothing more or less common in them. |
|
|
|
Re: "Junk" TEF files
Posted: 25 Oct 07 8:46 AM
|
| 'Don't know if this is the answer, but you should check to see if the Tef's sequence number are leaving a gap. When the remote client hasn't processed a series of Tef's in the correct order, the sync server keeps sending signals to the client. It has to get past the missing sequence numbers. Also look in the failed transaction folder to see if there is a problem with that specific user. |
|
|
|
Re: "Junk" TEF files
Posted: 25 Oct 07 12:16 PM
|
I use mike's sync report too. It's an outstanding tool!
With the remote user issue you are having I find it easiest to diagnose from the remote end. Look on the remote's machine at this directory:
**C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Infiles**
Typically if there are files in this folder and if the user has been complaining that stuff is missing from their database then I will create/install a new remote database for the user. This typically fixes the output of the sync report and restores the data the remote was missing.
|
|
|
|