Lately I have been getting a windows error message saying that the indexing was unable to continue (Vista). SHould I be concerned that L4 is not working properly or do you think this is a windows problem? Any suggestions?
Larry Dix
Hey Larry,
I'll join you in that my indexing starts every time and then "Logos 4 Indexer has stopped working" sign comes up. But I updated something yesterday and don't exactly know why or what it was then the indexer started. I've been through that before but I've never had a problem. This doesn't seem to want to stop.
Windows 7 (instead of your vista) AMD Athlon IIx2 235e processor, 2.7ghz, 4 gb ram, ddr 3 sdram, 7200 rpm, 500 gb memory, 64 bit desktop HP
Just wanted to join you since no one answered yet.
"You are not alone"
tim
Had this problem yesterday (see post about "Creating a New Index Speeds up Program?" which I duplicated below) and if you delete the"Library Index" folder in Logos 4 program files (or cut and save it to another location as I mentioned below,) then Logos will recreate an entirely new index. Takes longer, but I found it helped the program run better, so there may be a bonus.
(My post follows:)
Is it me, but yesterday I had to delete the Library Index folder after I recieved the Galaxie file updates (would not complete the indexing function). To do so I first saved the folder and its contents to another location, then restarted Logos 4 and it automatically recreated an entirely new folder and index (several hours). When done, I noticed two things.
First the new index was significantly smaller in size than the old one (4+ gig to 2.7 gig).
Second, my Logos 4 seems to work faster! This includes running passage guides, searching, information lookup, etc.
Wish I could do a more controlled test, but I already deleted the old index folder before I noticed this. Otherwise I would try switching it with the new one and would run identical program functions and time them.
I wonder if anyone else has had this experience?
Larry,
4.0a has a hard time merging indexes; it doesn't seem to work. The bug has been fixed in 4.0b but that hasn't been released yet.
Normally, I would ask that you post logs (http://wiki.logos.com/Diagnostic_Logging http://wiki.logos.com/Uploading_Logs ) but deleting the contents of the index folder and letting Logos reindex (as David above suggested) is likely to work. So, here's the path for your index, delete the contents of this folder C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\LibraryIndex . Go ahead and enable indexing logging before you start, should the indexer crash again it will give us some clues what the next step should be.
Go ahead and enable indexing before you start, should the indexer crash again it will give us some clues what the next step should be.
I think he means go ahead and enable logging before you start.
Thanks Rosie.
Thanks for the suggestion. How do you enable logging?
Thanks for the suggestion. How do you enable logging? Larry Dix
http://wiki.logos.com/Diagnostic_Logging
It seems to be a recent problem but I am having the same issue. In some cases the indexer runs for a while. This morning it ran for only a couple of minutes. Sure hope it's fixed soon.
