Problem with endless repetition of 2 downloads and version (in about Logos) not being updated
I recently got a new computer and reloaded Logos 4 - from a new disk with Ver 4.1 (4.10.4.5179). After about 3 downloads it started repeating the same download over and over again. On Forums I found you must delete two .db files in the L4 Data file ie download manager and update manager. Great - it did a different download. Then it did a second one which it decided to repeat again. I therefore deleted the two files mentioned above and it went back to download the first of those two downloads (or updates -= whichever you prefer) and now it is doing the second one again. I also not that since I loaded off the DVD the version of Logos that I have - found in Help / About Logos - has never changed. One last item found in the forums was a link to enable a logging function so you can be sent log files. That link takes you to a page that says I have been denied access. I am running on Win 7 64 bit if that helps complicate matters anymore. My old computer was Win 7 32 bit. Can anyone tell me what to do to stop going in circles. Thanks.
Comments
-
Wow Alan it sure looks like you've done your homework!
I can't determine why you've been denied access to the logging information but I'll post the information from http://wiki.logos.com/Diagnostic_Logging here.
[quote]
How do I get a diagnostic Log?
To turn on logging, hold down the CTRL key as you start Logos 4; this will turn on logging for that session. (It will also permit you to open to a blank layout) Log files are written to
(My) Documents\Logos Log Files
If this is not clear or working, watch this video http://vimeo.com/8230899 or see Starting from desktop.Holding down Ctrl doesn’t work, or I want logging to stay on permanently.
To permanently turn logging on, run this Java script (by double-clicking on it): EnableLogging.js.
It should display a dialog box saying “Logos 4 logging has been enabled”.To turn it off, run (double-click) DisableLogging.js.
If you tried to use the Java script, but that file opens in an editor/just shows you text.
Download the script file by right-clicking on its title above, choose “Save Link As...” or “Save Target As...” and Save it in
(My) Documents\Logos Log Files(create folder if necessary).
Double-click EnableLogging.js to turn logging on and double-click DisableLogging.js to turn logging off.I can’t run JavaScript. What’s that script really doing, anyway?
To enable logging
Copy the following three lines into Notepad:-
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Logos4\Logging]
"Enabled"=dword:00000001Save as “EnableLogging.reg”
Note that Notepad will probably append “.txt” to that name, so you’ll have to rename the file again as just EnableLogging.reg from within Windows Explorer. To do this, right-click on it and select Rename.
Double click on that newly saved file, accept the change, and logging will be enabled.To disable logging
Copy the following three lines into Notepad:-
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Logos4\Logging]
"Enabled"=dword:00000000Save as “DisableLogging.reg”
Note that Notepad will probably append “.txt” to that name, so you’ll have to rename the file again as just DisableLogging.reg from within Windows Explorer. To do this, right-click on it and select Rename.
Double click on that newly saved file, accept the change, and logging will be disabled.What do I do with them?
These logs can then be used to File a proper Bug Report either by emailing them to technical support or see Uploading Logs to learn how to upload them to the forums.
Note that the logs are overwritten each time you start L4, so it’s best to rename or capture the logs before you start L4 again. It also helps to compress (zip) the log files before you upload them as they can be very large.We'll try to take a look at the log files and determine what is causing the hitch.
Sarcasm is my love language. Obviously I love you. 0 -
Thanks. I hope I have done this right. Here are two log files that came up last time I booted as suggested above.
1007.Logos4Indexer.zip4621.Logos4.zip
It looks like I have an indexer problem on one. Yesterday I took some advice from a forum and deleted the one index file and it solved one problem but this other post above post dates that.
Thanks, Alan
0 -
There were two logs when I posted but this one went AWOL.
0 -
Alan G Heathcote said:
from a new disk with Ver 4.1 (4.10.4.5179).
Looking at Release Notes => http://wiki.logos.com/Logos_4_Release_Notes noticed version 4.10.4.5179 is bit old.
Wonder about downloading and installing current stable release => http://www.logos.com/windows/installlogos4 (may not need to delete database files)
Keep Smiling [:)]
0 -
Thanks for the Logs, Dave Hooton is better at reading these than I am I'm curious if there's a need to manually delete the udpatemanager.db or the downloadmanager.db (or both).
But for the immediate moment while waiting on confirmation of that, I agree with KS4J you need to update your program. I'm assuming that internet updates are turned off?
I believe either way you can force an update by typing update now in the commandbar to initiate a program update to get you to the latest version of L4. There have been lots of bug fixes (and maybe this one) since 4.1, version 4.10.4.5179 (Currently: v4.20.4.8828)
Else you could just run this to update manually: http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
Thanks for the Logs, Dave Hooton is better at reading these than I am I'm curious if there's a need to manually delete the udpatemanager.db or the downloadmanager.db (or both).
Neither of the logs had errors; just showing that one 51 MB download was cancelled.
Thomas Black said:But for the immediate moment while waiting on confirmation of that, I agree with KS4J you need to update your program. I'm assuming that internet updates are turned off?
Manually update L4 as per the links and enable permanent logging before starting L4.
I suggest you let a future download complete its course and then save the logs (by renaming). Upload logs if it crashes or repeats (hover over the Logos4 icon in the Windows taskbar to see the size).
Dave
===Windows 11 & Android 13
0 -
Thanks to all of you who have tried to help. As always with distance help there are things I can see or things that I know which you can't see or don't know. I will try to go through some as it might help the analysis. In no particular order.
1. I am connected to the internet on L4 at all times. My other computer is right up to date - but I am never connected to the internet using L4 on both at the same time.
2 Finding out the size of active downloads by hovering mouse is understood - that is how I picked up that the same download was repeating all the time. In other words, it would download and then do its thing. I would close L4 and then restart it and lo and behold it would start that exact same download again. That is when I deleted the .db files mentioned above and it went back to a previous download and then the same old 51MB one which it just kept downloading. Hence in the log I cancelled that download.
3. On the log files attached above I notice that the Indexer log came 3 minutes before the Logos4 one. Therefore I conclude my first problem may be in the index.
4. When I originally loaded on this computer, I used my DVD for a year ago with ver 4.0 on it. That routinely crashed about 2 minutes after opening. I then called the local Logos office and asked them to send me the latest DVD they had - which is Ver 4.1 mentioned right at the top. I installed that and the 2 minutes in crash problem was resolved. About 3 updates later we went into the constant repetition on the same download. THen I deleted the two .db files and it progressed - only to spin again 2 downloads later.
5 When I first installed the 4.0, there was a version of McCaffey (sp?) on the computer but I had not activated it but it was doing update downloads. I installed 4.0. Later installed OVER 4.0 (which I am now wondering at the wisdom of doing) 4.1. At some stage after that I put my normal antivirus program on the computer (ISA or F-Prot) and then uninstalled McCaffey. Today on one forum I read about Antivirus problems so went into F-Prot and saw that it allowed 3 L4 exe files to operate, one of them being the Indexer exe applic.
6. As suggested I downloaded the Logos4Setup.exe which two of you suggested. When I clicked on the file to open it, and error message came up "Location of the file in downloads ...Logos4Setup.exe is not a valid Win 32 application". My first thought is that I am running on Win 7 64 bit so why are you crying about 32? But you know how arguments with MS products go. So that is a mystery to me which maybe one of you can suggest a solution to.
So that is some more background. I am seriously wondering if an uninstall and reinstall off the 4.1 DVD wouldn't be the wisest solution, unless I can find how to use that downloaded Setup.exe file - with the antivirus program disabled for the duration of installation.
Right now you are all asleep and I have a meeting so when day comes to your side of the world maybe you can come back to me. I am 10 hours ahead of WA - in South Africa. Once again, thanks for your time and help - it is greatly appreciated. When we solve this one we can put a summary page at the end so others can learn in one page from the solution and wisdom contained herein.
0 -
Alan G Heathcote said:
Right now you are all asleep and I have a meeting so when day comes to your side of the world maybe you can come back to me. I am 10 hours ahead of WA - in South Africa. Once again, thanks for your time and help - it is greatly appreciated. When we solve this one we can put a summary page at the end so others can learn in one page from the solution and wisdom contained herein.
The beauty of the online support forums is that Logos power users are spread out all over the world, so chances are there's always someone awake when you're posting questions. We who have the orange star badges (MVPs) are not Logos employees, just extra eager users who like answering questions.
"Logos4Setup.exe is not a valid Win 32 application" sounds like it is due to a corrupt download. Try downloading the file again and try running it again.
If that doesn't work, there are some other possible solutions to that error message listed here: http://en.kioskea.net/faq/1591-exe-is-not-a-valid-win32-application. Some suggestions are irrelevant to your situation, but I'd try sfc /scannow. There's more information on how to do this here.
0 -
Rosie Perera said:
"Logos4Setup.exe is not a valid Win 32 application" sounds like it is due to a corrupt download.
If the .exe file was corrupted, it's possible your other downloads are being corrupted too - that would explain repeated downloads.
However, I'd strongly recommend you get the .exe downloaded and installed before attempting other troubleshooting. There's not much point spending time working out a problem when it may have already been fixed.
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 Barnes said:Rosie Perera said:
"Logos4Setup.exe is not a valid Win 32 application" sounds like it is due to a corrupt download.
If the .exe file was corrupted, it's possible your other downloads are being corrupted too - that would explain repeated downloads.
However, I'd strongly recommend you get the .exe downloaded and installed before attempting other troubleshooting. There's not much point spending time working out a problem when it may have already been fixed.
Once Logos 4 is installed, can use scan command to copy resources from DVD - then only need to download updates.
Wiki has scan installation - Method 3 could be helpful => http://wiki.logos.com/Quick_Installation_onto_multiple_computers
Alan G Heathcote said:My first thought is that I am running on Win 7 64 bit so why are you crying about 32?
Currently, Logos 4 is a 32 bit application that installs in c:\Users\<userid>\AppData\Local\Logos4 on Windows 7 (including 64 bit versions).
0 -
Just to echo by shear volume: redownload the corrupted installer until you get a clean copy. If you'd like, send me an email at tcblack with a gmail extension and I'll download and zip up the installer and send it to you.
Sarcasm is my love language. Obviously I love you. 0 -
Thank you to all of you for your help. Bottom line problem is solved. But here he how we got there:
I downloaded that Logos4Setup.exe about 8 times and it gave the error every time. Even tried doing it on another computer and copying it across to this on a flash drive. Same error.
Rosie had given a bunch of suggestions and I went through each of them that seemed applicable - doing the scannow item first - of course it found no errors. Antivirus check, and so on and so on that was in that list she gave me and nothing solved it.
Then I tried the Keep Smiling for Jesus Wiki link about the multiple computers. That might have been suggested by someone else earlier but for whatever reason I didn't try it then - but I had seen it. Anyway when you click that link, you get the 3 method approach. I was a bit tired after a really long and "exciting" meeting so the words on the page were not getting through too well. But I kept seeing comments about backing it up to and external HD. Suddenly a little light came on in my head. My other computer has the absolute uptodate version of L4 and I backed it up last weekend onto the external before playing with installation on the new computer. So the light comes on, all these corrupt files that you can't seem to download and which are at a ver 4.1 level, are already on your external HD at a 4.2 SR2 level and one of them is the setup.exe file. I was about to click that to run setup when the penny really dropped - just copy User/My Name/Appdata/Local/Logos 4's contents from the external HD and overwrite what is on the new computer C. Over 15 GIG of copying so it took a while. Then in Data you have a random file name and then a ton of subdirectories. I noticed I now had TWO random files names with the identical directories underneath but one was dated last weekend and one was dated today. I then copied the contents of the random file from the external HD (dated last weekend) and overwrote everything in the other random directory on C (dated today) so that the older files replaced the newer. That took a while because it was around 15 GIG again. THen I booted L4. I had to renter my user name and password, and it then booted. It immediately started an update download - not that big and then it indexed. The version showed up as 4.2 SR-2 (4.20.4.8288) and everthying was working well.
Now the issue of the two random files in the AppData Local Logos 4 became interesting. I noticed that the subfiles were now updated to the new time in the random file that had come from the external HD, not the one that had been previously installed on this version of Logos in this computer. I shut it down and restarted a couple of times - wonderful - no problems.
Then I shut it down and booted my other computer and launched Logos. That one has not run since the weekend so when I launched it it prepared the library and then ran - same version as above and not problems. I think it did the same download and indexed and then I closed and rebooted and it was fine.
So the problem has been solved in a strange way. One item yet remains to be taken care of. At some stage I will have to delete one of the random files in App Data Logos 4 - the one that has the now older files in it.
So the solution for this problem came because I was in a multiple computer situation and had a back up or second version available that was working. Many thanks for all your suggestions and time. I trust that this will help someone else in the future and save them from whatever problem I had - which of course still remains to be solved in the sense that I still can't boot a download of Logos4Setup.exe without getting that error message. But I can probably go on Windows Forums if and when that reappears to try and solve it then.
Thanks,
Alan
So I copied them
0 -
Quite a saga Alan! I'm not following how you got a dual install directory (random).
At any rate I would suggest RENAMING rather than outright deleting the old random directory just in case. After a few run cycles then go ahead and delete it once you've demonstrated it isn't necessary.
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
Quite a saga Alan! I'm not following how you got a dual install directory (random).
At any rate I would suggest RENAMING rather than outright deleting the old random directory just in case. After a few run cycles then go ahead and delete it once you've demonstrated it isn't necessary.
The thing I would test to make sure it is working correctly before you delete one of the random named directories is syncing of your personal notes and things. Make some changes in Logos on one of your computers (add a note, some highlighting, etc.), force a sync (click on the sync arrows) and then sync Logos the other computer, and be sure that the changes came across. I think Logos uses that random directory name to uniquely identify your installation. I don't currently have to working computers with Logos installed on them anymore, so I can't check whether the directory names have to be the same on both of your computers for syncing to work correctly, or whether, on the contrary, they must be unique for each computer.
0 -
Alan G Heathcote said:
Now the issue of the two random files in the AppData Local Logos 4 became interesting. I noticed that the subfiles were now updated to the new time in the random file that had come from the external HD, not the one that had been previously installed on this version of Logos in this computer. I shut it down and restarted a couple of times - wonderful - no problems.
Look at your latest Logos4.log (in a text editor like Notepad) and you will see an entry near the top like:
.... Data Folder = C:\Users\Alan Heathcote\AppData\Local\Logos4\Data\zv1x4ty5.yyy, Documents Folder = C:\Users\Alan Heathcote\AppData\Local\Logos4\Documents\zv1x4ty5.yyy
This tells you which is YOUR "random Id" folder. Both \Data and \Documents have the same Id, so you can safely delete the other.
Dave
===Windows 11 & Android 13
0 -
Alan G Heathcote said:
Thanks to all of you who have tried to help. As always with distance help there are things I can see or things that I know which you can't see or don't know. I will try to go through some as it might help the analysis.
- We need to be sure that you understand what is being asked of you, however elementary it may seem (and sometime we assume too much[:)])
- it is important to be on the latest version of L4, as this alone may resolve the problem
Alan G Heathcote said:3. On the log files attached above I notice that the Indexer log came 3 minutes before the Logos4 one. Therefore I conclude my first problem may be in the index.
The internal timestamps tell us how the logs relate and the content tells us how relevant it is to the problem; so (for example) I wanted a complete logos4Indexer.log to know what files were being downloaded.Dave
===Windows 11 & Android 13
0 -
Yes, I checked the syncing of my personal notes and it is working fine on both computers. Tried it several times over the last 3 days. Thanks for that - its one of the acid tests.
To clarify how I got a dual install directory (random): the first install put in the first random directory. That had the problem, somewhere, I never found out.
I then pasted into the L4 folder the contents of the back up from my other computer. This over wrote everything until it came to the random directory and all its contents. SInce the random directory was different on the back up of the other computer, it wrote a second random directory into the L4 directory. That left me with two, the new one being from my other computer.
When I booted Logos, since I had overwritten the whole L4 directory, it said it must read the code from the random directory I had just pasted in, not the earlier troubling one. This meant that both my computers were now working off the same random directory name, but the one on each respective computer.
The files in the older random directory that was troublemaking have not been updated since that time. I have not yet deleted them but it is as good as gone since the program is ignoring them. At some stage in a week or so I will zap them but I am waiting until the two computers at differnet times have had plenty of chances to run. Again I never run both at the same time.
Hindsight: when I copied the folders over into L4 in the new computer from the back up of the old one, I should not have overwritten the whole L4 folder, rather the contents of each folder at the lower level ie under the level of the random directory. Then my random directory name would not have changed.
Anyway, for now with a 3 or 4 day test, everything is working fine and syncing fine between the two.
Dave Hooten's told me a particular random folder was mine and I could delete the other based on the logs he read. Not so. As explained above I somehow by copying, told it to read the pasted random folder. But before pasting, yes that was the random folder I was dealing with.
Thanks to all of you for your help - it was really appreciated. Hope there is some help in here for someone else one day.
Alan
0 -
Alan G Heathcote said:
Dave Hooten's told me a particular random folder was mine and I could delete the other based on the logs he read. Not so. As explained above I somehow by copying, told it to read the pasted random folder. But before pasting, yes that was the random folder I was dealing with.
Your latest log, as I stated - ie. from the one that is now working - will show you the random User Id/folder that it uses. I just used one for an example.
Dave
===Windows 11 & Android 13
0 -
Dave, you are correct. At the time you wrote that the logs you were reading showed a random folder name which you then used as an example.
What you didn't know (at that point in time) was I had already over-written it so therefore it was nolonger the correct one. I didn't mean in the previous post that you were wrong, I just meant things had changed - but I worded it poorly. Sorry for that.
Thanks for being available to help and thanks for all your input,
Alan
0
