Incomplete Data on Desktop

Question

Hi! Everyone
We are working wit MAM 25 SR5 SP21.
We do have the following parameters  set on the MobileEngine.config file:
MobileEngine.Sync.RepetitiveSyncEnabled=true
MobileEngine.Sync.MaximumNumberOfRepetitiveSyncs=10
MobileEngine.Sync.TimeBetweenRepetitiveSyncs=1000
We do use this parameters for both PDA and Laptops.
On PDA we sync only once and we get the synchronization process successfully complete. (First time and second time,  third time, .......... and always)
BUT on portatil we do have to try the sync process many times. I t is not constant. Firs time of sync process the data comes ok with only once sync process. But after frist synchronization process,  when we need to sync again we have to try the sync process more than once some times I have tried 8 times in order to get new data.
I have change the maximumNumberOfRepetitiveSync to 50 and to 100 but I got error.
Can anyone tell me how can I set the right parameters in order to get a complete synchronization process ? The best option would be if I can have only one set parameter for both PDA and Portatil.
Thank you very much
Xiomara

Answer 1

Hi Xiomara,
if I read this - do you have the same MEREPMETA.XML file in PDA and Laptop? We know there is a different MAM version for Laptop and for PDA available. You can run the PDA version on Laptop as well - so while it is working on the PDA as you said, could you please check if it makes a difference in the sync, if the PDA version is used on the Laptop?
From your findings I would expect, that even you set the repetitive sync to a very high number, it does only run one time. Set the trace level on the PDA to all and check the log file after the sync You can see how often the Laptop syncs after you pressed the button. I think it will tell you it runs only one time.... This means either the SyncBOs on the Laptop are not set to Synchronous, or you have a simple misstiping of the repetitive parmeters on the Lapop.
Please check, if both things are correct we can look a little deeper into the issue - but I would expect that one of these two things causes your problem.
But anyway: going Larisses way will cure the problem from the other side - cause the data is prepared already in theoutbound queue and with the next sync the data coes down to the device. Only problem: you need to run the distributor before you sync and this will not solve the first issue in my understanding of the process.
Hope that helps!
Regards,
Oliver