Thanks to Dave Hooton for all the help in the past, but it's still crashing. I deleted the index file and started from scratch. It still gets to a few minutes left and crashes. If I search my library I get no search results.
2350.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2350.Logos4.log:550:0]
0753.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/0753.Logos4.log:550:0]
Latest Crash:
7041.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/7041.Logos4.log:550:0]
2251.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2251.Logos4Indexer.log:550:0]
It occured while I was in Nashville for an Ashley Cleveland concert.
http://www.ashleycleveland.com/
Latest Crash: 7041.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/7041.Logos4.log:550:0] 2251.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2251.Logos4Indexer.log:550:0] It occured while I was in Nashville for an Ashley Cleveland concert. http://www.ashleycleveland.com/
It looks like that crash is happening during Indexing. The error message is:
Program Unhandled exception: System.InvalidOperationException: The two postings (D=1003, T=86, O=853089, W=171340) and (D=1003, T=86, O=853198, W=168194) have conflicting character and word offsets.
This is right after the line:
LibraryIndex Finished indexing resources (in 02:05:44.1660761); writing postings.
So it looks like indexing is finishing and the crash is happening afterwards. This looks very similar to a problem Richard Lyall was having over on this thread, and it turned out his hard disk was failing.
Could you run scandisk and check for errors?
I've run scan disk many times since I installed the program and have never come up with any errors. The computer is only about 3 months old.
I know you're probably tired of hearing wild ideas that might help, but here's another one, inspired by Richard Lyall's issue, together with one I had with my previous computer.
Try turning off 'write caching' to the HDD. This is done through device manager>properties for your HDD. The exact steps are different for each OS.
The reason this might work is that the indexer can max out the data throughput on the HDD device. On my old system, for very intensive operations this would cause failures - probably because the write cache wasn't big enough to hold all the incoming data. My result was corrupt data. Turning this off meant some things took a few more milliseconds to complete, but it was worth it to prevent the data corruption.
When I look at the HDD data tasks in the Win7 Resource monitor during indexing on my machine, the system pegs to 100% from time to time. This suggests that turning write-caching off could help you, if the HDD device is not communicating it's 'full' status in time for the indexing program to see. Having this turned off, should let the indexing program see this directly and buffer those writes itself.
Of course, this is a stab in the dark. But who knows? And it's a pretty cheap solution to try.
I'm going to try it right now. Thanks, I'll let you know what happens.
It made my computer SUPER sloooooooow and then the indexer crashed.
3113.Logos4Indexer.log
Oh well. It was worth a try.
But this should not make your computer super slow, which suggests another potential hardware issue, or device or program conflict (notice I said 'suggests').
Now you turned off HDD write caching, not the Windows virtual memory cache (AKA 'page file'). Right? I would expect really bad performance and program crashes without a paging file.
I unchecked this box and restarted Logos 4 so it would resume indexing:
That's the right one. It shouldn't slow down your system as you described, unless there is a lot more going on than on my system.
Sure wish I could help you out here.
Thanks for trying. As soon as I turned write caching back on everything came back up to speed.
I uninstalled Windowblinds and CursorFX again and I have already removed Bon Jour. I restarted my computer started Logos 4 and it and the indexer crashed immediately. Here are the Log Files. I'm not giving up until we get this figured out. It's been 2 months and five days now.
8461.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/8461.Logos4.log:550:0]
4744.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/4744.Logos4Indexer.log:550:0]
Wow, I can't imagine all of the effort and time you've put into this. Have you considered formatting your hard drive and doing a fresh OS install and then installing Logos first? (forgive my suggestion if you've already done this and I've missed it in this thread). It seems to me that doing this would definitely tell you if your indexer problem is software or hardware related.
I've been thinking about updating from Windows 7 32 bit Home Premium to 64 bit Ultimate...
I tried a merge index once the indexer quit on it's on this time and it just crashed. Logos 4 hasn't yet. Here's the log:
03878.Logos4Indexer.log
Michael, I admire your tenacity.
I would have cleaned the HDD and re-installed the OS + fixes by now!
IF I had a fast internet connection with unlimited downloading I might. I hope it's fixed before I get to 1000 posts.
I'd backup the resource folder and other necessary data first!! Then use the wiki Method 3 (scan) for the reinstall.
Crashed again when I tried to open the program.
6136.Logos4.log
I purchased Windows 7 Professional last night and am installing the 64 bit edition now. Hopefully the next time I post I will not have these problems. It seems I was the only one that had this problem and I truly appreciate everyone's help from the forum and Bradley and Don from Logos.
Michael,
Please keep us informed (install and test L4 to be running OK before installing other apps).
Installed first received the following error message when trying to start.
Description: Stopped workingProblem signature: Problem Event Name: CLR20r3 Problem Signature 01: logos4indexer.exe Problem Signature 02: 4.0.3.2197 Problem Signature 03: 4ae8c809 Problem Signature 04: Libronix.Utility Problem Signature 05: 4.0.3.2197 Problem Signature 06: 4ae8c66e Problem Signature 07: 4db Problem Signature 08: 2d Problem Signature 09: ZBZBEBJ14NSH2JKXAN13UML1DTWCXDQV OS Version: 6.1.7600.2.0.0.256.48 Locale ID: 1033
Michael
I guess that is a MS error dialog. Please attach any L4 log file(s).
How did you install?
5224.Logos4.log
6523.Logos4Indexer.log
Installed from CD then turned off internet and replaced contents of the weird file in appdata with that from a good installation.
The CD(?) has a very old version (4.0? 2197) so you need to install the latest (4.0a 5180) to overcome the error. Further you need to follow a safe method. So uninstall L4 and install using Method 3 at http://wiki.logos.com/Quick_Installation_onto_multiple_computers
Yes, it involves indexing but it will be a better installation.
OK so I should have it scan to the funky file location on my external hard drive? That's what I'm having it do now.
Indexer has already crashed
0363.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/0363.Logos4Indexer.log:550:0]
I can't see any errors in the Indexer log. What message did you see? Was L4 open and is there a logos4.log?
Restart L4 which should start the indexer. If it crashes again wait a minute or so before closing L4.
5700.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/5700.Logos4Indexer.log:550:0]
Indexer is stuck at 3 hours and 12 minutes...
I closed the indexer and the program manually and then restarted. The indexer time is going up instead of down. It is now at 7 hours left.
1348.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1348.Logos4Indexer.log:550:0]
3 hours and 30 minutes...
Now it's up to 4 hours...
5 hours...
6 hours...
7 hours...
It crashed again, still shows no results!!!
4214.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/4214.Logos4Indexer.log:550:0]
I'm trying a rebuild index command now.
Crashed again on rebuild index command....
635636.Logos4Indexer.log
I deleted the libraryindex file, restarted and it is now indexing again. I've been on hold for a half an hour so far waiting for someone from tech support to answer. I have a lot of software I need to install besides Logos 4 so it would be really nice for it to work.
Here's a link to where I got the info:
http://community.logos.com/forums/p/5990/46269.aspx#46269
Crashed again, surprise surprise...
2330.Logos4Indexer.log
Response from Bradley Grainger:
Sorry, I don’t have any additional information at this time. The seemingly-random timing and nature of the crashes makes it extremely difficult to attempt to pinpoint the cause of the bug. In my last email, I speculated on a few possible causes (.NET framework bug, corrupted resource, faulty hardware, Logos 4 bug), but I can’t think of a good way to eliminate these from investigation. (Since you say no other programs have problems, we can probably eliminate hardware. OTOH, this only happens on one of your systems and not the other. I don’t know what that means.)
Some troubleshooting ideas (unfortunately, none of these is very quick):
- compare the resource files on both systems to verify that they’re byte-for-byte identical
- are the resources all the latest versions available from our server?
- turn off automatic update downloads (in Logos 4); delete all resources from Logos4 folder; use “scan” command to bring in 100 resources at a time; does the indexer crash at some specific point? What about scanning them 10-at-a-time?
Bradley
Does this give any of the rest of you all any ideas? Thanks!
[quote]Response from Bradley Grainger:...Since you say no other programs have problems, we can probably eliminate hardware.I'm not sure this is definitely true. The indexer could be using more memory than the the other software. If you have a bad memory chip, then it could work fine until it tries to use the bad portion of memory. Many of your log files don't have errors, but one that was found indicates corruption, which could also be from accessing bad memory:
[quote]System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.I would re-seat* your memory DIMMs in their sockets just to be sure, since you've tried everything else; and if you have two or more DIMMs, try removing one and trying the indexing again.
*i.e., take them out and put them back in to ensure a good connection.
I'll try that Todd and I'm going to upgrade the memory since I now have 64 instead of 32 bit windows.
If you're buying new memory, then I would try the new chips by themselves first (in case you're going to continue to use any of the old memory).
I agree with Todd's analysis because we have ruled out interference from other apps, OS issues, and .NET 3.5 issues (it is pre-installed with Win 7). The logs indicate some sort of corrupion and memory seems most likely:-
2010-01-18 09:18:37.5328 7 Info LibraryIndex Doing a full re-index because the existing index seems to have been corrupted.
2010-01-18 14:22:00.0683 7 Error Program Unhandled exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2010-01-18 14:50:48.2351 7 Info LibraryIndex Doing a full re-index because the existing index seems to have been corrupted.
But I would like to know what you observe when it "crashes". Does it simply stop with no messages?
Regards,
Sometimes there is a message and it asks if I want to debug and sometimes it doesn't. Since I deleted the index file and tried a new index the file only has 117 kb in it. I just deleted the index file again and pasted in the one from the working install. It's about 3.3 GB. When I started Logos 4 and did a search it searched without any message that it was still indexing and had the same results as the working one. It still started indexing anyway and I'm waiting to see what happens. It was at 17 mins. and now 19 mins. I'll see what happens when it finishes or crashes. Why isn't there a way to turn off the indexer? I also pulled out my RAM and reseated it.
You can turn off the indexer by doing a CTRL-SHIFT-ESC and going to the Processes tab and locating the Logos4Indexer process, clicking on it, and pushing the End Process button. It isn't a Logos-supplied function, but it works. Maybe you want to wait to do this??
Thank you. I know how to turn it off that way. I meant how to turn it off period, so it doesn't start up every time I start the program. It works fine until I go to restart it the next time and then the indexer has fouled up the index that was working. When I get updates on the other computer I could index it and paste it to this one until I figure out how to resolve the issue.
I want to thank everyone for their support and prayers. Untilyesterday I don't think I had even prayed about the installation oncethat I can remember. [:(] When the indexer quit running last nightafter I had replaced the libraryindex files from the working computer Icould search with out the message saying that it was still indexing soI decided to upgrade to the latest beta because I saw that it hadimproved indexing abilities. I also had removed my RAM and made sure itwas firmly and correctly seated.
This morning I closed theprogram after the indexing had stopped overnight from the new betafiles and when I restarted it the indexer did not start up so I did asearch and no message that it may not be correct because it was stillindexing! I'll re-post in a few days if it's still going smoothly.
Thanks again to everyone for your help (Logos and Forum) and even more so your PRAYERS.
Istart back to school this morning at a Tech school (at the age of 46)to get a diploma in CIT and I hope what I've learned here will help methere. My job was eliminated last May and because I live 50-75 milesfrom Knoxville and Chattanooga I have not been able to find a job evenwith a good resume and a Bachelor's degree. The state is paying for allof my school and continuing unemployment and COBRA for me until Igraduate or am hired. Thankfully my wife is an RN and has been blessedwith a good job and of course the Lord Himself is the one who hasblessed me and watched over me as I'm sure He does for many of you.
Psalm 40:16-17Let all those who seek You rejoice and be glad in You; let such as loveYour salvation say continually, “The Lord be magnified!” But I am poor and needy; yet the Lord thinks upon me. You are my help and my deliverer; do not delay, O my God.
