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]
Michael, you definitely deserve some sort of award for persistence.
When I have had indexer problems they have always been solved by reloading all my resources (as I've never been able to figure out which one was causing the problem). I ordered the Logos 4 DVD resource and used it for that purpose just this past week and got my Beta installation working at long last. Logos needs to work on this issue, especially figuring out how to report what the indexer is choking on.
Have you tried reloading all your resources? BTW: I did that once by deleting the Resource folder and letting Logos 4 do the big download, but I still had trouble. I think the fix may be getting and using the DVD to be sure you have every bit in every resource you are supposed to have.
Mark, I've downloaded everything, uninstalled, used the DVD, uninstalled, and transferred from an older laptop that has a working setup. Same problem each time. I've tried each install at least twice. I use AVG and turn it off when indexing. I have plenty of RAM and 122 GB of free space, all windows updates, SR7...
I don't know what other checking you've done, but it seems that at least some further checking should be done. Have you run a check on your RAM and your hard drive? Also, what anti-virus software are you using?
How can I download the beta and try it?
I don't really think that you would have missed this, but is there enough disk space? Have you recently run windows upgrade (particularly upgraded the .NET framework)? Are you running as administrator on the machine?
I got L4 to run an a netbook with a N278 ATOM processor, VP SP3, and 2GB ram so you have enough otherwise.
http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe
Robert, I am not running as Administrator and wasn't on my other machine. I have plenty of hard drive space and I have all my windows up to date. Mark, When I try to download the beta I receive the following error message:
I can't read that on my computer. What does it say?
I actually took a chance on that one so it may be an out of date link, however when I launch it it tells me my Beta installation is up-to-date.
I take that back. I can see it. No idea why that is happening but I'll bet it is part of the rest of your problem.
Try emptying your cache and your download folder and try again. I wonder if you are getting corrupted files as you download.
I've emptied my cache. I also get the following error message:
That is different but not much help as I am not a programmer and don't know anything about C++.
I would normally dump the cache and file and reboot and try again. Or I'd give up. However that latter choice would later bother me and I'd try again at that point.
If you are in the US, then i would really suggest that you contact Tech support. After loading L4 i had problems with L3 updates. If you can get to the 2nd level Tech support, they can get on your machine remotely and see what is happening. It took 2 hours (watching them move things around on my machine) but they got it all working. I was impressed.
Steve, I have been in contact with Level 2 support for over a month. I forward every error log to them as well. The development team has looked at them and I guess they still don't know what is happening. It's been a week since I last heard from level 2 support on this one.
I'm not sure what this is about, but notice the differences in the file sizes given in the two different locations.
I deleted that and cleared my cache and then tried downloading the file from IE instead of firefox and got the same error messages.
Wow
You are the most patient person i have ever met! (really)
Wish i knew enough to help you, the people here on the forum have been helpful. Please don't give up. [Father please lead one of your servant to assist Michael to resolve this problem. Thank You Lord in advance!]
Did you get a log file of this crash? If so upload it or send it on to the folks at Logos tech support. It is pointing to an underlying problem that someone with more experience than you and I would have to diagnose. My suspicion is that it is something in the underlying operating system and not directly in Logos that is causing the problem.
I haven't tried, but I believe you can try to repair your Windows installation without reloading it completely. Insert the installation disc and I believe it will give you that option. I'd want to check online about that before trying, though. Maybe you have a corrupt file or even a .dll somewhere that Logos is accessing and nothing else is.
I typed the error message into Google and got a lot of hits. Unfortunately none of them specifically apply. However the gist was that sometimes there is an out-of-date file or driver on your computer and sometimes the original program was not compiled correctly. I can only scratch my head and hope that a programmer at Logos can help.
Thanks for all of your efforts. I do appreciate it.
Mike
This one looks like there are several things going on. Such problems do get hard to find. Logos$setup(2).exe is not a valid executable probably means it was corrupted during download.
At a guess, one of the system libraries on your machine is either corrupted or out of date compared to those used by LOGOS. This situation often happens if you install or maintain a compiler (like Visual Studio) on your computer (particularly if it is on older version or not MS). Other applications can also put in newer, older, or just modified libraries but few would bother because of compatibility issues. Since the problem occurs on two different machines you might need to look for a common program that might have changed your system libraries. And don't forget the possibility of an undetected virus or rootkit. One common cause of problems is older devices (my system has problems with a Sonus FIrebox from years ago on the firewire bus) whose drivers don't work right anymore because the manufacturer never updated them.
Michael
Can you give a little history of what happened since you had two working systems (and identify older laptop). We need the logos4Indexer.log files (zipped) as well.
Dave, I have never had two working systems, only the one that is listed in an earlier post in this thread. The Vista machine. Don Everett told me that they thought the Merriam Webster Dictionary 10th edition file may be corrupt so now I've deleted it and tried to start a fresh index, but Logos 4 keeps crashing. I have sent Don probably 10 e-mails since yesterday. I don't have time to keep messing with this, I have spent countless hours messing with it. It is by far the buggiest software I've ever seen in my life. I've had Logos since 1.6 and have loved Logos since. I don't want a refund, I want this software to work. I just don't understand what it is going to take to get Logos to come up with a solution. You would think that after a month and a half there would be an answer or some help above Level 2 whatever that is. I sold this software through bookstores for 10 years and would be embarrassed to try to sell it now, it has been and still is a HUGE headache. Maybe that is why it is not being offered in stores.
4341.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/4341.Logos4.log:550:0]
6153.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/6153.Logos4Indexer.log:550:0]
Michael, I understand your complete frustration. It would seem that since you are not having any other problems with software on your computer that the problem must be with Logos. However, the fact that we are not hearing from lots of other people with your problem may point back to your specific computer and installation. In other words if Logos was a buggy as you say then the very problems you are having should be occurring with lots of other people. If they are we have not heard so. Problems, yes. But intractable problems? Rare.
So while that is no comfort to you on the one computer you own, Logos does work for you on one machine and it is working on probably thousands of other machines as well. It isn't working on one of your computers. We can't conclude that your machine might have something wrong with it because you are not reporting other problems, but it is still a possibility. It might be one component other programs are not accessing. Because of this it may be next to impossible for Logos to solve the problem. They might not be able to tell from the error reports exactly what is wrong.
There is one other suggestion I can make if you want to try it and haven't done so already. Create a second user account on your machine and try to load Logos 4 from the DVD while logged into that account. Keep the account simple. Don't load a bunch of other software except your internet browser. That might further isolate your Logos installation from other software that may be creating a conflict. If it works it might tell us something and point us to further solutions.
Mark,
I'm not into discussing how many people have problems. There is no way to know this and it doesn't really matter to me at least. I have done everything tech support has suggested and nothing has worked. I'm not going to do the second install because I have neither the time nor know-how to do it. We have no idea how many people have asked for refunds or seen all of the problems on the forums and decided not to buy. I just want the software to work and it should work fine if the machine that is advertised by Logos as having the capability to handle the software is used. My other computer has the bare minimum, it is for my home school children to use, which btw they use 3.0 and this one has everything recommended and more.
4341.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/4341.Logos4.log:550:0] 6153.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/6153.Logos4Indexer.log:550:0]
I did get to look at your logs (copy/paste into browser address bar and delete ":550:0" then open to notepad).
The Logos4 log shows only three errors:
But each time the installation seems to proceed normally. The log file ends without any apparent reason after reporting info at 11:56:45.
The Indexer log shows no errors and appears to be proceeding normally until 12:01:14 this morning.
This would suggest either a manual termination, or an termination by some other program or Windows service. The following questions are my attempt to look for potential software conflicts that may be causing the problem. If we can rule these out, we could look in some other places:
First, let's rule out running any Nokia software on this system (Nokia software is known to cause prob's with L4).
Next, your screen shots look like a non-standard Win7 screen - at least the colors and buttons very different from mine. Are you running any thing special as an overlay for Win7?
Next, what other software do you have running in the background. One of your screen shots showed L3 running in the background. What else is running (include programs and background tasks)?
Which version of .NET is installed (if you don't know try this program to check for you: http://download.cnet.com/Dot-Net-Check/3000-10250_4-10867483.html -- CNet is a known safe download site.)
Next, are you running Visual Studio? If so, which version?
Which anti-virus program are you using
Thanks Richard,
No Nokia software.
I use Windowblinds software on both computers. It hasn't affected the other one or anyone else that uses it as far as I know. If you change the "blind" it will cause Logos 4 to crash this is a known issue. http://community.logos.com/forums/p/4969/39033.aspx#39033
Below are the processes that are running.
I don't know what Visual Studio is so I assume not. I use AVG free for my antivirus. I'm running Dot Net 3.5.
I use Windowblinds software on both computers. It hasn't affected the other one or anyone else that uses it as far as I know. If you change the "blind" it will cause Logos 4 to crash this is a known issue. http://community.logos.com/forums/p/4969/39033.aspx#39033 Below are the processes that are running.
This is from the Win7 machine that's giving you the problems, right?
I notice WBVista on that list. I assume that's Windows Blinds for Vista. (Can you confirm that WBVista is guaranteed to work for all Win7 apps?)
Let's see if we can eliminate WB as a potential issue (since WPF is so graphically intensive, it seems necessary to eliminate it as a potential problem).
Can you temporarily disable WB, and restart Win7 clean?
Will L4 run without WB running?
[If it still doesn't the only way to definitively eliminate WB would be to completely uninstall it from your Win7 machine. I hate to suggest that, but if you are willing to give it a try, would could eliminate WB and move on to other potential problems.]
It just crashed again after I clicked my Bible reading for the day. Below is the log file. I've left the indexer running.
1538.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1538.Logos4.log:550:0]
It just crashed again after I clicked my Bible reading for the day. Below is the log file. I've left the indexer running. 1538.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1538.Logos4.log]
1538.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1538.Logos4.log]
Same errors as before (see previous post). We still need to eliminate WB as a cause.
I did as you suggested, turned off Windowblinds and restarted. Although it still is called Vista it has been update for Windows 7. When I restarted the indexer started and then crashed on it's own after I started Logos 4 and canceled updates. Logos 4 is still working so I will try to use it for a while and see what happens.
2211.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2211.Logos4Indexer.log:550:0]
I did as you suggested, turned off Windowblinds and restarted. Although it still is called Vista it has been update for Windows 7. When I restarted the indexer started and then crashed on it's own after I started Logos 4 and canceled updates. Logos 4 is still working so I will try to use it for a while and see what happens. 2211.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2211.Logos4Indexer.log:550:0]
The indexer shows this happening:
How much free space do you have on C:\ on this machine (rule out 'ran out of storage space)?
According to the log, though, the indexer did finish downloading something (3.1 MB) in size, and then exited normally.
How is L4 running without WB?
Just slightly off-topic. Windowblinds users reporting trouble:
Itoo updated WindowBlinds to 7 on my Windows 7,and been having manyproblems with it since. Since updating, I’ve had most of the appsinstalled on this machine crashing either when opening them or whentrying to use them. When, I uninstalled WindowBlinds and that seems tohave corrected the problem.
1. When I installed WindowBlinds 7, it took a long time to install. The information says "installing" but it never finish.
2. When I cancel installation, it is installed, but not correctly.
3. When follow the suggestion to update, the installation take too long.
4. Once, my computer crash, because I try to use a new skin.
Please help.
Thanks
121GB of free space. It just crashed again when I looked at a few passages and hit the back arrow to go back to a previous passage. It does this pretty often. The same problems I was experiencing before I turned off Windowblinds.
What crashed L4 or the L4 indexer? (I'm assuming the former.)
Unfortunately, the only way to rule out WB, is to completely uninstall it. The reason being that some programs (like Windows Blinds) replace windows components, and even when they are not active, the replaced components are still present. If you decide to uninstall, be sure to follow all instructions from Windows Blinds about how to completely uninstall their program.
If you are wiling and able to do this, we could rule out WB completely and begin to consider some other things.
Hi Michael,
I've reviewed every log file that you've posted on this thread, but unfortunately none of them log any error information. While sometimes that means that a crash isn't happening, or it's the wrong log file, it can also mean that the crash is severe and is bypassing our normal error reporting mechanisms.
Please attach a screenshot of the "Logos 4 has crashed" dialog that appears. If there is a link to show more details, please click those links and capture as much information as possible in the screenshot.
Thanks,Bradley
Do you have CursorFX and WindowBlinds installed on both computers?
What is the make and model of the video card in each computer? Have you updated the crashing computer to the latest video drivers?
Don Everett has several files I have sent to him as well. I have CursorFX and Windowblinds 7 fully updated on both computers. Nvidia GeForce 8200M G on the Windows 7. I just updated the driver and haven't had any blue screens of death since. I believe the date on the update was 12-4-2009. The older computer has a Mobile Intel (R) 945 Express Chipset. All windows updates are installed.
After these two screens Logos stays grayed out until I close it in Task Manager.
8836.Logos4.log
0486.Logos4Indexer.log
I have no idea why the last post came up several times. I only sent it once.
It's a little strange to me that the "stopped working" dialog has a "Debug" button; that usually only appears if a debugger is installed, which is not typically the case. Unfortunately, it's preventing any useful information being shown in that dialog.
There is a Microsoft tool named ADPlus (http://support.microsoft.com/kb/286350) that could collect the information we need to understand this problem; if I gave instructions on how to run it, would you be willing to spend the time (probably 10-15 minutes) to set it up and run it?
YES!
Does it work on Windows 7? I couldn't tell from the Microsoft site.
Brad,
I hope you can help Michael. I've got to be AFK for a while and hate to see this get dropped.
Thanks!
(BTW, I still suspect WB &/or CursorFX, but I'm sure you know more about it that I ever would.)
Great! [:)]
I just created a wiki page on this: http://wiki.logos.com/Creating_a_Crash_Dump_with_ADPlus
I tested out the instructions on a 32-bit Vista computer (and they worked); I think that enough should be similar on 64-bit Windows 7 that the instructions will work there, too. If you encounter errors, please let me know and I'll correct the problems.
The file that it creates may be too large to email (to me: bgrainger@ you know where); a site like MegaUpload could be used to store the file. (I don't think Logos has an anonymous FTP that you could use for this purpose).
I'm leaving work soon, but I'll check this thread again tomorrow morning. Thanks for helping us diagnose this problem.
I'm on it. Thanks Bradley!
What do I do once I get here? If you don't see this tonight, I won't be around until after 5:00 ET tomorrow night. Thanks again.
