Logos 7.15 SR-1 Mac OS 10.13.5
Receiving repeated—continual—synchronization failures due to an exception with CustomDictionaries.
5488.LogosLogs.jackcav.20180622-075925.zip
I've had my share of this error; which FL should investigate.
Delete the folder /Users/jackcav/Library/Application Support/Logos4/Data/fwu3dehb.5cn/UserDictionaryManager/ and restart Logos for a quick fix.
I've had my share of this error; which FL should investigate. Delete the folder /Users/jackcav/Library/Application Support/Logos4/Data/fwu3dehb.5cn/UserDictionaryManager/ and restart Logos for a quick fix.
Thanks, Dave. I had previously deleted the contents of that folder. After your post, I deleted the folder. Unfortunately, this did not clear the problem. In addition I now have a series of Invalid ResourceId warnings.
[quote]
2018-06-22 21:30:37.1804 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.114), Version (2004-06-14T20:33:56Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1804 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.112), Version (2015-01-08T22:29:00Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1804 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.117), Version (2015-01-08T22:29:00Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1804 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.124), Version (2015-01-08T22:29:00Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.113), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.115), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.118), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.119), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.121), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.122), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.134), Version (2015-01-08T22:31:49Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.111), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.116), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.120), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.123), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.125), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.132), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.135), Version (2015-01-08T22:37:16Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.138), Version (2015-06-18T00:05:39Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.140), Version (2015-06-18T00:05:39Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.142), Version (2015-06-18T00:05:39Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId ({8062ECD0-5B4C-484D-86BF-E460B1EEA999}), Version (2015-06-23T23:22:04Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1810 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId ({BDD1F99E-9360-452E-822E-8CAFB760E7A0}), Version (2015-06-23T23:22:11Z), or ResourceType (); rejecting metadata record. 2018-06-22 21:30:37.1905 | WARN | 22 | MetadataServiceUtility | Invalid Titles (Count=1), Languages (Count=1), or MilestoneIndexes (Count=1); rejecting metadata record for LLS:LEWIS. 2018-06-22 21:30:37.1905 | WARN | 22 | MetadataServiceUtility | Invalid ResourceId (LLS:40.170.145), Version (2017-05-09T23:46:37Z), or ResourceType (); rejecting metadata record.
Should I rebuild Index?
UPDATE: Remembered that earlier today, I hid a number of audio resources that I have never used. That should answer my question about rebuilding index. It is near my bedtime here in the southeastern US, so rebuild index is happily running.
After running Rebuild Index, I am still getting the same synch failure and all those Invalid ResourceId warnings. This installation is a complete download and install a few days ago.
Does anyone have any idea what these resources could be?
Would be nice to hear from FL concerning these errors, as I am not the only one reporting them. DeletingUserDictionaryManager does not correct the problem.
I've filed a case for this error.
Thank You
This has happened again!
Mine has had this synch error continually since I first reported it. I have not had a single synch success.
Is anything being done about this? I still have continual synch failures. Deleting Custom Libraries does not alleviate the problem.
Hi Jack,
I do not have a resolution for you at this moment, but I can confirm that despite the error message sync should still be occurring for changes to your documents, and when you create new documents. I didn't want you to think that nothing was syncing since you saw that message.
