2 windows service components handle message synchronization for the Sage SalesLogix Mobile platform. The connector and Real-Time sync engine handle the synchronization process in different ways. Firstly the synchronization data is created and passed through the connector for all synchronization scenarios. The real-time engine is responsible for detecting and notifying a users device that new data (that has been identified in a watch) exists in the main database. If we look as the connector as the right hand, and the real-time sync as the left hand there is a time were the right does not know what the left is doing. This occurs specifically when you initiate the full sync on the device (initial load) and real-time is enabled. Since real-time is is initiated and the full sync has started and can take some tome to process it is possible that the real-time can disrupt the load process. This happens because the when a real-time sync occurs it looks into the queue to see if another sync is occurring and cancels it with the assumption that the current state of the database is newer and the changes will rollup, with the hope of reducing bandwidth requirements. In most scenarios this would be a good thing except for the initial load where having the load canceled is not such a good thing.
To get around this issue ensure that your admin does not turn on real-time sync for a given user until their initial load is completed. This will allow the connector to work undisturbed and get the load data onto the users device.