Indexing Crashes
4.0a installed automatically - no problem. However, indexing is another kettle of fish. Indexer keeps crashing. I've tried restarting, rebooting but still indexer won't work and now I can't get L4 to run without crashing and wanting to send a report which never gets past the compiling stage. Suggestions please.
Every blessing
Alan Macgregor
(Banff, Scotland)
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
Comments
-
Welcome to the forums Alan! Can you tell us a bit more about your setup? Here's a few questions:
1. Which version of Windows you are running?
2. It is probably implied in your message, but were you doing an upgrade from another version?
3. If not, have you got past the download and preparing your library stage?
I visited Banff years ago. Do you guys have snow up there right now? We do! (just north of London).
0 -
I'm also having problems indexing with 4.0a. I had to reinstall from scratch yesterday, and since then, indexing has not completed. Third attempt currently under way.
P.S. I know Banff fairly well - I have an elderly aunt who lives in Findochty
0 -
I had the same problems, but in my case it was solved with:
- Letting the indexer run a few times (it seemed to pick up from where it left off).
- Loading Logos with a blank workspace.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Alan Macgregor said:
4.0a installed automatically - no problem. However, indexing is another kettle of fish. Indexer keeps crashing. I've tried restarting, rebooting but still indexer won't work and now I can't get L4 to run without crashing and wanting to send a report which never gets past the compiling stage. Suggestions please.
If you can produce some logs that would be very useful - http://www.logos.com/support/article/2135
Elect to open with a Blank Layout (point 4).
Dave
===Windows 11 & Android 13
0 -
Mark
FYI Running XP SP3, no screensaver, full power, everything "always on" (ie HDD always on, Display always on, etc)
- Launched L4
- Cancelled auto-index.
- Cancelled auto-homepage
- Command line: Rebuild Index
- Indexer crashed after 23 minutes, showing 8 hrs to index (I have L4 Gold plus a lot of extras, as I've been a Logos user since 1.6 in 1993/4)
- L4 hasn't crashed though.
Anyone any further suggestions.
Every blessing
Alan Macgregor
BTW Snow has all gone here. Nice day for the time of year up on the Moray Riviera.
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan,
Exit L4 and the indexer, then follow Dave's link to turn in logging - but make sure you run the javascript files to do so (at the bottom of that page).
Then load Logos to start the indexing again. After the crash, you'll have folder in My Documents called "Logos Log Files". Upload the indexer log here for us.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Failed again.
Here is the info you asked for.
Every blessing
Alan
Computer: Lenovo ThinkCentre Intel Pentium Dual CPU E2180 @2.00 GHz
2.00 GHz, 1GB of RAM
Physical Address Extension
MS Windows XP Professional Version 2002 Service Pack 3
5125.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/5125.Logos4Indexer.log:550:0]
73014.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/73014.Logos4.log:550:0]
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan,
You're getting the following error in your indexing:
Unhandled exception: System.Data.SQLite.SQLiteException: Some kind of disk I/O error occurred disk I/O error
Can I suggest you run scandisk (possibly with "scan for bad sectors" turned on). Then try Logos again.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Also, 1 book took 18 hours to index which suggests it may be corrupted/ in a bad sector. When scanning has finished delete LOUWNIDA.logos4 (Louw-Nida Lexicon) from C:\Documents and Settings\Alan Macgregor\Local Settings\Application Data\Logos4\Data\fqvew1f5.cep\ResourceManager\Resources (it may be necessary to use Explorer so you can view Hidden files and folders). When you start L4 it should be downloaded and indexing will start.
Dave
===Windows 11 & Android 13
0 -
Thanks, Mark and Dave. I'm currently running CHKDSK /r as Scandisk is no longer available in Win XP. When that finishes I shall delete LOUWNIDA.logos4 as suggested then take it from there! I'll keep you posted on progress.
Every blessing,
Alan
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Ran CHKDSK /r and there were no errors. Deleted LOUWNIDA.logos4. Restarted computer. Ran Logos 4. It didn't load LOUWNIDA, becuase the Indexer crashed again. Sorry no log, but I did write down the error message.
Application has generated an exception that could not be handled. Process ID= 0xa24 (2596), Thread ID=0x12dc (4828)
I really haven't the time to debug much more. If the next try doesn't work, it's back to Logos 3 for a year, when I hope the bugs should be fixed!
Every blessing
Alan
[:(]
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
If there's no disk corruption, the problem is probably caused by file corruption, perhaps during the download process. Your Louw-Nida lexicon took 18 hours to index, and the error I referred to above occurred just after it started indexing, so that could be it. Try deleting that file: LOUWNIDA.logos4
If you are able to attach your indexing logs, that definitely helps.
If you've had enough, can I suggest uninstalling Logos, then ordering the DVD and installing from there? That should resolve any errors due to download file corruption.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark
I did delete the LOUWNIDA.logos4 file, as I noted in my previous post.
I have the DVD. I presume that I can just stick it in and it will find the proper file, just like Logos 3, without having to uninstall and reinstall.
Every blessing
Alan
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan,
Sorry I missed the fact that you'd deleted Louw-Nida. I'm suggesting you uninstall/reinstall Logos4 because that will delete your indexes, and resources, which are what appears to be causing the problem. You can't just "stick the DVD in" - that's not how Logos4 works, and even if it did, that wouldn't solve the problem. I can't guarantee and uninstall/reinstall will work, but there's a good chance it will.
Mark
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
