Windows 7
Have tried "repair"
Have tried"bitsadmin" (no success)
Have tried turning off Virus checker
Have even re-formatted HD and re-installed Windows (Logos4 indexer worked for a couple of weeks after).
Only thing that seems to work is re-install--
Indexer failure rarely results in any error logs: ie.
3223.dec 3 Logos4.zip
0564.Dec 3 Logos4Indexer.zip
0003.indexer failure.txt
These files were supposed to help:
8267.WER8DEA.tmp.zip
8473.WER73B5.tmp.WERInternalMetadata.zip
The last time it did give some error logs
1376.Logos4.zip
3326.Logos4Indexer.zip
7142.Logos4IndexerCrash.zip
2678.Logos4IndexerError.zip
I' not going to re-format again.
I did that because Logos techs suggested my User accounts had "issues."
Well this time as well as an Admin & Guest I also put on two other Stadard Users: L4Beta and 4Logos.
As it is the L4Beta User side that is not working properly, so Tech support does not really want to talk to me.
[Is there even a beta right now? ...Don't think so, so it wpould be 4.6a SR-4.
Thanks
ps this is the continual Indexer crash message:
Logos Bible Software4Indexer has stopped working
Windows can check ... etc
Check on-line...etc
Close program...etc
Details:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos4indexer.exe
Problem Signature 02: 4.61.0.3380
Problem Signature 03: 50b553bd
Problem Signature 04: System.Drawing
Problem Signature 05: 2.0.0.0
Problem Signature 06: 4f9267f5
Problem Signature 07: 7b0
Problem Signature 08: ffffffff
Problem Signature 09: System.ArgumentException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
As soon as one clicks anywhere on this message the Indexer disappears out of the Program Manager list of Processes
[This has been going on since April. Logos tech staff took extensive control of computer and could not really help.
[Advised to Scan empty folder ie re-down loading many, many G's of REsources each time--plus their suspicion about my Windows User Accounts - but they have all been re-installed).
As the other User account with a "safe" Logos 4 installation using: "Update Channel: default/stable" etc, [and NO to internet] seems to consistently work, I feel that this is a Logos issue? The frustrating thing is that every time this is "fixed" -- the account that I then choose to mainly work from is the one in which Logos 4 always gets "wrecked."
Thanks
[This does not give a lot of motivation here to pay money to upgrade/cross-grade to L5--this 4.6a version of Logos was to have been "the" stable one].