Synchronization problem
My Logos 9 program developed a problem with not synchronizing for about a month or more. I know that this has been an issue for many over the course of time, but at that time I didn't have the "problem" so I didn't pay too much attention to the solution. I "remember" seeing something in the forums, however, I cannot remember what the actual problem/solution ended up being. I seem to remember that there was either an extraction of a file somewhere or an addition somehow or another, that would remedy this problem.
I was hoping that with the release of L10, this problem would be resolved on my end. That is not the case. I have tried "sync repair" and at first, I thought it had worked...alas, it was not to be.
SO, if anyone remembers that particular "cure" for the synchronization problem, I would really appreciate your help in getting this resolved. Thank you to any and all who have the answer/solution.
Comments
-
-
Hi Bill
I'm afraid there isn't a "one solution fits all" to these types of issues - we would really need to see logs (ideally just after you noticed a sync problem and closed Logos). That might enable us to identity what is the cause of the issue
Details on logs are at https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files
0 -
I was able to find the file without any problem. However, when I tried to use the paperclip to attach the file, it wouldn't complete the task.
0 -
-
Hi JT. Thank you for trying to help with this. The file was/is compressed, however, every attempt at attaching the log files to the paperclip doesn't happen. The size is showing as 12.5M.
0 -
every attempt at attaching the log files to the paperclip doesn't happen. The size is showing as 12.5M.
I believe there is a 5MB limit
What happens if you close Logos, start it again, wait until you get the sync icon indicating there is a problem, close Logos?
I would expect the log file would be a lot smaller.
0 -
Hi Graham, I did what you suggested and the Log file is still 6+MB.
0 -
Hi Graham, I did what you suggested and the Log file is still 6+MB.
Try usng the Amber icon (to the right of the paperclip) - I think there is a higher limit there.
0 -
Amber seems to be only to upload graphics...at least for me.
0 -
12.5mb is a mighty large log file.
Suggestion: aren't log files a sort of text file? Perhaps you could copy sections of the file and paste them individually?
ASUS ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti
"The Unbelievable Work...believe it or not." Little children...Biblical prophecy is not Christianity's friend.
0 -
Amber seems to be only to upload graphics...at least for me.
Interesting - it works on zipped files for me on Win 11
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Hi MJ. I haven't made the switch to Windows 11 yet. I wanted to make sure that L10 is compatible and from many posts, it would seem that should be my next venture. I don't mind the syncing problem so much because I haven't seen any degradation in speed, etc., it is just the unknown "problem" that has me curious.
0 -
Hi Graham, I did what you suggested and the Log file is still 6+MB.
I suggest you delete the Logos.log file before you restart Logos. Close Logos soon after the sync problem occurs and then try to upload the zipped Logos.log file.
The alternative is that you look for ERROR in the log file that relates to a Sync problem and paste about 10 lines before and after into your next post.
Dave
===Windows 11 & Android 13
0 -
Hi Graham, I did what you suggested and the Log file is still 6+MB.
I suggest you delete the Logos.log file before you restart Logos. Close Logos soon after the sync problem occurs and then try to upload the zipped Logos.log file.
The alternative is that you look for ERROR in the log file that relates to a Sync problem and paste about 10 lines before and after into your next post.
Thank you Dave. I did as you suggested. It reduced the size of the file considerably. It would seem I have captured "something" if this isn't the correct file, I'm not sure what else to try.
0 -
https://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/170/7065.Logs.zip
That supplies access to the file. [Y]
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
I have attempted, several time, to attach that file via the paperclip without success. I can open the file, however, since I don't know what to look for, other than "error," nor how to six that error, I will "live with the problem", just like I've done for quite a while. Thank you to everyone who has offered help.
0 -
I am not an expert log reader. The following <may> be relalted to your issue.
2022-10-24 09:56:45.5443 ERROR 22 ApplicationUtility | Exception while syncing client: FavoritesSyncItem ~SyncClientException: Web service error: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
2022-10-24 09:56:45.5483 INFO 22 SyncManager | ClientExceptionHandled: Logos.Sync.Client.SyncClientException: Web service error: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
---> Libronix.Utility.Net.WebServiceException: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
at Libronix.Utility.Json.Web.AutoWebServiceRequest`1.HandleResponseCore(WebServiceResponseHandlerInfo`1 info)
at Libronix.Utility.Net.WebServiceRequestBase`1.DoGetResponse(HttpWebRequest webRequest, Func`2 getWebResponse, IProfiler profiler, IWorkState workState)
at Libronix.Utility.Net.WebServiceRequestBase`1.GetResponse(IWorkState workState)
at Logos.Sync.WebService.JsonSyncClient.SubmitItems(SyncSubmitItemsRequest request, IWorkState state)
at Logos.Sync.WebService.JsonSyncService`1.SubmitItems(IEnumerable`1 items, SyncSubmitItemsSettings settings, IWorkState state)
content: {"message":"An error has occured."}
--- End of inner exception stack trace ---
at Logos.Sync.WebService.JsonSyncService`1.SubmitItems(IEnumerable`1 items, SyncSubmitItemsSettings settings, IWorkState state)
at Logos.Sync.Client.SyncClient.Sync(SyncPurpose purpose, SyncRestrictions restrictions, IWorkState state)
at Logos.Sync.Client.SyncV2Client.Sync(SyncPurpose purpose, SyncRestrictions restrictions, IWorkState workState)
at Logos.Sync.Client.SyncManager.SyncManagerThread()2022-10-24 09:56:51.4792 INFO 16 ResourceMetadataDownloadManager | Requesting community metadata for 44 items.
2022-10-24 09:56:51.8335 INFO 44 ResourceMetadataDownloadManager | 0 community metadata records retrieved from service.
2022-10-24 09:56:51.8357 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:WS_08806D9B0A584E37B2B9B7926525D2A8. (Other)
2022-10-24 09:56:51.8367 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:BOUNDFOREXILE. (Other)
2022-10-24 09:56:51.8374 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:YKSHRSSYRLNDSRL. (Other)
2022-10-24 09:56:51.8380 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:NTNLHBRWSCRPT. (Other)
2022-10-24 09:56:51.8386 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:JRSLMCTYGRTKNG. (Other)
2022-10-24 09:56:51.8393 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:CMPRHNSVTYNGLSH. (Other)
2022-10-24 09:56:51.8399 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:PARABLESSAGES. (Other)
2022-10-24 09:56:51.8406 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT13CH1. (Other)
2022-10-24 09:56:51.8415 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT64JN. (Other)
2022-10-24 09:56:51.8427 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT04NU. (Other)
2022-10-24 09:56:51.8436 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT20PR. (Other)
2022-10-24 09:56:51.8443 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT02EX. (Other)
2022-10-24 09:56:51.8449 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT17ES. (Other)
2022-10-24 09:56:51.8455 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT71PHP. (Other)
2022-10-24 09:56:51.8462 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT01GE. (Other)
2022-10-24 09:56:51.8468 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT27DA. (Other)
2022-10-24 09:56:51.8474 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT05DE. (Other)
2022-10-24 09:56:51.8481 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT15EZR. (Other)
2022-10-24 09:56:51.8487 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT63LU. (Other)
2022-10-24 09:56:51.8494 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT80JAM. (Other)
2022-10-24 09:56:51.8500 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT61MT. (Other)
2022-10-24 09:56:51.8506 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT81PE1. (Other)
2022-10-24 09:56:51.8512 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT38ZEC. (Other)
2022-10-24 09:56:51.8519 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT66RO. (Other)
2022-10-24 09:56:51.8525 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT34NA. (Other)
2022-10-24 09:56:51.8531 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT62MK. (Other)
2022-10-24 09:56:51.8537 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT87REV. (Other)
2022-10-24 09:56:51.8544 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT23IS. (Other)
2022-10-24 09:56:51.8550 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT79HEB. (Other)
2022-10-24 09:56:51.8556 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT09SA1. (Other)
2022-10-24 09:56:51.8563 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT69GA. (Other)
2022-10-24 09:56:51.8569 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:RTBT76TI2. (Other)
2022-10-24 09:56:51.8577 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:TWCTLDTLPRLLBBL. (Other)
2022-10-24 09:56:51.8586 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:WARPEACEVIOLENCE. (Other)
2022-10-24 09:56:51.8592 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:LNDSCPNTRTSTMNT. (Other)
2022-10-24 09:56:51.8599 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for DB:CHURCH-HISTORY-ONTOLOGY. (Other)
2022-10-24 09:56:51.8605 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:CS341ROOT. (Other)
2022-10-24 09:56:51.8612 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:CS341ROOTWKBK. (Other)
2022-10-24 09:56:51.8619 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:CS341ROOTAUDIO. (Other)
2022-10-24 09:56:51.8625 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:WRSHPNGRFRMRS. (Other)
2022-10-24 09:56:51.8631 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:TTCLRKHRLYCHRCH. (Other)
2022-10-24 09:56:51.8638 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:HBRWWRKBKLSS165. (Other)
2022-10-24 09:56:51.8646 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:CMPLTNCSLWS. (Other)
2022-10-24 09:56:51.8654 WARN 44 ResourceMetadataDownloadManager | Failed to download updated metadata for LLS:VNGLCLSMSTMVMNT. (Other)
2022-10-24 09:56:51.8675 INFO 44 ResourceMetadataDownloadManager | Requesting all community metadata with milestone greater than '5515490'.
2022-10-24 09:56:51.9553 INFO 44 ResourceMetadataDownloadManager | 0 community metadata records retrieved from service.
2022-10-24 09:56:51.9566 INFO 44 ResourceMetadataDownloadManager | Finished metadata update.There are also hundreds of this kind of error:
2022-10-24 09:56:35.6067 ERROR 35 SqliteNotesClientRepository | Unable to convert text range Faithlife.NotesApi.Core.TextRangeRequest: {"code":"NotFound","message":"Failed to open text range: {\u0022resourceId\u0022:\u0022LLS:1.0.71\u0022,\u0022resourceVersion\u0022:\u00222019-09-20T19:21:55Z\u0022,\u0022indexedOffset\u0022:1103856,\u0022indexedLength\u0022:9,\u0022indexedVersion\u0022:\u00222010-04-28T19:07:36Z\u0022}"}
0 -
JT and others, this is what is showing in my log files (all 64 pages of them (and that is after a clean restart of my laptop and the program)), and they all look identical... IF I'm reading this correctly, there is a file error in my "Favorites" with some character sets...IF I knew how to find such character sets, I could, at least try to, rectify the problem.
Copy of the Logos Log Files following a failure to proper synchronize
Program Version: 10.0 SR-1 (10.0.0.0234)
Windows Version: 10.0.19044.0
.NET Framework Version: 6.0.7
Time: 2022-10-24 09:56:38 -05:00 (2022-10-24T14:56:38Z)
Installed memory: 30,639 MB
Install path: C:\Users\bshew\AppData\Local\Logos\System\Logos.dll
Free install space: 230,845 MB
Data path: C:\Users\bshew\AppData\Local\Logos\Data\kgqdsynm.cvc
Free disk space: 230,845 MB
Temp path: C:\Users\bshew\AppData\Local\Temp\
Free temp space: 230,845 MB
Program Version: 10.0 SR-1 (10.0.0.0234)
Time: 2022-10-24 09:56:38 -05:00 (2022-10-24T14:56:38Z)
Exception while syncing client: FavoritesSyncItem
Logos.Sync.Client.SyncClientException: Web service error: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
---> Libronix.Utility.Net.WebServiceException: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
at Libronix.Utility.Json.Web.AutoWebServiceRequest`1.HandleResponseCore(WebServiceResponseHandlerInfo`1 info)
at Libronix.Utility.Net.WebServiceRequestBase`1.DoGetResponse(HttpWebRequest webRequest, Func`2 getWebResponse, IProfiler profiler, IWorkState workState)
at Libronix.Utility.Net.WebServiceRequestBase`1.GetResponse(IWorkState workState)
at Logos.Sync.WebService.JsonSyncClient.SubmitItems(SyncSubmitItemsRequest request, IWorkState state)
at Logos.Sync.WebService.JsonSyncService`1.SubmitItems(IEnumerable`1 items, SyncSubmitItemsSettings settings, IWorkState state)
content: {"message":"An error has occured."}
--- End of inner exception stack trace ---
at Logos.Sync.WebService.JsonSyncService`1.SubmitItems(IEnumerable`1 items, SyncSubmitItemsSettings settings, IWorkState state)
at Logos.Sync.Client.SyncClient.Sync(SyncPurpose purpose, SyncRestrictions restrictions, IWorkState state)
at Logos.Sync.Client.SyncV2Client.Sync(SyncPurpose purpose, SyncRestrictions restrictions, IWorkState workState)
at Logos.Sync.Client.SyncManager.SyncManagerThread()
Program Version: 10.0 SR-1 (10.0.0.0234)
Time: 2022-10-24 09:56:41 -05:00 (2022-10-24T14:56:41Z)
Exception while syncing client: FavoritesSyncItem
Logos.Sync.Client.SyncClientException: Web service error: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
---> Libronix.Utility.Net.WebServiceException: Status code not handled. Request: POST https://favoritesapi.logos.com/v1/favorites/sync/up (status InternalServerError, content type 'application/json; charset=utf-8', content length 35)
at Libronix.Utility.Json.Web.AutoWebServiceRequest`1.HandleResponseCore(WebServiceResponseHandlerInfo`1 info)
at Libronix.Utility.Net.WebServiceRequestBase`1.DoGetResponse(HttpWebRequest webRequest, Func`2 getWebResponse, IProfiler profiler, IWorkState workState)
at Libronix.Utility.Net.WebServiceRequestBase`1.GetResponse(IWorkState workState)
at Logos.Sync.WebService.JsonSyncClient.SubmitItems(SyncSubmitItemsRequest request, IWorkState state)
at Logos.Sync.WebService.JsonSyncService`1.SubmitItems(IEnumerable`1 items, SyncSubmitItemsSettings settings, IWorkState state)
content: {"message":"An error has occured."}
0 -
IF I'm reading this correctly, there is a file error in my "Favorites" with some character sets.
There is a problem with syncing some Favorite, usually the last one you added/changed. Try deleting that.
Dave
===Windows 11 & Android 13
0 -
Hi Dave,
Thank you for your reply. I treat my "Favorites" like a file cabinet with nested folders within nested folders, etc., ad infinitum. I would be hard pressed to remember which was the last file that I put into my Favorites and secondly, this syncing problem has been going on for quite a while. I will, however, try to remember which file in my Favorites is the most likely culprit. I would hate to think if I had to completely restart (replace) my Favorites structure.
Again, thank you!
0 -
I would hate to think if I had to completely restart (replace) my Favorites structure.
One way would be to rename your Favorites folder e.g. as oldFavorites. When you restart Logos it will be reconstructed from the Server, minus any Favs that did not sync. The rename provides a safety net.
The folder is C:\Users\bshew\AppData\Local\Logos\Documents\kgqdsynm.cvc\FavoritesManager
Dave
===Windows 11 & Android 13
0 -
Thank you, Dave...all is well, and I can still access all of the files in my "File Cabinet". Thank You!
0
