L4 won't index since last large update
It then tried to index and works for a while and then stops and says the indexer won't work and wants to send an error report to Microsoft. It does this every time I start my computer as part of the startup routine. This has made it part of my start up routine to pause the indexer for 4 hours so it will run and crash when I am not working at my computer.
It also means that all those updated books are not indexed into my library.
Until the automatic update, things were working fine and it would index as needed with updated or new books.
My computer is running Windows XP. Core 2 Duo, Centrino Duo.
I would love to get Logos working again and am not sure what to do. (I believe I have figured out how to remove the indexer from the startup configuration, but will need to restart the computer to be sure.)
Thank you for your help,
Rob
www.3rdcultureliving.com - Simple Abundant Legacy
Comments
-
Rob said:
Logos automatically updated a while ago including a huge resource download.
It then tried to index and works for a while and then stops and says the indexer won't work and wants to send an error report to Microsoft. It does this every time I start my computer as part of the startup routine. This has made it part of my start up routine to pause the indexer for 4 hours so it will run and crash when I am not working at my computer.
It also means that all those updated books are not indexed into my library.
Until the automatic update, things were working fine and it would index as needed with updated or new books.
My computer is running Windows XP. Core 2 Duo, Centrino Duo.
I would love to get Logos working again and am not sure what to do. (I believe I have figured out how to remove the indexer from the startup configuration, but will need to restart the computer to be sure.)
Thank you for your help,
RobEnable logging and follow the instructions on that wiki page to upload them here.
But you may want to try this solution that has worked for some with the indexing crash issue:
This issue has been seen many times, and is often due to an out of date resource. You may be able to solve it by pausing the indexing (as you've been doing), start L4 and type update resources in the command bar. This will check all your resources for possible updates and can take some time, depending on the size of your library. If any new resources download, restart Logos4 and let it do it's thing while it loads. After your homepage, or layout is finished loading, pause indexing again (if necessary), and type update resources a second time, to ensure that the first attempt didn't miss anything. If nothing new gets loaded, enable logging (see above) and restart your computer.
Report back if this doesn't fix it, and also post your logs.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Hi Rich,
Thank you for the quick reply. I tried updating, but it still crashed. Here are my log reports.
Thank you so much for your help.
Rob
Note: I am not sure if I attached the log reports correctly. It is just showing up as a line of text [View:http....] I will see what happens after I post.
www.3rdcultureliving.com - Simple Abundant Legacy
0 -
Rob said:
Hi Rich,
Thank you for the quick reply. I tried updating, but it still crashed. Here are my log reports.
Thank you so much for your help.
Rob
Note: I am not sure if I attached the log reports correctly. It is just showing up as a line of text [View:http....] I will see what happens after I post.
They posted fine.
Your Logos4.log shows that there was stuff downloading when the log stopped recording, so there may still be items downloading. Let that finish (pause indexing, if you can pause it before it crashes). If you can do that, you may not have to do what I'm suggesting below.
I'm not the best at understanding these, but it looks to me like there's a problem with the LGNTI. One of the easiest ways to fix this is to remove the resource and have Logos re-download it. There are two ways to do that:
Method 1: Pause indexing again, open Logos4, open Program Settings from the Tools menu and "Hide" the LGNTI (you seem to have a lot of hidden resources, so I assume you know how to do this). Then close and reopen Logos4. The LGNTI should then be deleted. Double check your Library to make sure. If it's gone, unhide it and Logos should download a fresh copy for you.
Method 2: Pause indexing, close L4, navigate to your resources directory and delete LGNTI.Logos4. Then reopen Logos4 which should detect the missing resource and download a fresh copy for you. If it doesn't detect the missing resource, you'd need to type in update resources to force L4 to download it.)
Choose one method (not both) and report back. There are other things to try, including deleting your resource indexes, but I'm hoping that this will do it for you.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Rob said:
Thank you for the quick reply. I tried updating, but it still crashed. Here are my log reports.
Try the command update resources once more.
If that does not download any resources then try:
- delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
- restart Logos4
This should download the resource causing the error (KJV1900) and start indexing.EDIT: I see that Richard thinks the LGNTI is the problem, but that had indexed successfully.
Dave
===Windows 11 & Android 13
0 - delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
-
Dave Hooton said:Rob said:
Thank you for the quick reply. I tried updating, but it still crashed. Here are my log reports.
Try the command update resources once more.
If that does not download any resources then try:
- delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
- restart Logos4
This should download the resource causing the error (KJV1900) and start indexing.EDIT: I see that Richard thinks the LGNTI is the problem, but that had indexed successfully.
I gotta ask, Dave. How do you conclude, by reading these log files, that the LGNTI finished and the KJV1900 is the problem? I'm not disputing you, but I just can't figure out how you conclude that by looking at the indexer log.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 - delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
-
Richard DeRuiter said:
but I just can't figure out how you conclude that by looking at the indexer log.
2010-12-15 15:57:35.4375 9 Info BibleIndex (Timed) Indexing LLS:KJV1900
...2010-12-15 16:01:39.5937 7 Info BibleIndex (Timed) Indexing LLS:LGNTI
...2010-12-15 16:03:55.4375 7 Info BibleIndex (2m 15.8s) Indexing LLS:LGNTI
2010-12-15 16:03:55.4375 7 Info BibleIndex (Timed) Indexing LLS:LLXXI
2010-12-15 16:04:17.4687 7 Info WindowsIndexerProgress 30 of 148 resources indexed; total progress is 15.0%
2010-12-15 16:04:19.6875 9 Error Program Unhandled exception:The error occurred on thread 9 and the last program that started (Timed) there was KJV1900. If it had finished there would be a time like (2m 15.8s), which is how I know that LGNTI finished.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Richard DeRuiter said:
but I just can't figure out how you conclude that by looking at the indexer log.
2010-12-15 15:57:35.4375 9 Info BibleIndex (Timed) Indexing LLS:KJV1900
...2010-12-15 16:01:39.5937 7 Info BibleIndex (Timed) Indexing LLS:LGNTI
...2010-12-15 16:03:55.4375 7 Info BibleIndex (2m 15.8s) Indexing LLS:LGNTI
2010-12-15 16:03:55.4375 7 Info BibleIndex (Timed) Indexing LLS:LLXXI
2010-12-15 16:04:17.4687 7 Info WindowsIndexerProgress 30 of 148 resources indexed; total progress is 15.0%
2010-12-15 16:04:19.6875 9 Error Program Unhandled exception:The error occurred on thread 9 and the last program that started (Timed) there was KJV1900. If it had finished there would be a time like (2m 15.8s), which is how I know that LGNTI finished.
Aha! I didn't realize those were thread designations (not that I had any other idea about what they were).
Thanks!
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
OK, I have the same problem as others. Everytime I start Logos 4 it starts, but never completes, indexing. I have tried the "update resources" and deleting the KJV1900 files mentioned above. They do not re-download and I continue to not be able to complete the indexing process.
The crash text file shows an error, "Error ID: 7249
Error detail: IndexingException: No translation word for specified document position"Can you help?
Thanks.
0 -
Curtis A. Tilton said:
OK, I have the same problem as others. Everytime I start Logos 4 it starts, but never completes, indexing. I have tried the "update resources" and deleting the KJV1900 files mentioned above. They do not re-download and I continue to not be able to complete the indexing process.
The crash text file shows an error, "Error ID: 7249
Error detail: IndexingException: No translation word for specified document position"Can you help?
Okay, following Dave's guidelines, it looks to me like the problem is with the NKJV (LLS:1.0.30). Try deleting that, as you did the KJV1900 and restart L4 to download it again.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Rich, I think the error is in thread 7 which is attempting to index LLS:1.0.71 which is the NASB95. Otherwise I'd do as you said.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
Rich, I think the error is in thread 7 which is attempting to index LLS:1.0.71 which is the NASB95. Otherwise I'd do as you said.
AARRG! You're right! I must have been dislexic or something. Those two lines are one above the other. Yes, the NKJV finished. It then started the NASB95. [Heavy sigh -- I'll get it right yet.]
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
So, Rich, Mark, or Dave,
What causes these resource files to make indexing not work as it is supposed to? I'm no geek but would like to understand a little better. Thanks!
0 -
Joan Korte said:
What causes these resource files to make indexing not work as it is supposed to?
I don't know. There must be a minor corruption in the file which doesn't affect its display or other use in Logos. Since the resources are tagged for certain things to be indexed it is probably something in that part of the data that gets messed up. Just guessing.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Maybe I am going to sound like the kid who keeps asking why? [A] so why would my files not be corrupt, too?
0 -
Thanks to all. That seems to have fixed it. I deleted NASB95, then typed, "update resources" in the command window. It downloaded some updates and then I restarted Logos and got the reindexing message. However, this time it seems to have finished and I restarted the program with no further indexing messages. Thanks again.
0 -
Joan Korte said:
so why would my files not be corrupt, too?
Apparently it happens on individual hard drives, not with the resource from Logos. Something must cause a bit to get dropped some time on one's hard drive and that does it. Again, I'm making a guess, but I'm sure it does have to do with the locally stored resource or we'd all have the problem.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Curtis A. Tilton said:
However, this time it seems to have finished and I restarted the program with no further indexing messages.
Good. Thanks for getting back to us and affirming the solution worked.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
Apparently it happens on individual hard drives, not with the resource from Logos.
It only happens on Reverse Interlinears and the resource sometimes appears to finish indexing after the crash! I'm puzzled why everybody doesn't get it. Anyway, I created a wiki bug report to get Logos involved with this issue.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
It only happens on Reverse Interlinears
And hasn't it been mainly two of them: the 1900 KJV and the NASB95?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Dave
===Windows 11 & Android 13
0 -
Hi Rich,
I too have the indexing problem for the last several days. I have attached the error log and hope you would be able to guide me on what is happening and how to fix it.
0 -
Hi Rich,
I too have the indexing problem for the last several days. I have attached the error log and hope you would be able to guide me on what is happening and how to fix it.
0 -
Hi Rich,
I too have the indexing problem for the last several days. I have attached the error log and hope you would be able to guide me on what is happening and how to fix it.
0 -
Kurien Varghese said:
Hi Rich,
I too have the indexing problem for the last several days. I have attached the error log and hope you would be able to guide me on what is happening and how to fix it.
We'd need to see the indexer log too, the crash log doesn't tell us which resource is the issue. Follow the instructions for enabling diagnostic logging and post the logs here, as directed by that wiki page.
Or, you could simply delete and replace the KJV1900 and the NASB95 (follow the instructions given earlier in this thread), and see if that fixes it (those two resources seem to be the culprits for this problem with this update).
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I deleted KJV1900 and NASB95 and tried 'update resource' wich said there are no resources to update. Then I started Logos 4 with diagnostic logging and attached the Indexer logo. I am using Windows 7 professional.4657.Logos4Indexer.log
0 -
Kurien Varghese said:
I deleted KJV1900 and NASB95 and tried 'update resource' wich said there are no resources to update. Then I started Logos 4 with diagnostic logging and attached the Indexer logo. I am using Windows 7 professional.4657.Logos4Indexer.log
First, note that the command is update resources (with the 's' on the end). If you ran that command that way, you're fine. Otherwise, type it in the correct way and see what happens.
It looks to me like the issue here is the LEB, but I'm not sure, as I don't know what all the lines mean in the indexer log. But try deleting it (LEB.Logos4) and then typing update resources in the L4 command bar. See if that works.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Thank you for all the help. I deleted KJV1900 and NASB95 and it seems to have completed the indexing.
One strange thing. The KJV1900 redownloaded and is working fine. However, the NASB95 no longer exists in my library and is not in the "Resources" folder.
Is anyone else seeing this issue?
Thank you for all your help,
Rob
www.3rdcultureliving.com - Simple Abundant Legacy
0 -
-
Same effect even after doing the above - deleted LEB.logos4, ensured KJV1900 and NASB95 are also not in the resources folder. Did update resources again but I got the message 'no resources updated'. After restarting Logos 4, indexing started automatically and later got the message, Indexer stopped, sending error to Microsoft. Attached are the three logs after starting with diagnostic logging.
2134.Logos4Indexer.log the indexer log.
0 -
This shows a crash while indexing the LEB. So at this point it is time to stop trying various fixes and wait on a word from Logos.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Any idea on how often Logos looks at such issues or do I need to report the problem directly to the Technical Support. I still have the indexing problem but not much is heard in the forum which seems others may not be having or or got fixed.
0 -
One user reported it fixed by Technical Support, so that is the way to go!
Dave
===Windows 11 & Android 13
0 -
Although the problem was reported a week back I did not get any feedback from the Technical Support. Then I tried the 'Rebuild Index' option from the Command prompt which did a complete reindexing of the library taking around 4 hours and the problem was resolved. I had another automatic resource update and the reindex failed after the update. On checking the Resources I found the deleted files back in the resource folder. I deleted them again and Rebuilt Index - so far it seems to be working. I will wait until the next update to see if the deleted resources get downloaded again and the problem reappears.
0 -
Kurien Varghese said:
Although the problem was reported a week back I did not get any feedback from the Technical Support.
How did you contact tech support? They don't read the forums but they should get back to you if you report via email or phone. It is reasonable to nag them if you haven't heard back in a day or two.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I contacted them through the net and I got a response "
It is our goal here at Logos to provide you with the very best support possible. Please know that we'll respond to your e-mail as quickly as we can, normally in 24 to 48 hours.
Anyway the issue is resolved for the time being but I have to see what happens when a new update comes through.
0 -
Dave Hooton said:
Try the command update resources once more.
If that does not download any resources then try:
- delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
- restart Logos4
This should download the resource causing the error (KJV1900) and start indexing.Dave,
I had the same problem and upon checking my logs found that the KJV1900 was causing the issue for me as well. So I deleted the resources as per your instructions but when I restarted Logos and attempted to "update resources" It came back with the message "no updates found". I am currently indexing and logging the process so I will see what happens. Thoughts? Comments?
0 - delete KJV1900.logos4, KJV1900NT.lbsrvi, & KJV1900OT.lbsrvi from C:\Documents and Settings\CRU User\Local Settings\Application Data\Logos4\Data\pjwzyd4w.ghp\ResourceManager\Resources (use Folder Options in Control Panel to view hidden files and folders)
-
Bob Schlessman said:
I am currently indexing and logging the process so I will see what happens. Thoughts? Comments?
This is the solution that Tech Support have found:-
- Delete the NASB95.logos4,
NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and
KJV1900OT.lbsrvi files.
They are in
C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
deleted, restart Logos 4 and enter the command Update
Resources.
Allow the program
to download the updates and restart Logos 4 again.
After Logos 4 loads
check your library to make sure the Bibles have completely
re-downloaded:
Open the King James
Version (1900) and make sure the Interlinear Data is available in the
Old and
New Testaments.
Repeat with the New
American Standard Bible (1995).
If the books do not
show up they may be still in the Downloaded folder.
Close Logos
4 and
go to the following location
C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder
\ResourceManager\
Delete the
ResourceManager.db file and restart Logos 4 to force
discovery.
After Logos 4
reopens repeat step 4, if the Bibles appear to confirm the interlinear
information is there as well.
Let indexing complete and go from Step 4 above.
Dave
===Windows 11 & Android 13
0 - Delete the NASB95.logos4,
-
Dave Hooton said:Bob Schlessman said:
I am currently indexing and logging the process so I will see what happens. Thoughts? Comments?
This is the solution that Tech Support have found:-
- Delete the NASB95.logos4,
NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and
KJV1900OT.lbsrvi files.
They are in
C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
deleted, restart Logos 4 and enter the command Update
Resources.
Allow the program
to download the updates and restart Logos 4 again.
After Logos 4 loads
check your library to make sure the Bibles have completely
re-downloaded:
Open the King James
Version (1900) and make sure the Interlinear Data is available in the
Old and
New Testaments.
Repeat with the New
American Standard Bible (1995).
If the books do not
show up they may be still in the Downloaded folder.
Close Logos
4 and
go to the following location
C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder
\ResourceManager\
Delete the
ResourceManager.db file and restart Logos 4 to force
discovery.
After Logos 4
reopens repeat step 4, if the Bibles appear to confirm the interlinear
information is there as well.
Let indexing complete and go from Step 4 above.Followed the above instructions and it worked like a charm. Thank you Dave and all of the others who pursued this issue and made the solution available! [:D]
0 - Delete the NASB95.logos4,
-
Bob Schlessman said:
Followed the above instructions and it worked like a charm. Thank you Dave and all of the others who pursued this issue and made the solution available!
As we say in Oz, "No worries, Mate"
Have a happy New Year.
Dave
===Windows 11 & Android 13
0
