I see Mac users have had some problems downloading. I'm experiencing similar issues on both of my machines: Win 8.1 Pro on both. Start installation of Logos 5, get to 15% of downloading resources and stalls. What to do?
I am a mac user but I can offer a couple of ideas.... If there is corrupt file somewhere I can see how it could cause issues. Have you tried deleting everything to install it fresh? Also I am not 100% certain it is a mac issue but I am curious if it is a possible issue with slower connections, do you know what speed your connection is / latency?
-Dan
I've deleted everything and restarted the installation on the first computer. Actually I did that twice on that computer. That's what led me to try installing on the second computer, which is experiencing the same issue.
High speed internet here. I used a wired connection on the first computer, wifi on the second.
If you can upload indexing logs, we might be able to work out what's going on. You'll need to turn on diagnostic logging, then start Logos, and wait for the stall. Then upload your logs here.
Here are the files from a week or so ago when I was trying to self -fix it.
0724.cef.zip
The indexing log you uploaded shows that there are 1,009 updates (about 6.5Gb), and that it was cancelled manually. But the log is from nearly two weeks ago. To diagnose the problem we'll need a log that actually records the stall.
6320.Logos.log
This is the only file that changed when I opened and tried to download resources.
It doesn't help. From the link in Mark's post ensure that logging is permanently enabled. In Tools >> Program Settings set Automatically Download Updates to NO (which will stop downloads from interrupting indexing).
Start Logos and after the download has stalled for a few minutes, compress the Log Files folder and upload it before doing anything else!
54006.Logos Log Files.zip
Auto DL was already turned off. Here are the logs after opening, starting the download, waiting, and them zipping the logs before closing Logos.
The logs show:
There is no indication of a stall as the log finishes with the commencement of the download at 0%
If the download is still under way, then upload more logs if it has stalled.
But I'm curious that you allowed the download when indexing was under way (as per Logos' notification icon). The idea of Auto DL = NO is to wait until indexing is complete and then start the download.
48185.Logos Log Files.zip -- Updated Logs. I've let Logos stay open the whole time since my last post.
I thought I paused the indexing before starting the DL, Sorry if I forgot, hopefully these logs can still help.
The download isn't going anywhere. Try the following
As an FYI, I've did all of that before starting this thread.
I thought I paused the indexing before starting the DL,
I didn't say to pause the indexing, and now you say that you already did what I asked, including the removal of the database file!?
If those steps haven't helped then you should contact Technical Support.
If you were more careful in reading my post you would understand that what I said was that I did all of your steps before I even made this thread. A simple Google search provided that advice. Please refrain from further posting in the thread Dave, as I'd like to see if someone has any helpful, less condescending advice before calling tech support.
Does anyone else have any ideas? To recap:1. I have done the steps Dave has mentioned. It didn't help and that is why I made this thread.2. I have uploaded my logs here. These are the most updated log files as of this posting. Logos has been open for a number of hours now.
Thanks.
2477.Logos Log Files.zip
Roy,
Your indexing log suddenly finishes, just after the download begins. That suggests that the indexer crashed at that point, in such a way that the crash couldn't be logged.
Could you check your windows event log for any errors, warnings or critical issues that occurred around about the the index log finishes (2014-11-21 15:14:25)?
Logos downloading problems are often BITS related. That's unlikely, given that you're experiencing the problem on two PCs, but it's still worth checking, I think. There's a whole bunch of advice on this and other related issues at https://www.logos.com/firewall, which is worth working your way through, if you've not done so already. Perhaps you could confirm that.
Mark
Let me give you a piece of advice: being rude to Dave isn't going to make you very popular around here! I've spent quite a bit of time on these forums in the last 4 years, as you can see from my post count, and this is the first time I can remember that anyone has had the bad judgement of doing such a thing. There are very few users here as helpful as he is, even fewer as humble and self-effacing, and only one that I can think of who can even begin to compete with his knowledge about Logos (and he doesn't have anywhere near the same amount of free time as Dave, and is most likely spending the day writing his sermon (as are most forum regulars)). Every one of us here is hugely in Dave's debt, and would take his advice any day. And be grateful for it!
You can, of course, wait and hope to be noticed by Bradley. He's the Director of Software Development, so he does, admittedly, know more than Dave, but he's unlikely to be at work on a Saturday. He does occasionally post even on weekends, but not frequently.
So if you won't work with Dave, I suggest you call Tech Support. Though they will most likely try the same things as Dave. And they will almost certainly be a lot less competent than he is.
EDIT: I guess I was wrong about Mark writing his sermon.[:)] Good for you.
I guess I was wrong about Mark writing his sermon. Good for you.
I'm preaching in another church tomorrow, so not quite so much preparation is needed [:)].
If you think what I said was rude, you're gonna have to toughen up a bit. And if Dave is so good, then it appears that he can still learn by actually reading posts before getting snippy.
I paused indexing there, but I will look in my event logs to be sure.
We had a disconnect or misunderstanding that started with your comment "I thought I paused the indexing" followed by my emphasis on "wait until the indexing completes before starting the download" followed by your "As an FYI, I've did all of that before starting this thread." which left me wondering exactly what you meant by "did all of that" and didn't indicate what you were doing or going to do.
So my response was an attempt to clarify the situation. I apologise if it came across as "snippy".
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
