quadbyte

Finally my solution, it took me quite a while ... Find out the corresponding DB name (the file .sync\ID contains this name as hex value) Close Resilio sync (be sure - in windows resilio may remain in the tray icon and has to be closed by the context menu) Backup the sync.dat (e.g. copy as sync.dat.SAVE) Open the sync.dat with an BEncode editor (in the following I use torrent-file-editor). Switch to the 'tree' view. Remove entry '.fileguard' Select the correct folder (check the DB name: folders > #Index > fc > db_name) Remove under 'errors' the entry 'dictionary' ['Wörterbuch'] ('errors' will remain as an empty list) Save (select encoding of the original file first ['Kodierung']) (in my case 'windows-1252') Done. After Restart of Resilio for locked files the triangle is visible again in the folder view.

When I close and reopen the file the situation remains the same: The warning triangle is only visible in the 'history', not in the 'folder' view. The information about this behavior is being stored in the sync.dat, I have not yet figured out how. The rebuilding of the database is a good hint that I did not know, even though it does not solve my problem.

Hello, When I try to sync a locked file (e.g. a document being opened by ms word) I see a triangle in the 'folder' view. Clicking on that triangle further shows me the kind of problem like 'no permissions to acces the x file' - with the option 'Ignore' or 'Ignore all'. After clicking 'Ignore all' the triangle and the message shows up only in history if I filter with 'warnings', but not anymore in the 'folder' view. So my question is: How can I reset / undo this behavior to be again notified in the 'folder' view? I am using version 2.7.2 (1375) Regards, K.

When using BTSync to synchronize volume E:\ I happened to encounter a strange behaviour: After a while new files were not synched although BTSync claimed to have done so. After heavy testing I noticed an even more strange behaviour: Folders alphabetically preceeding the folder 'System Volume Information' were not mentioned when synching neither single files in the root folder. Trying to re-index folder E:\ (remove then re-add the folder) would suddenly lead to consider only a few files instead of thousands being on the volume. Enabling debug logging uncovered the following error: Got error 5 while obtaining file info for \\?\E:\System Volume Information. After encountering this error, BTSync stopped synching (but claimed that synching was sucessfull). The folder 'System Volume Information' was at first not accessible to view its content, I had to add appropriate rights (added it to the group of Administrators). In there I found a file named 'tracking.log'. After the date of the timestamp of that file, BTSync had stopped working properly. When I had given access to 'System Volume Information' folder, BTSync worked properly again. The file 'tracking.log' is created by 'LocalSystemNetworkRestricted' via svchost.exe (One can verify this by using e.g. the Windows 7 resource monitor). It seems to be created in the root folder 'System Volume Information' on every drive. So what exactly happened? BTSync tries to scan every folder (starting alphabetically at the last one), encounters missing access rights on 'System Volume Information'. It then stops working but claims that synchronizing has been done. Solution: Grant access to the folder and BTSync will work properly again. (It does not help to simply exlude that folder in the .SyncIgnore file) Maybe this my observation may help someone.