We are aware of this issue and working to fix it. As a workaround, you may try the following:
1. Go to your storage folder (the place where Sync stores all the DB files and service data).
2. Create a debug.txt file.
3. Put the "00000000" value there (eight zeros, no quotes).
4. Save and restart Sync.
It should no longer corrupt your ID files.
i've been trying to run this between two Synologies (213j -> 215j) for weeks now on the latest version 2.0.
NOTHING but constant database errors and ID file corruptions. I have tried this above fix - didn't work. I'm looking at other sync applications at the moment, as 4 weeks and still only 3/4 through syncing less than ten folders across 1.7TB of data on GB lan is crazy, and I refuse to offsite the second NAS if it is not reliable.
The database errors aren't ideal but could be lived with, I guess. The corruption is not livable with and breaks this entire product. no way I would consider going pro under these conditions.
It is also maxing the CPU on both boxes up to 100% a lot, and consuming a lot of memory - something no other app has done on either NAS.
If there isn't a fix very shortly, I will move to anything else no matter how painful the move, as ongoing pain is worse!
[Solved] "cannot Identify The Destination Folder" Related To Low Memory? Also, Possible .sync/id Corruption
in Sync Troubleshooting
Posted
i've been trying to run this between two Synologies (213j -> 215j) for weeks now on the latest version 2.0.
NOTHING but constant database errors and ID file corruptions. I have tried this above fix - didn't work. I'm looking at other sync applications at the moment, as 4 weeks and still only 3/4 through syncing less than ten folders across 1.7TB of data on GB lan is crazy, and I refuse to offsite the second NAS if it is not reliable.
The database errors aren't ideal but could be lived with, I guess. The corruption is not livable with and breaks this entire product. no way I would consider going pro under these conditions.
It is also maxing the CPU on both boxes up to 100% a lot, and consuming a lot of memory - something no other app has done on either NAS.
If there isn't a fix very shortly, I will move to anything else no matter how painful the move, as ongoing pain is worse!