Sync error with Logos 9.4

Graham Criddle
Graham Criddle MVP Posts: 32,490
edited November 21 in English Forum

i am consistently getting sync errors with Logos 9.4 with a sequence of log messages starting with:

2021-05-10 15:34:21.1074  WARN 17 SyncItemJsonConverter | Error reading JSON for Logos.Documents.Contracts.Guides.GuideTemplateSyncItem: Could not find member 'version' on object of type 'GuideTemplateSyncItem'. Path 'version', line 1, position 12225.

2021-05-10 15:34:21.1114 ERROR 20 ApplicationUtility | Exception while syncing client: GuideTemplateSyncItem ~InvalidOperationException: Current error context error is different to requested error.
2021-05-10 15:34:21.1398 INFO 20 SyncManager | ClientExceptionHandled: System.InvalidOperationException: Current error context error is different to requested error.

The logos.log file is attached

4064.Logos.log

I am getting the same errors on my MacBook also running 9.4

I am running a beta version of 9.5 (beta 3) on another Windows computer and wonder if something on that platform is generating something that can't be handled on the 9.4 systems.

Any insights appreciated, Graham 

Tagged:

Comments

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    Thanks for reporting this. The issue is a compatibility issue. We're going to fix this in 9.5 so that the new sync data will be compatible with earlier versions.

  • Graham Criddle
    Graham Criddle MVP Posts: 32,490

    Thanks for reporting this. The issue is a compatibility issue. We're going to fix this in 9.5 so that the new sync data will be compatible with earlier versions.

    Thanks Philana

  • Dave Hooton
    Dave Hooton MVP Posts: 35,682

    2021-05-10 15:34:21.1114 ERROR 20 ApplicationUtility | Exception while syncing client: GuideTemplateSyncItem ~InvalidOperationException: Current error context error is different to requested error.

    I 'fixed' that in  9.4 by editing the Passage Guide template (my active guide) and replacing one section (Cross References). But the error came back today!

    Dave
    ===

    Windows 11 & Android 13