Please Help! Keep getting error on trying to sync Logos.
I keep getting an error whenever I click the sync button saying, an error has occurred during synchronization. please try again.
So I can't get my sermon on my ipad.
Comments
-
Hi Joey
Sorry to hear you are having problems.
Please enable diagnostic logging as per https://support.logos.com/hc/en-us/articles/360027869132
And then upload a copy of your logs in a reply to this post (use the paperclip icon in the forum editor)
That should hopefully give us an indication of what element is causing the sync issue.
To get a "clean" set of logs please stop Logos, start it again, attempt the sync operation, close Logos after getting the error message.
Then submit logs before starting Logos again
Graham
0 -
-
The issue is reported as:
Exception while syncing client: SermonWriter
System.InvalidCastException: Unable to cast object of type 'System.DBNull' to type 'System.String'.
at System.Data.SQLite.SQLiteDataReader.GetString(Int32 ordinal)
at Libronix.Utility.Data.ExceptionHandlingDbDataReader.GetString(Int32 i)
at Libronix.DigitalLibrary.Documents.Sermon.SermonManager.OurSyncClientRepository.SyncItemFactory.CreateDocumentHeadingsAndSetSyncStateToSubmitting(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 shows that the problem is associated with syncing a Sermon - which is consistent with what you were seeing.
But it doesn't idenfity the Sermon document that is causing the problem.
I think at this point I would contact Customer Services - contact details at https://www.logos.com/contact-support - and see if they can conduct further troubleshooting.
It might end up wiith having to delete the sermon document you have been working on (or going back to an earlier version). As a precaution, I would export it to Word so you have a backup copy. You can do this using the Publish button and selecting the Print / Export option
0 -
This looks like some bad data got in the local db. Joey, would you be willing to share your local Sermon.db with us? We want to get this sorted out for you and prevent any future documents from getting in this state!
Instructions on attaching Sermon.db:
- Press Window key + R.
- Type %localappdata% and press Go.
- Navigate to Logos\Documents\randomfolder\Documents\Sermon
- Right-click Sermon.db
- Click Properties > Send To > Compressed Folder
Then attach the compressed folder to a reply message, just like you did with the logs.0 -
-
If I uninstall Logos and then reinstall, would that most likely fix my problem, and I would only lose documents from the time the error started until now?
0 -
If I uninstall Logos and then reinstall, would that most likely fix my problem, and I would only lose documents from the time the error started until now?
Hi Joey - installing logos would be pointless all you need to do is reinstall and that will overwrite the 'programs' files. As you say data files, indexes and libraries will be unaffected.
Speaking from ignorance though if your problem is with one of your sermon files then changing the program will do nothing to help. The 'problem file' will still be the 'problem file.
Hang on until somebody can have a look at your sermon.
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
If I uninstall Logos and then reinstall, would that most likely fix my problem, and I would only lose documents from the time the error started until now?
My guess is that if you just deleted the Sermon.DB Dustin mentioned above you would get back to that point.
But if you can, I'd hold on until hearing back from Dustin.
0 -
I will wait, but I already deleted all sermons that I created since just before I started seeing the error and notes but I'm still getting the error.
But I did not delete the sermon.db yet.
0 -
I appreciate your patience here, Joey. It was very helpful to look at your sermon data. For reference, it appears one of your templates ("Joey's Template") somehow got a `null` title, which should be impossible, and we are tracking down how that possibly happened.
In the meantime, deleting `Sermon.db` is probably the cleanest way to recreate your data. Close Logos, delete that same sermon.db file you sent us, when you reopen Logos it will sync down all your saved sermons.
0 -
I deleted the sermon.db yesterday and I still got the same error, but then this morning I deleted all the files in the sermon folder including the backups, (I did back them up just in case), and then relaunched Logos and that seemed to work. It is syncing again.
Thanks to everyone for your help.
On a further note, each year I create many sermon documents with a sermon template I had called Joey's Template, so I can just go to Sermon Manager and click on my next sermon to work on. I guess this year one of the files must have corrupted.
I am going to try again with a new sermon template tonight and see what happens.
0 -
I guess I spoke too soon. I got up this morning and the same thing is happening, an error in syncing. I had only created one sermon document. I was able to go in and delete sermon.db, sermon.db-shm, and sermon.db-wal and now it is syncing again, but something must still be wrong I shouldn't have to constantly do this to keep Logos syncing.
I will leave it again for now, so hopefully they can find a solution, if not I will try a complete uninstall and reinstall and see if that works.
0 -
That is terrible, Joey, I am so sorry this isn't working as it should! While I look into this, was this new sermon created from a template again, from Sermon Manager or from the Documents menu?
0
