indexing bug
Comments
-
I also hid the reverse interlinerar bibles and had my indexing complete for the first time. However, I starting bringing in each hidden resource one by one and I got a crash each time on the first four before I quit. I'm wondering if I'm doing anything wrong. On the first crash (ESV) I removed ESV again and added back the next one (notes are at home so I don't have which one) before I restarted Logos. Once restarted Logos downloaded the new resource and started indexing. I repeated this process four times and each time it crashed before completing the indexing. So I made sure all the reverse interliners were hidden and I started up Logos and it started indexing again. It was late so I let it run but it seemed that it was doing the whole index all over again. But I was up to 18% and still going so I don't think it was going to crash. Any similar experiences by anyone else. Any other advice or could all reverse interlinears be the problem.
I'll try some other things tonight but if I have to wait for the full indexing to occur inbetween hiding and unhiding resources it could take some time.
0 -
Jerry Self said:
I got a crash each time on the first four before I quit
This is quite serious but it is not related to anything you have done. I suggest re-hiding all RI's and getting back to a stable index, then contact Logos Technical Support. Please keep us in the loop, though.
Dave
===Windows 11 & Android 13
0 -
Thanks Dave - I experienced the same as Jerry. I've emailed tech support.
Mike
0 -
Update:
Came home from work today after the clean index that I described from last night. I still had my reverse interlinears hidden. I started unhiding them one by one but I didn't start with any of the four that had crashed on me the night before. Everyone of them indexed without a crash, even the ESV which was the first to crash after the clean index that I had yesterday. I don't have any explaination but now I have a complete library indexed.
One thing I did was to open up my Task Manager and watched the processes going on. That allowed me to see the Logos Indexer doing it's thing, see how much of the CPU it was using, and how much memory it was using. One other thing I did differently tonight was to make sure my Logos icon was visible in my task bar so when Logos was doing something in the background I could see it, hover over the icon and get some info about what was going on and how the progress was. That allowed me to react to the notifications that were associated to the icon as they popped up. I followed the instructions on the notifications and let Logos stop and start by clicking on the notifications instead of starting and stopping on my own. I think I was fighting Logos last night by starting up Logos while it was trying to start itself up. However, this does not explain why I had to hide all of the reverse interlinear bibles to get my first clean index and now why each could be added back in without a crash.
I hope this helps in some way. I'll keep following the posts to see what's going on. I would like to know what is causing this and not just be happy that my problem is fixed. You guys have been critical for getting me this far.
0 -
Jerry Self said:
However, this does not explain why I had to hide all of the reverse interlinear bibles to get my first clean index and now why each could be added back in without a crash.
Thank you for the update. Michael and yourself have shown conclusively that there is an issue with indexing the Reverse Interlinear resources, but Logos do not yet know the cause (they have been unable to reproduce the crash). I'm pleased that the workaround can produce a workable installation without the RI's and even lead to a complete resolution in your case.
Dave
===Windows 11 & Android 13
0 -
I'm baaack! Things are not as good as I had hoped. I had a chance to start using some of the reverse interlinears last night and ran into problems. For the ESV when I do a right click on a word and select Lemma and then "Search This Resource" I get zero hits. This happens for any word I select. For the the Cambridge Paragraph Bible It does the same thing. For the NIV the reverse interlinear window at the bottom does'nt show up even thought the button is present. I click on the button and nothing comes up. For the New Living Translation I don't even have the button at the top. For the other interlinears the "Search This Resources" seems to work. Tonight I will try a "Rebuild Index" but I don't have much hope. I'm still hoping Logos can figure this out. Let me know if there is anything else I can try.
0 -
Jerry Self said:
I'm baaack! Things are not as good as I had hoped. I had a chance to start using some of the reverse interlinears last night and ran into problems. For the ESV when I do a right click on a word and select Lemma and then "Search This Resource" I get zero hits. This happens for any word I select. For the the Cambridge Paragraph Bible It does the same thing. For the NIV the reverse interlinear window at the bottom does'nt show up even thought the button is present. I click on the button and nothing comes up. For the New Living Translation I don't even have the button at the top. For the other interlinears the "Search This Resources" seems to work. Tonight I will try a "Rebuild Index" but I don't have much hope. I'm still hoping Logos can figure this out. Let me know if there is anything else I can try.
My guess is that you have a corrupt database somewhere.
But have you tried rebuilding just the Bible index? Before doing that enable logging so we can see what's going on.
- Enable logging (http://wiki.logos.com/Diagnostic_Logging)
- Run the rebuild Bible index command and let indexing finish completely.
- Shut down Logos4 and before restarting post all the logs and other files in Documents/Logos Log Files (http://wiki.logos.com/Uploading_Logs).
Regarding
the NIV, it is incomplete and would only show RI data in the NT.
However, the NLT Interlinear button should be visible regardless of the
passage.Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I did as you suggested and a few seconds into the indexing it stopped.
Here are the logs
0 -
Just purchased a new computer and Logos. It's stops indexing around 7%. Hope someone can help!
Thanks!
JD
0 -
Jerry Self said:
I did as you suggested and a few seconds into the indexing it stopped.
Here are the logs
JD said:Just purchased a new computer and Logos. It's stops indexing around 7%. Hope someone can help!
Thanks!
JD
Welcome [:D]
Appears Logos 4.2b SR-1 (4.22.5.1109) is encountering a protected memory error during indexing on Windows 7 with Service Pack 1.
For grins on a Windows 7 computer with Service Pack 1 running Logos 4.3 Release Candidate 1 (4.30.0.1498), issued Rebuild Index command to completely rebuild Bible and Library Indexes, which completed without encountering protected memory error. A release candidate should be stable for daily use. If no significant bug(s) are reported in next few days (am aware of potential sync issue), then Logos 4.3 RC 1 would become stable 4.3 release. Earlier in this thread, Logos mentioned 4.3 indexing code change => http://community.logos.com/forums/p/35501/269974.aspx#269974 Option: could install current Beta (Logos 4.3 RC 1) to see if indexing bug went away with code change. Wiki page => Logos 4 Beta Program has Beta download link. Also PC Beta forum thread => 4.3 Release Candidate 1 (v4.30.0.1498) shipping soon has update channel command plus announced Personal Book Builder (PBB) is free.
Keep Smiling [:)]
0 -
The problem is indicated as being unable to write to protected memory, which is usually due to corrupt memory.
This came up a week or two ago with someone else. I'm not sure it was resolved.
I suggest that you contact tech support.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
JD said:
Just purchased a new computer and Logos. It's stops indexing around 7%. Hope someone can help!
Thanks!
JD
See my reply to Jerry above.
This is an unresolved problem. Please save your logs and contact tech support.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
My indexer/updater is needing to close now too since my computer shutoff abruptly last night. This is the log,...Is there a resource I could remove also to fix?
0 -
Douglas said:
My indexer/updater is needing to close now too since my computer shutoff abruptly last night. This is the log,...Is there a resource I could remove also to fix?
This appears to be a different issue than the two above.
To answer your question we'd need to see the indexer.log as the crash txt file doesn't tell us which resource, or user content is causing the problem.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Appears Logos 4.2b SR-1 (4.22.5.1109) is encountering a protected memory error during indexing on Windows 7 with Service Pack 1.
Protected memory error also happened with Logos 4.3 RC 1 on Windows 7 Service Pack 1 => http://community.logos.com/forums/p/36252/271840.aspx#271840
Personally puzzling about what is different about my pair of 64 bit Windows 7 Service Pack 1 configurations that can index my entire library and ones not working.
Keep Smiling [:)]
0 -
Richard DeRuiter said:Douglas said:
My indexer/updater is needing to close now too since my computer shutoff abruptly last night. This is the log,...Is there a resource I could remove also to fix?
This appears to be a different issue than the two above.
I'm sure the problem will be resolved by allowing an update from 4.0c to the latest version 4.2b SR-1 eg. using http://downloads.logos.com/LBS4/Installer/4.22.5.1109/Logos4Setup.exe
Dave
===Windows 11 & Android 13
0 -
Personally puzzling about what is different about my pair of 64 bit Windows 7 Service Pack 1 configurations that can index my entire library and ones not working.
I don't think it is connected with 7 SP1, nor any hardware issue (been down that path too many times). Reverse Interlinears are particularly suspect but Logos have yet to reproduce the error for themselves.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Richard DeRuiter said:Douglas said:
My indexer/updater is needing to close now too since my computer shutoff abruptly last night. This is the log,...Is there a resource I could remove also to fix?
This appears to be a different issue than the two above.
I'm sure the problem will be resolved by allowing an update from 4.0c to the latest version 4.2b SR-1 eg. using http://downloads.logos.com/LBS4/Installer/4.22.5.1109/Logos4Setup.exe
Thank You. I had to use a "copy" version a few night ago to fix a syncing issue, and it was not as up-to-date as the previous copy. It is on the Preparing your library right now...Does it normally index at this phase?
0 -
Douglas said:
It is on the Preparing your library right now...Does it normally index at this phase?
You can expect it to index as part of this phase given the previous failure.
Dave
===Windows 11 & Android 13
0 -
Hey Dave!
Thank you very much for the Logos Setup update post, it even fixed the shortcut bar not syncronizing.
0 -
Dave Hooton said:
I'm sure the problem will be resolved by allowing an update from 4.0c to the latest version 4.2b SR-1
[sigh]
Gotta remember to look at that first line first.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I was using a system with Windows 7 quad core (have returned it to get Intel in same config rather than AMD) and had the same problem with indexing - protected memory error. I solved it by copying over my Vista installation which worked to the Windows 7 computer - see the Wiki about installing on multiple pcs. From that point forward it seemed to work ok. It involved deleting certain folders on the Windows 7 computer in the Data folder for L4 and then copying over those same folders from the working Vista installation I have. The copying was done after a fresh install of L4 without allowing it to do a download of resources or a fresh indexing. See this article http://wiki.logos.com/Quick_Installation_onto_multiple_computers. I believe it was method 2 that I used. Either way it worked for me.
0 -
Dave Hooton said:
Personally puzzling about what is different about my pair of 64 bit Windows 7 Service Pack 1 configurations that can index my entire library and ones not working.
I don't think it is connected with 7 SP1, nor any hardware issue (been down that path too many times). Reverse Interlinears are particularly suspect but Logos have yet to reproduce the error for themselves.
Not know if connected with Windows 7 Service Pack 1; so far have not seen a protected memory error without Windows 7 Service Pack 1, as noted by Bradley => http://community.logos.com/forums/p/35501/270780.aspx#270780 (have seen 4.2b SR-1 and 4.3 RC 1)
After rereading Bradley's earlier replies => http://community.logos.com/forums/p/35501/269914.aspx#269914
wondering what anti-virus and anti-malware software is installed ? (possibly real time scanning interference)
On one laptop have AVG Free Edition 2011, version: 10.0.1390; newer laptop has Avast Free Ant-Virus 6.0.1203 (both laptops can completely rebuild Logos 4.3 RC 1 indexes: newer laptop is noticeably faster: Bible index done in 14m 54.6s vis 35m 41.4s and Library index done in 1h 26m 54s vis 2h 19m 13s; appears 2nd generation 2.00 GHz Quad Core i7 is bit faster than 2.26 GHz Core 2 Duo).
While researching, found one article using SQL Server CE with similar error => http://stackoverflow.com/questions/2423458/attempted-to-read-or-write-protected-memory-sql-compact-and-net that was fixed by changing database connection code (software).
Keep Smiling [:)]
0 -
Tim Engwer said:
I believe it was method 2 that I used. Either way it worked for me.
Most likely Method 2. But good to know that it solved your indexing problem.
Dave
===Windows 11 & Android 13
0 -
The "IndexingException: Attempted to read or write protected memory" crash appears to be related to the new AMD A6 and A8 chips. See the update I posted here: http://community.logos.com/forums/p/36252/275076.aspx#275076
0 -
The only way that I was able to work around it was to do the 'method 1'
copy of a working installation from my old Intel-based desktop to my AMD A8-based laptop. It seems that having a working index from the initial installation and updating from there helped to avoid whatever the initial indexing was hitting.Thanks
Mike
0 -
Any work arounds other than having a indexed copy lying around?; I'm starting to get pretty frustrated.
0 -
I've ordered an AMD A6-3400M system for testing, which I hope will let us reproduce and fix the issue. As I mentioned, this is one of the strangest bugs that I've ever seen, so we may be a week or more out from a fix.
The only known workaround is to use an Intel CPU...
0 -
On a hunch, I tried setting the AFFINITY of LOGOSINDEXER.EXE To a single core (0); It finished without problem, when before it crashed repeatedly; I'm running on an AMD A6-3400M APU with Radeon(tm) HD Graphics 1.40GHZ)
I suspect the problem occurs when you're taxing the core of the CPU that's dedicated to the graphics card on a chip
Hopefully this helps other users in the same boat!
0 -
Thanks for this feedback! That's a great workaround (and I wish I had thought of it).
I'll pass your suggestion on to Tech Support so they can let our other affected customers know.
0
