7331.Logos4.zipEverytime I start Windows7, the Logos4 Indexer "stops working" and I have to continually close it by using Task Mangager. Logos attempts to prepare My Library to no avail.
We will need the Logos4Indexer.log to know what the issue is. How long has this been happening?
5280.Logos4Indexer.zip
This has been going on for about a month now. Since I upgraded to Windows7. I work offshore so I couldn't report sooner.
I am having the same problem. I have uploaded a zip file with the indexer logs0602.Logos Log Files.zip.
When I am able to get Logos to load I am missing lots of my resources :-(
5280.Logos4Indexer.zip This has been going on for about a month now. Since I upgraded to Windows7. I work offshore so I couldn't report sooner.
This doesn't look good.
While I'm by no means an expert at parsing these logs, it looks to me like there's a problem with one of the utilities the indexer uses to do it's work.
To resolve the issue, as I look at it (and need I repeat my caveat: I'm no expert at parsing these logs), means either calling (or emailing) Customer Service tomorrow (contact info on the Logos web site), or doing a complete uninstall/reinstall of L4. You could save some time with your reinstall if you follow Dave Hooton's advice on this page: http://wiki.logos.com/Quick_Installation_onto_multiple_computers
EDIT: The last line of the log suggests a memory error. And you could check that too. However, it may report that error if the utility is corrupt (the indexer program can't load the utility). Here's that last line:
2011-02-26 19:28:16.5434 6 Error LogosResourceCore Exception (WER status is 1) identifying resource file at 'C:\Program Files\Libronix DLS\Resources\ABANDON.LSF': Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
At any rate, another thing to check and thus rule out is a memory (RAM) or hard disk error. You may be able to find such testing tools on the web.
I am having the same problem. I have uploaded a zip file with the indexer logs0602.Logos Log Files.zip. When I am able to get Logos to load I am missing lots of my resources :-(
I don't see any problems in the Logos4Indexer.Log Both the crash reports show file access issues. It looks like you don't have a lot of available RAM (less than 2GB), which could be part of the issue, but you do have about 11GB free space on C (which L4 is using for temp file space).
To be more specific, we'd need to see the Logos4.Log file as well.
This also looks to me like something Tech Support would need to resolve, as we don't have the ability to 'look under the hood' on these logs to be certain about much.
Here is a revised zip file that includes the Logos log1145.Logos Log Files.zip
This looks like something else I've seen recently. I'll have to look at that thread and get back to you. But I can't do it right now. Could be a while before I can get back to the forums.
Here is a revised zip file that includes the Logos log
The two crash files are from earlier crashes, not from the same run as the Indexer and Logos Log file are from. I assume neither the Indexer nor Logos is crashing right now.
That said, if you can get into Logos, try hiding the following two resources: SBLGNT and SBLGNTAPP. If you cannot get into Logos, go to your Resources folder and delete the two files. That file should be here: \Logos4\Data\si4drjd0.dgl\ResourceManager\Resources Se if you can restart Logos and see what happens. Zip up the latest log files if you have trouble and send them back to us.
I finally found the thread I was thinking about. The log files showed some similar things. The solution was to uninstall/reinstall Logos4. But it may have been resolved by deleting the metadata and library catalogs. See Mark Barnes post a few posts down for instructions on how to do that.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
