![]() ![]() ![]() You will need to delete this sync copy by clicking SmartSync | Delete Copy. Instead, it behaves as a parent file, showing nothing in the Synchronization Status menu. If a connection failure or similar disruption occurs during the initial creation process for the synchronized child, the sync copy may be created without the hierarchical information necessary to establish it as a copy. To resolve this issue, we suggest that you contact Technical Support. This conflict is caused by an invalid entry in the Adjusting Entries database which may also display in the Adjusting Entries browse. In the Synchronization Conflicts dialog, an entry may display with the label Unknown object. Unknown object in the Synchronization Conflicts dialog We strongly suggest you contact Technical Support and back up the file before attempting either of these resolutions. There may be a corrupt file in the parent file's _Sync folder.If you cannot open the parent file but your sync copies are still synchronizing correctly, then there are two potential causes for the error. Confirm that permissions for both the share connection where you are accessing the parent and the parent folder have been set correctly to Read/Write. Typically the user creating the sync copy only requires Read access to the parent file however, without Write access, communicate is blocked between log files which results in this error. This issue is typically permissions based. #Smartsynchronize Offline#Occasionally, the file is created, but cannot communicate with the parent and will display a warning that the parent is offline or unavailable. Users will often create sync copies from File | Open by selecting the option to Open as a Synchronized Copy. Working Papers does this automatically when the Data Store is unavailable, but a connection from the field to the main office will reestablish the link to the Data Store and could potentially slow down the synchronization process. It may also be necessary to force Working Papers to use the personal Data Store. On slow connections, it is suggested that clients disable file tracking under Tools | Options | Data Store. If slow performance persists beyond the transfer of a large amount of sync information, Working Papers may be reading and writing a significant amount of information to the Data Store. If subsequent synchronizations between the same two files are also slow, that is an indication of a larger problem. Because of this it is best, if possible, to let a synchronization that is still showing progress reach completion. If several documents have been added to the file while offline, the initial synchronization can run very slowly. This is true for all external documents (Word, Excel, scanned images, etc.) and CaseView documents. If the changes to synchronize are miniscule, the entire file must still synchronize to determine what the change was. Most synchronized data consists of relatively small pieces of information. There are several factors that can affect synchronization performance. File going online and offline repeatedly.Unknown object in the Synchronization Conflicts dialog.Click the applicable heading for SmartSync troubleshooting information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |