Sync errors this morning?
I am getting the yellow triangle now this morning. I had exited Logos properly, and the back circle was dimmed indicated it had completely sync'd and was current.
I had exited because I needed to reboot my system (Windows 7 x64). When it restarted, I noticed the Synchronizing dialog box was upa long time, so I clicked Start Now. Once Logos was up, the black circle spins a long time, then gets a yellow triangle. I checked the log file, the only error in it is this one, which seems to indicate a server problem on Logos' side:
2013-05-26 06:07:46.7463 20 Warn SyncManager Error occurred during synchronization download - Libronix.DigitalLibrary.Synchronization.SyncClientException: InternalServerError ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
at Libronix.DigitalLibrary.Synchronization.SyncClient.SubmitRequest(SyndicationFeed syndicationFeed, Nullable`1 dtSince, Nullable`1 dtSinceCollaborating, IEnumerable`1 headers, Boolean bExcludeDeleted)
at Libronix.DigitalLibrary.Synchronization.SyncClient.GetItems(DateTime dtSince, DateTime dtSinceCollaborating, IEnumerable`1 seqIgnoreSyncDates, Boolean bExcludeDeleted)
--- End of inner exception stack trace ---
at Libronix.DigitalLibrary.Synchronization.SyncClient.GetItems(DateTime dtSince, DateTime dtSinceCollaborating, IEnumerable`1 seqIgnoreSyncDates, Boolean bExcludeDeleted)
at Libronix.DigitalLibrary.Synchronization.SyncManager.DownloadItems(ISyncClient syncClient, ISyncManagerPreferences preferences, IEnumerable`1 seqIgnoreSyncDates, IDictionary`2 dictItemSources)
Comments
-
Has this been resolved? If not upload the full logos.log via the paper clip icon.
Dave
===Windows 11 & Android 13
0 -
Yes, later in the morning it started working. Hopefully that error can be traced on the server side for the future! Thanks Dave.
0 -
Don Awalt said:
Hopefully that error can be traced on the server side for the future!
Any time a "(500) Internal Server Error" occurs, it's automatically logged on the server and the appropriate team is alerted. I haven't looked into this specific case, but it's highly likely that a fix was deployed after we were notified of the error.
0 -
Thank you Bradley!
0
