No search results
Comments
-
Logos Indexer is not running in Task Manager, but the home page still says first time indexing is underway. It stopped on it's own and did not leave a crash log again. Melissa did anyone at logos find anything in the logs? Thanks.
0 -
Michael Lyman said:
The Indexer has twice stopped after indexing about 1704 resources out of 1722 in the main Index, but it did not get to LogosLXX this time. You have checked free space on the hard drive? When it stopped were you able to observe anything else eg. did the computer shutdown?
Dave
===Windows 11 & Android 13
0 -
127GB of free space and the computer has not shutdown during any of the episodes. A couple of times the error message stating the the indexer has stopped working has popped up, but that has happened during successful indexing in the past. Thanks again, Dave. I appreciate it.
0 -
Indexer stopped again today, no logs again.
0 -
Still no index, waiting for a solution from Logos.
0 -
Does anyone else have any ideas? Thank you.
0 -
I have had the same problem. I called tech support and to my surp rise the techie to whom I spoke had never heard of this issue! My solution was to reformat my hard disk, reinstall windows7 pro, reinstall Logos and it finally worked. Not very elegant!
0 -
Why did they say that all of that was needed? It's not an answer I'm satisfied with. I've never had as finicky a program as Logos 4. I had this problem with an early beta and some different indexing problems early on but nothing again until now. If that is the solution those of us who have problems can will have to do that on a regular basis since indexing is a regular process with the program. Melissa, what did the developers come up with?
0 -
Logos did not tell me to do that. I just decided that I had wasted enough time and I needed that search index.
0 -
Used Crap Cleaner to clean all files, turned AVG off, did a rebuild index command. I can search Bibles again now.
My entire library search is faster... but still no results...
No new log files.... now on day 10 of no index...
0 -
I tried the same thing and got the same results. A friend of mine has Logos 4 and he cannot search his library either.
That is why I finally gave up and reformatted and reinstalled. It is a terrible solution and Logos should fix thisbut I needed to get on with my studies and writing. I have had many problems with "logos 4 not responding." It seems that normal computers (win 7, 3 GB, 2.6 MZ ) are not enough to really manage this software. At least that is my experience.
0 -
Joseph, Logos 4 has been working for quite a while for me until this last update. My computer has the specs, I'm just waiting for tech support to get back with me. I'll continue to use Logos 3 until they do.
HP
G60-445DX Notebook PCAMD
Turion Dual-Core RM-75 2.20 GHzRAM:
4.0 GBWindows
7 Professional 64 bit Operating SystemNVIDIA
GeForce 8200M G0 -
Any ideas yet Melissa? Thanks.
0 -
Michael Lyman said:
No new log files.... now on day 10 of no index...
No log files at all? You may need to try to turn logging back on. (Rerun the EnableLogging.js script).
MacBook Pro (2019), ThinkPad E540
0 -
Nothing from development yet, but I do see in your account notes that a technician helped you with indexing issues back in November by having you delete the DownloadManager.db file found in C:\Users\Michael Lyman\AppData\Local\Logos4\Data\yoazfngm.dru\DownloadManager.
0 -
Since then I upgraded to Win 7 Pro 64 bit and redownloaded Logos. I just deleted that file and the library index and restarted Logos 4 after enabling logging again so we'll see what happens. Thanks for checking.
0 -
Indexer quit on it's own again. No index again... Logging has been turned on since 5-23-2010.
0 -
Michael Lyman said:
Indexer quit on it's own again. No index again... Logging has been turned on since 5-23-2010.
Every resource was indexed but 1164 of the 1722 had an error like this:-
Error LogosResourceIndexer Exception indexing 'C:\Users\Michael Lyman\AppData\Local\Logos4\Data\yoazfngm.dru\ResourceManager\Resources\CALTGCGAAR.logos4': External component has thrown an exception.
Should be pretty simple for Logos to figure!
Dave
===Windows 11 & Android 13
0 -
Since my last successful index. I have installed Adobe CS4 and upgraded to Microsoft Expression Web 4 and Office 2010. I don't think I have any other new software. I don't think any of these would cause a problem but I thought I should mention it. I am current on all Microsoft updates as well.
0 -
Michael Lyman said:
Since my last successful index. I have installed Adobe CS4 and upgraded to Microsoft Expression Web 4 and Office 2010. I don't think I have any other new software. I don't think any of these would cause a problem but I thought I should mention it. I am current on all Microsoft updates as well.
I've submitted your new Logos4Indexer.log to development.
0 -
Did you all find anything yet? Thanks again.
0 -
Updated to the Beta, deleted indexes, still no index after indexer stopped working on its on again, leaving no crash log... 19 days and counting.
0 -
Michael Lyman said:
Updated to the Beta, deleted indexes, still no index after indexer stopped working on its on again, leaving no crash log... 19 days and counting.
Michael, are you the same patient soul who had all those index crashing problems for the weeks after you first bought Logos? I feel so badly for you. You seem unusually cursed. I wonder if there is something fundamentally wrong with your machine? Maybe Logos should send a tech support person out to your location and trouble shoot it on site. I am so amazed you've kept with it for so long. And it is so puzzling why you're having so many problems and thousands of others are breezing through with no trouble at all.
0 -
Michael Lyman said:
Updated to the Beta, deleted indexes, still no index after indexer stopped working on its on again, leaving no crash log... 19 days and counting.
Developers are still working on this issue. Hopefully an answer will be available soon.
0 -
Rosie, Yes I had problems early on, but haven't for a long time again until now. My computer was new in October and I have had no problems with it except with Logos 4. I know some other people that have similar problems but haven't been persistent about getting it solved. I have no doubt we're in the minority and I understand Logos needs to prioritize based on how many users are having a similar problem. I still have Logos 3 and am happy with it. It still is millions of time faster than trying to find everything in hard copy and I use a lot of PBB titles so I'm content, but I have been to Camp Logos and bought a lot of Morris Proctor's materials and would like to be putting that to use as well. I know at that point there were a lot of new users whose program was crashing, because I kept hearing start-up music around the room,( I know how to turn mine off) of course, their computers may not have had the specs to run it either, mine does. I know it will be worth the wait. I wouldn't trade it in.
0 -
I am having the same problem. Search gives no finds. Have you received a solution yet?
0 -
gwcarlton@yahoo.com said:
I am having the same problem. Search gives no finds. Have you received a solution yet?
Yours may not be the same problem.
If L4 is indexing then wait until it has finished. If not then turn on Diagnostic Logging, start L4 and run your search. Stop L4 and upload Uploading Logs the logs.
Dave
===Windows 11 & Android 13
0 -
I'm trying a merge index command now. I've tried everything else I can think of.
0 -
Nope, that didn't work either.
0 -
0
-
Anything helpful in these latest logs?
0 -
Michael, I'm sorry the indexer hasn't been working for you. We're trying to figure out why.
How much RAM does your system have? Does your indexer process seem to be using a lot of memory when it runs? (You can see the memory usage of each process using Task Manager).
When the indexer quit without leaving a crash log, were you running any other software at that moment?
0 -
How much RAM does your system have? Does your indexer process seem
to be using a lot of memory when it runs? (You can see the memory usage
of each process using Task Manager).HP
G60-445DX Notebook PCAMD
Turion Dual-Core RM-75 2.20 GHzRAM:
4.0 GBWindows
7 Professional 64 bit Operating SystemNVIDIA
GeForce 8200M GIt does not seem to be using a lot of memory, it has indexed successfully numerous times since the last problem. I have set the priority to high sometimes to see if that would help.
When the indexer quit without leaving a crash log, were you running any other software at that moment?
Firefox, Logos 3, & Windows Live Mail, sometimes nothing when I have let it run as I was going to bed.
0 -
I just installed the latest Beta. It indexed for maybe a minute and stopped. No logs except for this and I have logging enabled...
0 -
Log from today.
0 -
I deleted my resource manager db and the bible and library index forcing a new index. Here are the latest log files. Indexing ran for only a short time. Why is there not a index crash log at least?
0 -
When the indexer quits without a log, does Logos4 quit too? (if it was open)
0 -
No, It is open and doesn't quit, it hasn't crashed for a long time, of course, I'm using Logos 3 most of the time right now.
0 -
I restarted windows and now I have a Bible Index again!!! I used CCleaner and cleaned up disk space. It's still indexing... I'll check back later.
0 -
Good. How low was the disk space before cleanup?
0 -
117 GB... and the indexer has now stopped and I have NO library index... only a Bible Index. [*-)]
0 -
Might I suggest something out of desperation!
- Hang on to your Bible Index!!
- Change Use Internet to NO in Program Settings (we don't want any downloads!)
- Backup your Resources folder
- Delete most of your resources (*.logos4/*.lbxlls only) but include all bibles and their dependencies eg ESV.logos4, ESVNT.lbsrvi, ESVOT.lbsrvi
- Delete the LibraryIndex folder
- Start L4
- Let it index
If that succeeds we'll do another increment of resources from the backup.
Dave
===Windows 11 & Android 13
0 -
I did this:
went to bed, got up this morning and I had an index again!!! I'd done it before and it hadn't worked, but this time it did!
0 -
Michael Lyman said:
I did this:
went to bed, got up this morning and I had an index again!!! I'd done it before and it hadn't worked, but this time it did!
Maybe you have a flakey hard disk. Have all the problems you've had in the past been on this same computer? (I seem to recall you had two computers, one of which didn't have problems.) Maybe if it happens again it's time to replace your hard disk. When you start having these sorts of problems frequently (even if automatically recovering from bad sectors takes care of it), it's usually an indication that your hard disk is headed for a catastrophic failure. Better to catch it before it happens than have it happen on you when you're unprepared.
0 -
Michael Lyman said:
went to bed, got up this morning and I had an index again!!! I'd done it before and it hadn't worked, but this time it did!
HD & memory problems were always likely given the unpredictable pattern of where indexing stopped eg. you reported a complete bible index when it hadn't completed indexing previously.
Start a cmd box with admin privilege and run chkdsk c:
When it completes report the # of kB in Bad Sectors and # of bytes in each Allocation Unit. This will give an idea of the damage on the HD, but you should definitely ensure you have a complete backup.
Dave
===Windows 11 & Android 13
0 -
Didn't find any problems. Here's what was found. Thanks again for everyone's help!
0
