Another Indexing problem

Don D. Thompson

Download and installation went smoothly.  Large amount of information so took some time, but not unmanagable.

Indexing began and I expected a long process, left the machine to do its work.  Indexing seemed to end quickly, but I did not notice any error messages.  Hard disk space may have been an issue at that time.  I have since made room, so that should not be a current issue.

Whenever I run Logos 4 the indexer starts and very quickly gives the message "Logos Bible Software 4 Indexer has encountered a problem and needs to close.  We are sorry for the inconvenience."

The program runs and many resources are there.  I have a large library and cannot easily tell if any are missing. 

Log files attached.

George Allakhverdyan

Download and installation went smoothly.  Large amount of information so took some time, but not unmanagable.

Indexing began and I expected a long process, left the machine to do its work.  Indexing seemed to end quickly, but I did not notice any error messages.  Hard disk space may have been an issue at that time.  I have since made room, so that should not be a current issue.

Whenever I run Logos 4 the indexer starts and very quickly gives the message "Logos Bible Software 4 Indexer has encountered a problem and needs to close.  We are sorry for the inconvenience."

The program runs and many resources are there.  I have a large library and cannot easily tell if any are missing. 

Log files attached.

Thanks for the logs Don, I have submitted them.

George Allakhverdyan

https://community.logos.com/discussion/comment/8695#Comment_8695

To help identify which resource is causing this problem and if you want to hold that in a temporary folder until Beta two, download this file

http://downloads.logos.com/LBS4/LDLS4Installer/EnableLogging.js (right-click-->save as) and run it.

Next, download the Logos4Indexer.NLog.Config file which Bradley talks about here:

http://community.logos.com/forums/p/740/6990.aspx#6990

This way we may get some more details from your logs that could identify the bad resource. (The problem is pulling the cover graphic  for this resource in my library, which, since it doesn't have one, causes Logos4 to crash).

Don D. Thompson

https://community.logos.com/discussion/comment/8713#Comment_8713

Followed the instructions and moved 680 resources dated before Feb 2006 into a temporary location not in the resources path.  The Indexer still comes up with the same error message.  I have attached the new log files.

Don D. Thompson

https://community.logos.com/discussion/comment/9551#Comment_9551

Update to Beta 2 has allowed indexing to get farther into the process.  Download of the beta 2 did not have an icon in the system tray.   Beta 2 did not install until Logos 4 was restarted.  Indexing of resources and downloading updates is in progress, will see how far it gets running overnight.

Don D. Thompson

https://community.logos.com/discussion/comment/11047#Comment_11047

indexing went to 1 resource remaining then halted.  Error message:  Application has generated an exception that could not be handled.  Process ID 0x364 (838)  Thread ID 0x12e0 (4832)

It seemed to take a long time to download updates.  While it was helpful to get an indication of the download progress, there was no indication I saw of the total number of updates that were being processed (ie it went from downloading % of 1.1 G to % of 493 M etc).

Don D. Thompson

https://community.logos.com/discussion/comment/11161#Comment_11161

log files

George Allakhverdyan

https://community.logos.com/discussion/comment/11165#Comment_11165

If you could (if you have a fast internet connection) send us this file: C:\Documents and Settings\Don\Local
Settings\Application
Data\Logos4\Data\1ppubx35.ddy\ResourceManager\Resources\UNGERBBLHB.lbxlls, we can investigate it, in the mean time, before you install beta 2 directly try deleting this file and re-start.

 

Don D. Thompson

https://community.logos.com/discussion/comment/11347#Comment_11347

file must be too big and/or my connection too slow.  The connection times out when I try to attach it.  Beta 2 seems to have installed, it says it is beta 2 when I check the help-about.  The indexer program is running at the moment (and I am at work) so I will try deleting the file this evening.  I will keep you informed.

George Allakhverdyan

https://community.logos.com/discussion/comment/11392#Comment_11392

Are you connecting to your computer at home from work to test this? Yea that file is large and won't upload here, can you try to use http://www.megaupload.com, let me know, if it is going into Beta 2 at home then there shouldn't be a need for you to delete this file, the fix was stepping over this resource's cover image to not crash at that point, since it is lacking a cover image. So yea if all is well (like it should be) with Beta 2, don't delete the resource, however we would still like you to upload it so we can see what the problem was. Thanks.

Don D. Thompson

https://community.logos.com/discussion/comment/11419#Comment_11419

This is installed on my laptop and I connect both at home and at work.  I own the business so I have a bit of flexibility [;)] I am sending the file to Megauploader now, it says it has about an hour to go.  This indexing message came up after Beta 2 was installed.

George Allakhverdyan

https://community.logos.com/discussion/comment/11439#Comment_11439

I have to go home for the day soon, does mega uploader say how long the file will remain as a link?

Don D. Thompson

https://community.logos.com/discussion/comment/11439#Comment_11439

http://www.megaupload.com/?d=6QH9YYDG

Don D. Thompson

https://community.logos.com/discussion/comment/11445#Comment_11445

It looks like the file will stay there for 90 days unless I delete it

Don D. Thompson

https://community.logos.com/discussion/comment/11464#Comment_11464

I am a bit confused as to what to try now.  The Beta 2 downloaded and seems to have installed; the help about shows Logos Bible Software 4 Beta 2 (4.0.2.8804). 

When the indexer ran again it came up with the application error message "Application has generated an exception that could not be handled.  Process ID=0x17a4 (6052), Thread ID=)x107c (4220)."

 

A bit of additional information.  The indexer system tray icon showed 321 resources left to index.  Logos 4 (collection matching 0) shows 3946 resources and Logos 3 (Bibliography) shows 4003 unlocked titles.

 

 

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/11687#Comment_11687

When the indexer ran again it came up with the application error message "Application has generated an exception that could not be handled.  Process ID=0x17a4 (6052), Thread ID=)x107c (4220)."

Hi Don,

Did you delete the "C:\Documents and Settings\Don\Local Settings\Application Data\Logos4\Data\1ppubx35.ddy\ResourceManager\Resources\UNGERBBLHB.lbxlls" file? The last set of indexer logs you attached indicated that it's still trying (and failing) to process this file. Deleting it, then restarting Logos 4 should enable indexing to complete.

(I think George may have meant his reply for someone else, because your logs don't show you to have EXCVJERUS.lbxlls.)

Don D. Thompson

https://community.logos.com/discussion/comment/11717#Comment_11717

That was my confusion last night.  One post said to delete the UNGERBBLHB.lbxlls file and another said it should not be necessary.  I have now deleted that file and the indexer is running.  I do not have EXCVJERUS.lbxlls.  I will advise when the indexer stops, hopefully because it has completed [:)]

 

Don D. Thompson

https://community.logos.com/discussion/comment/11740#Comment_11740

that allowed the indexer to complete.  Thanks [:D]

Don D. Thompson

https://community.logos.com/discussion/comment/11880#Comment_11880

Beta 3 downloaded and installed quickly.  Then (some resources?) downloaded and indexing began.  Indexing crashed.  I found that the  UNGERBBLHB.lbxlls resource had reappeared.  Deleting it from the Logos 4 resources directory allowed the indexing to complete.  Indexing still took a considerable amount of time and demanded significant CPU resources.

George Allakhverdyan

https://community.logos.com/discussion/comment/13964#Comment_13964

Beta 3 downloaded and installed quickly.  Then (some resources?) downloaded and indexing began.  Indexing crashed.  I found that the  UNGERBBLHB.lbxlls resource had reappeared.  Deleting it from the Logos 4 resources directory allowed the indexing to complete.  Indexing still took a considerable amount of time and demanded significant CPU resources.

Thanks for the update.

George Allakhverdyan

https://community.logos.com/discussion/comment/13964#Comment_13964

Beta 3 downloaded and installed quickly.  Then (some resources?) downloaded and indexing began.  Indexing crashed.  I found that the  UNGERBBLHB.lbxlls resource had reappeared.  Deleting it from the Logos 4 resources directory allowed the indexing to complete.  Indexing still took a considerable amount of time and demanded significant CPU resources.

Hi, so the case is this, it scans your LDLS3 3 paths and copies it over to your resources folder, apparently that file is corrupt from your LDSLS3 resource path and is being copied over. You may obtain a new copy of the file here ftp://ftp.logos.com/LbxBooks/UNGERBBLHB.lbxlls

Don D. Thompson

https://community.logos.com/discussion/comment/14149#Comment_14149

Hi, so the case is this, it scans your LDLS3 3 paths and copies it over to your resources folder, apparently that file is corrupt from your LDSLS3 resource path and is being copied over. You may obtain a new copy of the file here ftp://ftp.logos.com/LbxBooks/UNGERBBLHB.lbxlls

I put a new copy of the UNGERBBLHB.lbxlls resource in the LDSLS3 resource folder.  I also added the Ariel's Bible Commentary: The Book of Genesis and the Charles Spurgeon Collection to L3.  As expected the indexing process began when I started L4.  I exited L4 and the indexer continued to run.  It seemed to get through the resources and was back to showing "Logos Bible Software is indexing your library" when I mouse over the icon in the system tray.  I went back in to L4 and the indexer seemed to restart.  I have now left the computer to run overnight and the indexer appears to be hung up.  Log files are attached.

I did scroll through the indexer log file and noticed that there are some warnings (near the beginning of the log) which suggest a few resources should be rebuilt.  Should I be downloading replacement LDSLS3 versions of these files?  There are other warnings and errors in the log.

Odd, the indexer seems to have stopped while I was writing this message.  Opening L4 did not cause the indexer to restart and it appears that the Spurgeon resources are included in the Library.