How do I add those resources?
I've restarted Logos a couple of times, restared Windows, tried running Logos in different languages... The message keeps popping up...
Past IT Consultant. Past Mission Worker. Entrepreneur. Seminary Student (VIU).Christian Debate Forum --- Auferstanden! Blog
We'll need logs to see why it's not working.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
This has been happening to me too. On different computers. So I don't think this is an isolated issue.
6404.LogosIndexerError.zip
Running on ASUS Windows 10 I7 24 gig of ram, 1 Terabyte drive.
Philippians 2:3 Do nothing from selfish ambition or conceit, but in humility count others more significant than yourselves.
ditto
4137.Logos Log Files.zip
I went through the log file, and suspect the temporary NT211 course to be the culprit.
I'll try a full re-index once the other monthly temporary resources have expired.
I am having the same issue.
Me too
I am having the same problem also.
Well, add me to this list.
I had to endure four (4) consecutive indexes the other day when "new resources" needed to be added. I don't understand why it can't add them all and index once. It's a serial time killer.
My thanks to the various MVPs. Without them Logos would have died early. They were the only real help available.
Faithlife Corp. owes the MVPs free resources for life.
Doc B: I had to endure four (4) consecutive indexes the other day when "new resources" needed to be added. I don't understand why it can't add them all and index once. It's a serial time killer.
And you are not alone!
The issue disappeared once new resources were downloaded. May have been the download, or the automatic index process that cleared it. Not sure.
Hmmm. Same issue with me.
I did several things, so I am not sure which one cleared the indicator:
I suspected the temporary license to the class, so the above made sense to me.
Maybe it will help some of you.
John Fidel: I did several things, so I am not sure which one cleared the indicator: I cleared web cache. I removed a layout that had the Temporary Mobile Ed class in it. I ran update resources. I suspected the temporary license to the class, so the above made sense to me. Maybe it will help some of you.
Other than waiting for another resource to download and index, "Update Resources" seems to work.
Same here. I called FL and it is a known bug.
Mine is working now. However, I had to do a quick disk clean (McAfee) and restarted Logos (for the 5th) time and now it's ok. This is the second time this has happened and seems to occur when there is a large resource update.
see this thread
https://community.logos.com/forums/t/126703.aspx
mm.
Jan Krohn: 4137.Logos Log Files.zip I went through the log file, and suspect the temporary NT211 course to be the culprit. I'll try a full re-index once the other monthly temporary resources have expired.
Jan (and others) see my post here:
https://community.logos.com/forums/t/127633.aspx
I list all the steps I went through which cleared this up.
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
Well, my machines have cleared up now.
We discovered a problem that caused expired licenses to remain active on the server for a few hours after they expired. This led to a situation where the desktop application removed the resources from the library upon expiration, then the server indicated that they should be downloaded again. After downloading, the application would attempt to install them, but fail due to the expired license.
The server should be updated today with a fix that will correctly handle expiring licenses in the future. We are also adding some additional logging to the application to give us more information in case something similar happens again.
If you are continuing to have problems with this, and have not run the "update resources" command, please do so. If the problem persists after running that command and restarting the application, please post back here and attach your log files.
If this problem shows up in the future, please don't hesitate to post on the forums and attach your log files.
Andrew Batishko | Faithlife software developer