Corrupt Sync Events
Corrupt Sync events occur when the sync log contains errors. If you are seeing messages about corrupt sync events and SmartSync Repair is unable to fix them, run a manual reconciliation to repair the corrupt sync events.
The most commonly reported types of corruption are:
- Missing SmartSync event - events from a SmartSync session are sequentially numbered. A SmartSync event is missing when there are any gaps in the sequence.
- Corrupt SmartSync event - events are assigned a unique identifier and checksum information based on the contents of the event. A SmartSync event is corrupt when the unique identifier and/or the checksum do not agree with the contents of the event.
Causes of Corruption
Corruption can be caused by:
- A hardware failure.
- An unrecorded log entry.
- A corrupt log entry.
SmartSync keeps the synclog.slg file open while it is attached to a sync copy. While SmartSync is susceptible to network issues, processes are in place to decrease client impact. As with any network application, systemic network issues will result in data corruption. The existence of network issues should be investigated and reported.
Contact CaseWare Support for assistance in retrieving information from badly corrupted sync files.
SmartSync Server
The errors described do occur when using Working Papers with SmartSync in combination with SmartSync Server, as the server runs server side data verification. For firms with small IT departments looking to use SmartSync, switching to Cloud would be recommended.
