Indexing problem after installing Portfolio

After downloading and installing portfolio I keep getting the following message.
Logos Bible Software 4 Indexer has encountered a problem and needs to close. We are sorry for the inconvenience.
I have been running Platinum since Logos 4 first came out. I have not encountered this type of problem before. The indexing can be slow sometimes but it always completes without a problem.
I am running an older machine Windows XP-Sp-3. AMD pc 3200 with 2 gigs of memory.
It is a little slower than my laptop which has windows 7 installed on an intel 6500 core duo processor with 4 gigs of ram. Yet up untill now it has been adequate in running the program.
I have 88 gigs remaining on the hard drive so that isn't the problem.
I installed Tyndale commentaries earlier this week with no problems. I also downloaded a 1.05 gig update this week with no problems indexing.
Last night I installed Portfolio which was a 958 meg download. It hasn't completed the indexing since Portfolio was installed.
It seems to always index down to 3hrs and 30 min. before giving the error message.
I can still run the program and perform searches but the indexing is not complete.
Any help I can get is appreciated.
Comments
-
Your first step would be to turn on Logging ( http://wiki.logos.com/Diagnostic_Logging ) and then in the program issue the command "rebuild index" in the command line. You will probably want to do this before you go to bed so it can index overnight (remember to adjust your power settings so the computer doesn't decide to go to sleep on you). If the indexer stops working again then post the Diagnostic logs and someone will be able to tell you what the next step will be.
Prov. 15:23
0 -
I'm still getting the same error message.
Here are the attached log file and log indexer file.3060.Logos4.log
0 -
Did you try the Rebuild Index command and these are the log files?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Yes
0 -
The log file shows an error in the midst of merging two index files, which is why I asked. I thought the rebuild command started from scratch and ignored the partial index files created when you install new resources or Logos downloads updated resources.
At any rate, there is no information in the Log file that is helpful to me to understand what is wrong. It looks like it will take someone from Logos to figure this one out.
Just for interest sake, can you compare the screen capture below of my index folder (yours is probably at C:\Users\{your name}\AppData\Local\Logos4\Data\{random string}\LibraryIndex) with yours? Do you have the same number of files with the same names? Do you have or not have the supplemental files?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I had six additional files. The file size of each was zero. I've deleted the files.
I restarted logos and of course the indexer started. I stopped the indexing process and entered the command to rebuild the index. Let's see what happens.
I forgot to mention in my first post one other strange behavior. I restarted the computer to see if that would help solve the problem.
The indexer started indexing in the start up tray without me starting up logos 4.
0 -
williamnorman said:
I had six additional files. The file size of each was zero. I've deleted the files.
I restarted logos and of course the indexer started. I stopped the indexing process and entered the command to rebuild the index. Let's see what happens.
I forgot to mention in my first post one other strange behavior. I restarted the computer to see if that would help solve the problem.
The indexer started indexing in the start up tray without me starting up logos 4.
Did you delete all the files or just the zero sized files? I hope this latest index attempt works for you!
The indexer starting after a restart is not an unusual behavior, I believe this is by design.
Prov. 15:23
0 -
williamnorman said:
The indexer started indexing in the start up tray without me starting up logos 4.
It will do that if it didn't complete the indexing before you closed Logos. Annoying if you get into this loop of crash, restart indexing, crash, etc.
If Rebuild Index crashes again, zip the Indexer file up again and post it. The work around may be to delete the entire contents of the LibraryIndex folder and restart Logos which will relaunch indexing.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Indexing is completed.
Kevin and Mark
Thank you for pointing me in the right direction.
0 -
Glad the troubles are behind you for now. God bless.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -