Where to store your Endnote library, or not to store it
The EndNote Synchronization process is sensitive to the location where the library is stored.
If the storage location is a network drive or an external drive, this can pose a latency issue with saving and sending information which can disrupt the library. Even more disruptive can be ANY process that attempts to Copy EndNote Library files while the EndNote library is open.
This includes any backup process that dynamically scans, and transfers data. Backup processes like Time Machine, Backblaze, Carbonite can perform this way.
As does most synchronization services: iCloud, DropBox, OneDrive, SuiteSync, GoogleDrive, Box, etc.
If the EndNote library is stored in a hostile location, Sync is eventually going to collapse as the library becomes more and more damaged by conflicts during EndNote’s save process.
The solution is to save the library in a location which is not hostile (local and not synced by anything).
The above does not apply to Endnotes included sync functionality.
Alfasoft cannot tell you where to store your library as the set-up of every computer varies. All we can do is explain where you should not store your library, and why.
The technical reason is that EndNote needs to save several files in a specific order. If one of these files are simultaneous synced, then EndNote cannot save to it and the library may be corrupted.
Always make sure your library file is local to the system’s hard drive, and not on a network drive, or in an iCloud, DropBox, Onedrive-style synchronized folder.
This article goes quite a long ways to outline the issues between database files (EndNote library or MS Access database), and DropBox, OneDrive and iCloud:
For specific Mac considerations (iCloud) see article