![]() I sure have and i can assure it is a mess. There is nothing special about any of these records that sync into your DEVONthink database incorrectly. There is no way to know either when DTTG or why DTTG will do this. Just delete them all as there’s nothing in them even though when they were created there was.Īs I said, I’ve found the majority of this comes from DTTG and is persistent and replicable. Sometimes if you do a column view by file size, any file that is a size of zero is a corrupted/false record. It is very manual and extremely labour intensive. ![]() There is absolutely no way around the above process. However, should you need to do a full sync from scratch or Dropbox goes into a full sync from scratch mode that can happen, if there are any false records in your database, you will have to go through the above process. Once sync’d, even if a false/corrupted record gets back into your database, it Dropbox will keep sync’g. I spent a whole afternoon once deleting multiple records and then finally my database was fully sync’d. Eventually, the whole database will sync. However, if there is more than one record that is corrupted, Dropbox will stop at each one and you will need to delete each one. Record the name correctly and do a search and you’ll find this record. You need to be able to get to the “commit” point in the sync for a true sync to happen.įortunately, if you have the activity monitor on while your sync’g everytime Dropbox fails it will identify the record it has failed. That is, if you manually scan through the records in your database, there will be a record that has a header and nothing in the data field. I don’t know how you use your database but in my case I use it extensively with DTTG a dreadful product. Dropbox will not sync the database if it detects improper files. Tools verify and repair or rebuilding the database will not help at all in this case. I do automatic syncing in DevonThink upon database opening and closing. I am very careful not to start DevonThink until I am sure that Dropbox has fully synced with the computer. I can do this over and over until I manually delete the offending link, remove it from the trash, verify and repair and then re-sync.Īt present, when this happens, it is only a file or two, and typically seems to be related to an email as the originating document.Īt this point, I’ve always been able to recreate the entry after the fix, but I’m concerned about data loss. Run Tools->Verify and Repair again, and the same problem is found and reported as repaired. But when I do the next sync, the sync log reports the same problem again. I select repair and the program reports that the problem has been fixed. I will run Tools -> Verify and Repair, which reports that the problem has been found. Then, I will get a sync error on the work machine, usually due to a “file not found” type of error. Although dropbox syncs almost daily on my laptop, it may be many days between usage of DevonThink Pro on that computer. I sync with Dropbox realtime / daily at work. I mostly use the desktop at work with DevonThink Pro as my daily project management tool. I have two computers, and iMac desktop and a MacBook air laptop. I am still having issues, but I’m having trouble pinpointing what is happening. Why is this? Should the rebuild not just restore to the most recent condition, leaving the same number of conflicts, if any?Ī simple verify and repair did not work. Quite annoying!Īfter a database rebuild there seem to be hundreds of new conflicts. So the user has to start again at a later date. But there is no way to proceed with the Sync with the resolved records so far, leaving any remaining conflicts for a later date. Let’s say the user manually resolves a bunch of record conflicts, but there are still more to go (and there is no count). Sometimes, there are conflicts listed for records that have not been touched for several weeks. “Same content, different folder” or “Tag Name Change” etc. So, why the difference error? Perhaps some helpful clue could be provided. ![]() And all the modification dates/times are also the same. Sometimes the two “conflicted” records seem to be identical. Use all the records from the Local Database (or Server).Īlways use the record that smells most sweetly of new-mown grass.Īpparently identical Records (in Conflict). Use the records that have the most recent Content Modified value. Use the records that have the most recent Modification Date-Time. Also, I know there is a slider, but this has no scale, range or numbers.īox: “Resolve All Conflicts The Same Way”. Would gives the user an idea of the scale of the solve (and time needed to process). Initial Total Unresolved Records & Records Still Remaining Unresolved (& %). Sometimes it may be just a few, but sometimes it can be hundreds. There is no indication of how many records need to be resolved. Having some issues with the local server database sync process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |