L4 won't index since last large update

Page 2 of 2 (40 items) < Previous 1 2
This post has 39 Replies | 3 Followers

Posts 24961
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Dec 18 2010 1:29 AM

Mark A. Smith:
And hasn't it been mainly two of them: the 1900 KJV and the NASB95?

Yes!

Dave
===

Windows & Android

Posts 11
Kurien Varghese | Forum Activity | Replied: Sat, Dec 18 2010 8:47 AM

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.

5125.Logos4IndexerCrash.txt

 

Posts 11
Kurien Varghese | Forum Activity | Replied: Sat, Dec 18 2010 8:47 AM

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.

5125.Logos4IndexerCrash.txt

 

Posts 11
Kurien Varghese | Forum Activity | Replied: Sat, Dec 18 2010 8:47 AM

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.

5125.Logos4IndexerCrash.txt

 

Posts 5564
Forum MVP
Rich DeRuiter | Forum Activity | Replied: Sat, Dec 18 2010 8:55 AM

Kurien Varghese:

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.

5125.Logos4IndexerCrash.txt

 

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)

Posts 11
Kurien Varghese | Forum Activity | Replied: Sat, Dec 18 2010 11:26 AM

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

Posts 5564
Forum MVP
Rich DeRuiter | Forum Activity | Replied: Sat, Dec 18 2010 12:07 PM

Kurien Varghese:

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)

Posts 94
Rob | Forum Activity | Replied: Sat, Dec 18 2010 8:17 PM

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

Posts 24961
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Dec 18 2010 9:12 PM

Rob:

However, the NASB95 no longer exists in my library and is not in the "Resources" folder.

Is anyone else seeing this issue?

Yes!  But I'd wait until we know the solution on Monday.

Dave
===

Windows & Android

Posts 11
Kurien Varghese | Forum Activity | Replied: Sun, Dec 19 2010 8:03 AM

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.

 

6675.Logos4.log

 

4135.Logos4IndexerCrash.txt

Posts 9090
Forum MVP
Mark Smith | Forum Activity | Replied: Sun, Dec 19 2010 11:04 AM

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

Posts 11
Kurien Varghese | Forum Activity | Replied: Tue, Dec 21 2010 6:36 PM

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.

Posts 24961
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Dec 21 2010 6:46 PM

One user reported it fixed by Technical Support, so that is the way to go!

Dave
===

Windows & Android

Posts 11
Kurien Varghese | Forum Activity | Replied: Mon, Dec 27 2010 9:14 AM

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.

Posts 26546
Forum MVP
MJ. Smith | Forum Activity | Replied: Mon, Dec 27 2010 12:23 PM

Kurien Varghese:
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 Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."

Posts 11
Kurien Varghese | Forum Activity | Replied: Tue, Dec 28 2010 6:54 AM

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.

Posts 291
Bob Schlessman | Forum Activity | Replied: Wed, Dec 29 2010 10:28 AM

Dave Hooton:

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?

 

Posts 24961
Forum MVP
Dave Hooton | Forum Activity | Replied: Wed, Dec 29 2010 3:00 PM

Bob Schlessman:
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:-

  1. Delete the NASB95.logos4, NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and KJV1900OT.lbsrvi files.
    1. They are in C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
  2. Once the files are deleted, restart Logos 4 and enter the command Update Resources.
  3. Allow the program to download the updates and restart Logos 4 again.
  4. After Logos 4 loads check your library to make sure the Bibles have completely re-downloaded:
    1. Open the King James Version (1900) and make sure the Interlinear Data is available in the Old and New Testaments.
    2. Repeat with the New American Standard Bible (1995).
  5. If the books do not show up they may be still in the Downloaded folder.
  6. Close Logos 4 and go to the following location C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder \ResourceManager\
  7. Delete the ResourceManager.db file and restart Logos 4 to force discovery.
  8. 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 & Android

Posts 291
Bob Schlessman | Forum Activity | Replied: Fri, Dec 31 2010 7:45 AM

Dave Hooton:

Bob Schlessman:
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:-

  1. Delete the NASB95.logos4, NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and KJV1900OT.lbsrvi files.
    1. They are in C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
  2. Once the files are deleted, restart Logos 4 and enter the command Update Resources.
  3. Allow the program to download the updates and restart Logos 4 again.
  4. After Logos 4 loads check your library to make sure the Bibles have completely re-downloaded:
    1. Open the King James Version (1900) and make sure the Interlinear Data is available in the Old and New Testaments.
    2. Repeat with the New American Standard Bible (1995).
  5. If the books do not show up they may be still in the Downloaded folder.
  6. Close Logos 4 and go to the following location C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder \ResourceManager\
  7. Delete the ResourceManager.db file and restart Logos 4 to force discovery.
  8. 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! Big Smile

Posts 24961
Forum MVP
Dave Hooton | Forum Activity | Replied: Fri, Dec 31 2010 9:04 PM

Bob Schlessman:
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 & Android

Page 2 of 2 (40 items) < Previous 1 2 | RSS