Error during synch won't go away
This pretty much stays there on one of my computers, 24-7.
There are no error logs being generated.
???
Eating a steady diet of government cheese, and living in a van down by the river.
Comments
-
I assume you have checked the internet connection for that machine and have insured Logos is not started in offline mode? If so then the only thing I can think of is that something (perhaps in your firewall settings) is blocking logos.
0 -
Fredc said:
I assume you have checked the internet connection for that machine and have insured Logos is not started in offline mode? If so then the only thing I can think of is that something (perhaps in your firewall settings) is blocking logos.
Yes, it is connected and working fine.
No, the firewall isn't blocking Logos. None of these problems started until the last release.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Are running the most recent stable version or the most recent RC (released today)? I cannot duplicate this problem and without the Logos log it is difficult to see what is going on under the hood. Can you upload the logos log?
0 -
Fredc said:
Are running the most recent stable version or the most recent RC (released today)? I cannot duplicate this problem and without the Logos log it is difficult to see what is going on under the hood. Can you upload the logos log?
It updated again this afternoon, so I'm pretty sure I'm on the latest version, and I've never been on the beta(gainstit) channel.
The cef.log is the only item in my Logos log folder. Nothing else there.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
The cef.log is the only item in my Logos log folder. Nothing else there.
You have to enable logging to get the Logos.log file.
0 -
You have to enable logging to get the Logos.log file.
Done, and attached.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
BTW, every single time I post logs, I get this screen as a response-
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
One of your Clippings documents is failing to sync; however, the logs don't really say why.
It will probably be a document that's just on that specific computer and no others; if it's not important, you could just delete it. Otherwise, we could try to investigate further to find what's preventing it syncing.
0 -
One of your Clippings documents is failing to sync; however, the logs don't really say why.
It will probably be a document that's just on that specific computer and no others; if it's not important, you could just delete it. Otherwise, we could try to investigate further to find what's preventing it syncing.
Did it say which one?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
Did it say which one?
No, it didn't, but it's likely to be a recently-created document that's only on the affected computer.
0 -
Doc B said:
Did it say which one?
No, it didn't, but it's likely to be a recently-created document that's only on the affected computer.
Document count is over a hundred; this'll be fun. I'll take a screenshot on my home computer and see if I can figure out which one. Will simply deleting it on the laptop fix the sync issue? Or do I need to rebuild some index, etc.?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
Document count is over a hundred; this'll be fun. I'll take a screenshot on my home computer and see if I can figure out which one.
Bradley suggested it was a recent Clippings Document
Suggest opening the Documents menu, select Clippings on the right and sort by date. It could be one of the most recent ones.
0 -
Graham Criddle said:
Bradley suggested it was a recent Clippings Document
Using that as a starting point, I was surprised to find the same number of Clippings Docs (and all other docs, for that matter) resident on all my Logos installations.
I then sorted, as Graham suggested, the Clippings by date. I was again surprised to find one document dated today...I haven't opened or touched any documents, including clippings docs, in a couple days. (Here's what I saw-)
The Creation Studies doc isn't mine...I made a copy of this doc on the FL groups page last Friday. Since I hadn't touched it yet, and it was showing updated today, I happily thought I'd found the culprit. I print/exported it (because I want the content) and deleted it.
No joy in Mudville. The sync error is still happening. I'm neither Casey nor mighty, but I have indeed struck out.
I have no intention of deleting all my docs; recoverable or not. So how do I get a lead on the problem document?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
So how do I get a lead on the problem document?
I think it has the ID 5cf6846a75724794967729befebae11c.
If you upload your Clippings DB (C:\Users\borenjb\AppData\Local\Logos5\Documents\zqvrwgjg.xju\Documents\Clippings\Clippings.db) we should be able to identify the file from that. (If you don't want to upload that to the forums, you can email it to logosbugs@logos.com.)
0 -
If you upload your Clippings DB
Tell me how. Got this when I attached the .db file.
[Edit: In the mean time, I'll email it.]
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
If you upload your Clippings DB
Tell me how. Got this when I attached the .db file.
[Edit: In the mean time, I'll email it.]
You could simply zip it before uploading (makes it smaller, too).
Have joy in the Lord!
0 -
Doc B said:
So how do I get a lead on the problem document?
I think it has the ID 5cf6846a75724794967729befebae11c.
This corresponds to the "Trinity" clippings document. I'm still not sure why it's failing to upload though.
0 -
This corresponds to the "Trinity" clippings document. I'm still not sure why it's failing to upload though.
Deleted the Trinity doc from the computer showing the error.
Even after a couple restarts, the error is still showing.
But this seems bigger than a simple single-doc issue. Here are screenshots of my Clippings from my Desktop and from my Laptop. Same network, same firewall, etc. They don't even look like the same lists. Unless I completely misunderstand the system, they should look very much alike.
(Note that the Trinity doc is still present on the non-error computer...showing it hasn't been updated since Jan. '13.)
Desktop-
Laptop- (This is the computer on which I am getting the sync error.)
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
bump
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Doc B said:
But this seems bigger than a simple single-doc issue. Here are screenshots of my Clippings from my Desktop and from my Laptop. Same network, same firewall, etc. They don't even look like the same lists. Unless I completely misunderstand the system, they should look very much alike.
The Last Modified date doesn't sync, so sorting by modified date will order the lists differently on different computers.
If you sort by title, the lists should look the same.
We're still investigating this issue. To clear the sync error, you could delete Clippings.db from the affected computer. Otherwise, clippings sync may be affected on just that computer, but all other documents and settings will be syncing correctly.
0 -
To clear the sync error, you could delete Clippings.db from the affected computer.
This cleared the error indicator. The funny thing was, the Trinity doc which I deleted a few day ago is back with the rebuild of the Clippings.db file.
If something goes wrong again, I'll start another thread.
Eating a steady diet of government cheese, and living in a van down by the river.
0
