Logos not syncing properly

Oral Anderson
Oral Anderson Member Posts: 3 ✭✭
edited February 17 in English Forum

Logos quit syncing this morning without any user change on my MacBook Air. (MBA 2024, Sequoia 15.1) Only some of the adjustments to my sermon this morning was synced. It will not export to Proclaim either. It gave the message "An error has occurred during synchronization, click to try again."

I tested on my older iMac to see if it was a server problem. The iMac synced everything just fine to my mobile devices and Logos online. I tested both machines on the same network and also on separate networks. I checked for any proxy filter or firewall filters.

However, if I open something on either machine, it will correspond in the history of both machines…which means that some aspects are syncing but others aren't (I have only noticed this with my sermons).

Any solutions?

Tagged:

Comments

  • Graham Criddle
    Graham Criddle MVP Posts: 33,001

    Hi @Oral Anderson - and welcome to the forums

    To help diagnose this we would need to see logs from the machine that is failing to synchronise.

    Please enable diagnostic logging and post logs in a reply to this thread.

    Details for doing this are at https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files#tab-macos-logging

    Graham

  • Oral Anderson
    Oral Anderson Member Posts: 3 ✭✭

    Thank you for your response and help.

    The Utility reports Logos version number - 39.1.0.006. The version reported by the actual Logos software is 39.1.6.

    LogosLogs.oralanderson.20250216-172821.zip
  • Graham Criddle
    Graham Criddle MVP Posts: 33,001

    Thanks Oral

    The Logos.log file contains:

    2025-02-16 17:25:58.5082 ERROR 25 ApplicationUtility | Exception while syncing client: SermonWriter ~ArgumentException: passage must be set if and only if the kind is 'passage' (Parameter 'passage')
    2025-02-16 17:25:58.5098 INFO 25 SyncManager | ClientExceptionHandled: System.ArgumentException: passage must be set if and only if the kind is 'passage' (Parameter 'passage')
    at Logos.SermonWriterApi.BlockSyncItem..ctor(SyncId syncId, Boolean isDeleted, Nullable1 version, Nullable1 epoch, DateTimeOffset modifiedDate, String kind, Boolean question, Boolean handout, Boolean needsSlides, Int32 indent, String content, String style, Passage passage, Clipping clipping, EditablePassage editablePassage, EditableClipping editableClipping, Int64 rank, IEnumerable1 slideGroups, Int32 uiVersion, String extraPropertiesJson)
    at Libronix.DigitalLibrary.Documents.Sermon.SermonManager.OurSyncClientRepository.SyncItemFactory.CreateBlocksAndSetSyncStateToSubmitting(IConnector conn, Boolean includeErrorItems)
    at Libronix.DigitalLibrary.Documents.Sermon.SermonManager.OurSyncClientRepository.SyncItemFactory.CreateSyncItemsAndSetSyncStateToSubmitting(Boolean includeErrorItems)
    at Libronix.DigitalLibrary.Documents.Sermon.SermonManager.OurSyncClientRepository.GatherItemsToSubmitCore(Boolean includeErrorItems)
    at Logos.Sync.V3.SyncClientRepository.GatherItemsToSubmit(Boolean includeErrorItems)
    at Logos.SermonWriterApi.Client.Sync.SermonWriterSyncClient.GetBatchedItemsToSubmit(SyncClientRepository repository, Boolean includeErrorItems, Nullable    1 maxItems)
    at Logos.Sync.V3.SyncV3Client.SyncUpAsync(SyncClientRepository repository, Boolean includeErrorItems, IWorkState workState)
    at Logos.Sync.V3.SyncV3Client.SyncAsync(SyncPurpose purpose, SyncRestrictions restrictions, IWorkState workState)
    at Logos.Sync.Client.SyncManager.SyncManagerThread()

    This indicates that the problem is related to trying to sync a sermon document - but I haven't seen the particular error message before.

    My guess is that there is something in the changes you made to the sermon document this morning that has resulted in this condition - but I can't get enough from the log file to determine what.

    I can suggest three options:

    1. See if someone from Logos sees this thread and provides any more detailed advice
    2. Contact customer services and ask them to look at it
    3. Go back to an earlier version of the sermon (after making notes of the changes you made) and see if that resolves the problem.

    To go back to an earlier version, use the Version History button in the sermon builder

    image.png
  • Oral Anderson
    Oral Anderson Member Posts: 3 ✭✭

    Thank you for your help.

    I tried going back to a version of the sermon from before today, but I get an error. I deleted the sermon - did not fix the problem. I deleted and reinstalled the software, still no fix.

    I will follow the other options you suggested.

Categories