nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Logos 4 won't sync

Matthew Tolosa

I recently added my Logos 4 to my new laptop and it is not syncing across my platforms. For example, I did some reading in my Vyrso App and it syncs with my older laptop and my CPU, but for some reason it will not sync on my new laptop. Any ideas on how to fix this.

Find more posts tagged with

Comments

Graham Criddle

Hi Matthew - and welcome to the forums.

When you say it does not sync, what exactly do you mean? Are you referring to reading positions in a resource? If so, was the resource open in your new laptop at the time?

And is there any reason you haven't done the free upgrade to the core Logos 6 engine? https://www.logos.com/product/46767/logos-6-core-engine

Graham

Dave Hooton

I recently added my Logos 4 to my new laptop and it is not syncing across my platforms

You can't rely on Sync with Logos 4 as there have been changes since it stopped being maintained and there are no fixes for an unsupported version. Logos 5 will soon come under this regime so the best long term fix is Logos 6.

Andrew Malone

https://community.logos.com/discussion/comment/758091#Comment_758091

A different kind of sync problem. (Yes, I'd love to utilise my existing licence for Logos 6, but my WinXP machines make that unworkable at the moment.)

I've previously had no problems with Logos 4 and syncing. After correcting some system glitches a fortnight ago, however, L4 doesn't seem to talk with the sync server. When I start up, the 'synchronizing' splash screen pops up; the wedged circle rotates endlessly; I eventually grow impatient (I once gave it a full 30 minutes) and opt for 'Start Now'. Exactly the same thing happens on shutdown. I think this has also been happening mid-session; my machine would freeze up, probably about with the frequency of automatic attempts at syncing, until I turned off the Use Internet option.

(Perhaps relevant or perhaps another problem: some of my notes have started to duplicate. One verse now has nearly 2,000 of the same annotation...)

I've never delved into error logs, but am happy to be pointed towards a wiki or FAQ for some kind of diagnostic hints. Thanks!

Graham Criddle

https://community.logos.com/discussion/comment/764615#Comment_764615

Hi Andrew

(Yes, I'd love to utilise my existing licence for Logos 6, but my WinXP machines make that unworkable at the moment.)

I understand but there may be limits to what we can do to help. Bradley's comments on sync support at https://community.logos.com/forums/p/113509/757419.aspx#757419 are relevant.

I've never delved into error logs, but am happy to be pointed towards a wiki or FAQ for some kind of diagnostic hints. Thanks!

https://wiki.logos.com/Diagnostic_Logging shows how to enable and create logs. Please enable them, start Logos and leave it until the "sync problem" has happened, then close it down and upload logs before starting Logos again

Mark Barnes

https://community.logos.com/discussion/comment/764618#Comment_764618

I understand but there may be limits to what we can do to help. Bradley's comments on sync support at https://community.logos.com/forums/p/113509/757419.aspx#757419 are relevant.

As far as I know sync should still work on Logos 4 and Logos 5. As I understand it, Bradley was simply saying that they aren't guaranteeing it will always work on older versions, not that it has already stopped working.

Andrew Malone

https://community.logos.com/discussion/comment/764619#Comment_764619

As far as I know sync should still work on Logos 4 and Logos 5.

Thanks, gents. These are the sorts of answers and links I was hoping to solicit.

In the last couple of hours, a message from Customer Support included the following line:

The service through which we host our files updated their systems, rendering synchronization with XP impossible.

I don't know whether or not this claim is more authoritative and up-to-date than Bradley's. If correct, it does suggest that "unsupported" has taken one more step towards "inoperable". (While I'm disappointed, I don't begrudge this. I'm just recording it here for others who stumble across the thread.)

Dave Hooton

https://community.logos.com/discussion/comment/764820#Comment_764820

I don't know whether or not this claim is more authoritative and up-to-date than Bradley's. If correct, it does suggest that "unsupported" has taken one more step towards "inoperable".

It would be up-to-date, supporting Bradley's comment. You could mitigate the impact by working offline most of the time and ensuring your Documents folder (...\Logos4\Documents) is backed up.

Andrew Malone

https://community.logos.com/discussion/comment/764825#Comment_764825

Thanks, Dave. That's exactly as far as I've got in my own thinking. :-)

Andrew Malone

https://community.logos.com/discussion/comment/764850#Comment_764850

For anyone tracking this thread and issue: Although I'm unsure when the difference kicked in, I find that I'm no longer thrashing when it comes to connecting L4 with the sync server. I'm yet to test whether new notes are actually being communicated to and from the server, but I can once again work online without incessant stalling while the connection fails.