Logos 4 Indexer stopped working and Runtime Error

2134.Logos4IndexerCrash.zipI have two problems that may or may not be related. (a) When I turn on my computer, I receive an error message saying “Logos 4 Indexer has stopped working”. This is even before I try to run Logos. (b) When I try to run Logos, there is a message that an update is ready to be installed, but if I try to install it (by clicking yes), I get a Runtime Error stating “This program has requested the Runtime to terminate in an unusual way.” The only log file in the Log Files folder is Logos4IndexerCrash.txt . I am running Logos 4.2a SR-3 (4.21.5.0932).

Find more posts tagged with

Comments

Rich DeRuiter

2134.Logos4IndexerCrash.zipI have two problems that may or may not be related. (a) When I turn on my computer, I receive an error message saying “Logos 4 Indexer has stopped working”. This is even before I try to run Logos. (b) When I try to run Logos, there is a message that an update is ready to be installed, but if I try to install it (by clicking yes), I get a Runtime Error stating “This program has requested the Runtime to terminate in an unusual way.” The only log file in the Log Files folder is Logos4IndexerCrash.txt . I am running Logos 4.2a SR-3 (4.21.5.0932).

You need to update Logos to 4.2a SR-4. There is a known indexing problem with the HCSB which was addressed by the upgrade to SR-4.

If upgrading alone doesn't fix this, you may need to remove and restore the HCSB. To do that open the settings panel (Tools>Program Settings) and expand the "Hidden Resources" section at the very bottom of that panel. Then open your Library (CTRL-L) and type HCSB to find the HCSB. Then click on that resource (anywhere but the title) and drag it to the Hidden Resources portion of the Settings panel. Close and restart Logos4. After L4 finishes indexing, you may 'unhide' the HCSB by clicking the little 'x' to the right of the title in the "Hidden resources' of your settings panel. Then restart L4 and let the HCSB download again and index (this won't take as long as it used to).

If even that doesn't work, we may need more drastic measures. Report back and we'll see what we can do.

Graham Criddle

https://community.logos.com/discussion/comment/244541#Comment_244541

You need to update Logos to 4.2a SR-4

Hi Richard

Any reason you are suggesting SR-4 as opposed to -5?

Graham

Rich DeRuiter

https://community.logos.com/discussion/comment/244549#Comment_244549

You need to update Logos to 4.2a SR-4

Hi Richard

Any reason you are suggesting SR-4 as opposed to -5?

Graham

Yes. Here's the reason: I forgot we were on 5 (I'm on the beta).

Oops! [:$]

[sigh.]

Johan Thom

https://community.logos.com/discussion/comment/244541#Comment_244541

How do I upgrade to SR-4? I get a Runtime Error when I try to install the update; see (b) in my original post.

Graham Criddle

https://community.logos.com/discussion/comment/244712#Comment_244712

Hi Johan

How do I upgrade to SR-4?

Can you install the update manually using Logos4Setup at http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe?

Graham

Johan Thom

https://community.logos.com/discussion/comment/244713#Comment_244713

Graham, no - I get the same Runtime Error message.

Johan

Dave Hooton

https://community.logos.com/discussion/comment/244747#Comment_244747

Graham, no - I get the same Runtime Error message.

Johan

Try a reinstall as follows (re-downloading resources will be avoided):-

backup your Resources folder
uninstall Logos4 from Control Panel (leave PreRequisites)
delete the \Logos4 folder
install Logos4 as per Method 3

Further information will be found in the above wiki article.

Ralph Mauch

https://community.logos.com/discussion/comment/244713#Comment_244713

I've updated and it seems to have fixed the indexer crash, however I noticed at startup a couple of times that the logos icon appears and says it's indexing, but it shouldn't be, because nothing has been downloaded. This goes away after a while, but twice now I had to stop logos4 and restart to make it go away.

Has anyone else noticed this too? The last two days it hasn't happened, but I thought it a bit strange.

Ralph

Rich DeRuiter

https://community.logos.com/discussion/comment/244790#Comment_244790

I've updated and it seems to have fixed the indexer crash, however I noticed at startup a couple of times that the logos icon appears and says it's indexing, but it shouldn't be, because nothing has been downloaded. This goes away after a while, but twice now I had to stop logos4 and restart to make it go away.

Has anyone else noticed this too? The last two days it hasn't happened, but I thought it a bit strange.

Ralph

It is common behavior for the indexer to start when L4 starts. It always checks to make sure the index is finished (and the indexes are still there).

It is not common for the indexer to remain in the system tray indefinitely. Is there a message there when you hover with the mouse cursor?

Ralph Mauch

https://community.logos.com/discussion/comment/244793#Comment_244793

It is common behavior for the indexer to start when L4 starts. It always checks to make sure the index is finished (and the indexes are still there).

It is not common for the indexer to remain in the system tray indefinitely. Is there a message there when you hover with the mouse cursor?

Thanks Richard, that is good to know that it is common, maybe the couple of times it remained in the system tray, or where the hidden icons reside, was an oddity that I shouldn't worry about. No message when I hovered except that logos is indexing, and allowed me to stop the process for 4 hours. There was never anything in my searches that had that yellow message bar that some of the resources might not have all occurences due to indexing, which made me think that it wasn't actuallyh indexing, and my hard drive wasn't humming away at a fast pace. [:)] Since yesterday it isn't occuring any more then a few seconds at startup.

Ralph

Johan Thom

https://community.logos.com/discussion/comment/244751#Comment_244751

Dave, I have uninstalled Logos4, but I still get the Runtime Error when I try to reinstall, i.e. when I run Logos4Setup.exe. What else can I do?

Johan

Kevin Becker

https://community.logos.com/discussion/comment/245363#Comment_245363

Johan,

If that's the case I'd try a .NET repair/reinstall

for XP see: http://community.logos.com/forums/p/19022/143481.aspx#143481

for Vista/7 see: http://community.logos.com/forums/p/30141/223127.aspx#223127

Then try reinstalling Logos

Johan Thom

https://community.logos.com/discussion/comment/245389#Comment_245389

Kevin, it took me a while to get a reply from our IT people, but it does not seem as if there is anything wrong with my .NET. What is the next step - to uninstall Logos Prerequisites as well and do a complete new installation, or is it possible not to have to redownload my resources?

Kevin Becker

https://community.logos.com/discussion/comment/246887#Comment_246887

Kevin, it took me a while to get a reply from our IT people, but it does not seem as if there is anything wrong with my .NET. What is the next step - to uninstall Logos Prerequisites as well and do a complete new installation, or is it possible not to have to redownload my resources?

You can back up your resources to avoid re-downloading, but uninstalling Logos probably deleted them.

See: http://wiki.logos.com/Quick_Installation_onto_multiple_computers for more details about backing up resources for a reinstall

Uninstalling/Reinstalling the prerequisites is worth a try.

Johan Thom

https://community.logos.com/discussion/comment/246888#Comment_246888

I have backed up my resources before uninstalling. Which of the three methods should I now use?

Kevin Becker

https://community.logos.com/discussion/comment/246897#Comment_246897

I would use Method 3, just in case there was any problems with your indexes.

Craig Fildes

https://community.logos.com/discussion/comment/246898#Comment_246898

Try turning off all your firewalls and protection programs. One of mine was causing the problem.

Dave Hooton

https://community.logos.com/discussion/comment/298343#Comment_298343

Try turning off all your firewalls and protection programs. One of mine was causing the problem.

I nearly fell for the "really old thread trap" - from May 2011.