Won't Run, Won't Update

Earlier today I experienced a power outage while Logos 6 was running. I was not currently using the program, but it was running in the background.

A few minutes ago, I tried to start Logos, but got an error that said:

An upgrade is required

Some of your resources and documents are not compatible with this version. To continue using Logos Bible Software, upgrade to version 6.8 SR-1 or later.

The problem is my system was upgraded to that version a few days ago. I went to the install page and downloaded the setup file. When I ran it, I was given a message that my software was up to date and the installer closed.

I've installed my log files if they will help. I REALLY don't want to have to do a wipe and reinstall because I'm in the Philippines and my network bandwidth is NOT conducive to gigabytes of resource downloads.

8764.Logos Log Files.zip

Find more posts tagged with

Comments

Mark Barnes

Hello Douglas,

It's extremely unlikely that you'll need to do a full download.

However, the log files that you have aren't complete enough to understand what the problem is. Can you enable Diagnostic Logging, then try running Logos again, then upload your logs again.

Thanks.

Douglas Thompson

https://community.logos.com/discussion/comment/797419#Comment_797419

Here's the new file.

Thanks for the quick reply!

7573.Logos Log Files.zip

Mark Barnes

https://community.logos.com/discussion/comment/797421#Comment_797421

Hi Douglas,

Logos thinks it's running version 6.0. I'm not sure how that happened. Perhaps a system restore?

The other thing that's confusing is that Logos is installed in C:\Users\Doug\Downloads\Logos\, but your other log suggests the program itself is in \Logos\System\. That's a very unusual configuration. Was that deliberate?

I'm wondering whether Logos has got confused as to where it's been installed, and you'd ended up with two copies.

I think it would be best to double check the location(s) of Logos.exe before proceeding.

Where does the shortcut you're using point?
Is there a Logos.exe file in C:\Users\Doug\Downloads\Logos\?
Is there a Logos.exe file in \Logos\System\?

Douglas Thompson

https://community.logos.com/discussion/comment/797426#Comment_797426

My computer is configured with two SSD drives in a RAID-0 setup that contains my operating system and most of my programs. I have a couple of 2TB drives in a RAID-1 configuration that I use to store data.

When I first installed LOGOS, I could not figure out how to keep my library in a different location from the data. So, I installed it again and directed the installation program to install into the \Logos folder. This puts the program on the slower HDD array, but that's not a problem performance-wise. The shortcut I use to launch the program points to the \Logos folder.

However, I did look in the C:\Users\Doug\Downloads\Logos\ folder and there is also a Logos.exe file there, along with a lot of other folders. So, when the system auto-updated a few days ago, did it install the new program files in the C: location?

Mark Barnes

https://community.logos.com/discussion/comment/797429#Comment_797429

However, I did look in the C:\Users\Doug\Downloads\Logos\ folder and there is also a Logos.exe file there, along with a lot of other folders. So, when the system auto-updated a few days ago, did it install the new program files in the C: location?

That looks to be the case, but I can't be 100% sure.

Separating the 'program' from the 'data' is unsupported, and isn't worth it anyway. You should install everything (program, library, index, documents) in the same folder location. (If you really know what you're doing, you can use symbolic links to move some of that onto other drives, but as I said, that's not supported.)

The question is: how do we clear up the mess?

Can you try simply double-clicking on the Logos.exe file in C:\Users\Doug\Downloads\Logos\ to see if that works? If so, all you'll need to do is delete d:\Logos and change your shortcut.

If it doesn't work (or if it does work, but you're not satisfied having everything on drive c), then I'll show you how to reinstall without needing to re-download everything.

Douglas Thompson

https://community.logos.com/discussion/comment/797442#Comment_797442

It would appear that, when I ran Logos from my \ array, and it began to auto-update, it went ahead and installed itself into the default location. I checked the two \Logos folders, and it would appear that the one on the SSD array is a little more that 1GB larger than the one on the data array. Since it's already using up 17GB and I still have more than half of the original SSD space available, I'll just leave it where it is, and delete the one on the \ drive.

It might be a good idea to check with programmers and see if Logos is installed into a non-standard location and begins to auto-update, does the updater not pay attention to that fact? I can see no reason why the update process duplicated my installation in a place I didn't want it to begin with.

Thanks again for all of your assistance in this matter.

Mark Barnes

https://community.logos.com/discussion/comment/797577#Comment_797577

It would appear that, when I ran Logos from my \ array, and it began to auto-update, it went ahead and installed itself into the default location. I checked the two \Logos folders, and it would appear that the one on the SSD array is a little more that 1GB larger than the one on the data array. Since it's already using up 17GB and I still have more than half of the original SSD space available, I'll just leave it where it is, and delete the one on the \ drive.

Be careful. Doing that might cause the same problem next time around.

The install location of Logos is stored in the registry (HKCU\SOFTWARE\Logos4), and the users are also stored (HKCU\SOFTWARE\Logos4\Users). You need to be sure that the InstallDirectory entry matches the installation that you keep, and that the Users key matches the random folder name in that installation.

So if you have two full installations, I would personally:

Check the registry to see which one is in use.
Delete the other one.
Re-download 6.8 and make sure the installer is happy (it should say the installation already exists).

If you've already deleted the installation that the registry refers to, then you'll need to modify the two registry settings. To match the new location. But personally, I would only do this if I had to.

It might be a good idea to check with programmers and see if Logos is installed into a non-standard location and begins to auto-update, does the updater not pay attention to that fact? I can see no reason why the update process duplicated my installation in a place I didn't want it to begin with.

There are many users who install Logos on a separate drive, and run in without problems. I'd be 99% sure the problem arose because you tried to move the program and 'data' into separate locations. As I said, that's not supported.

Douglas Thompson

https://community.logos.com/discussion/comment/797614#Comment_797614

I think I was unclear in my initial post. I was attempting to install the software and data into two separate places, but could not find an option to do so. I think instead installed to my \ drive. I never had any problems until this last update. The second installation of Logos in my C:\Users\...\Logos\ folder is a new phenomenon.

THAT is why I'm really paranoid about having to eventually do a full wipe, reinstall and download. That would literally take weeks at the internet speeds available to me here.

Douglas Thompson

https://community.logos.com/discussion/comment/797622#Comment_797622

And, another update. I checked the registry key under Software\Logos4 and the installation path matches the C:\Users\...\Logos location.

I checked the key under Logos4\Users and there are two of them. One matches the Installation path random file name; the other matches the random file name on the \ drive. It seems to me that I could easily delete the \ installation. I could also conceivably delete the registry key under the Users entry, but that probably wouldn't be necessary.

Your thoughts?

Mark Barnes

https://community.logos.com/discussion/comment/797623#Comment_797623

I checked the key under Logos4\Users and there are two of them. One matches the Installation path random file name; the other matches the random file name on the \ drive. It seems to me that I could easily delete the \ installation. I could also conceivably delete the registry key under the Users entry, but that probably wouldn't be necessary.

I would agree with that assessment. You'll also need to update your shortcut to point to the drive c location.

I will ask a Faithlife staff member to take a look at this thread so they can see whether there's anything wrong with the auto-update feature. The way Logos updates itself was changed very recently, so it would help them to know which version you had prior to the auto-update.

Douglas Thompson

https://community.logos.com/discussion/comment/797625#Comment_797625

Well, I'm not sure where I'd find that information in the Logos folder. If there's a place I can look in the file structure to discover that, I'd be happy to look into it. I can tell you that the Logos.exe file in that folder was originally created on December 19, 2014. Not sure if that will help.

Mark Barnes

https://community.logos.com/discussion/comment/797632#Comment_797632

Well, I'm not sure where I'd find that information in the Logos folder. If there's a place I can look in the file structure to discover that, I'd be happy to look into it. I can tell you that the Logos.exe file in that folder was originally created on December 19, 2014. Not sure if that will help.

You can right-click on Logos.exe, choose properties and then select the Details tab to find out what version the installation is before you delete it.

Douglas Thompson

https://community.logos.com/discussion/comment/797633#Comment_797633

Ah...herein lies the rub. I, knowing better, actually REPLACED my logos.exe in the \ drive with the one from the C:\ drive. Rookie mistake, I know...I even considered renaming the old file and bringing the new one over, but I didn't.

Anyway...hopefully the date of December 19, 2014 will give them enough information to know what I was running. It was certainly Logos 6, as I purchased the Platinum base package.

Mark Barnes

https://community.logos.com/discussion/comment/797637#Comment_797637

Ah...herein lies the rub. I, knowing better, actually REPLACED my logos.exe in the \ drive with the one from the C:\ drive. Rookie mistake, I know...I even considered renaming the old file and bringing the new one over, but I didn't.

Anyway...hopefully the date of December 19, 2014 will give them enough information to know what I was running. It was certainly Logos 6, as I purchased the Platinum base package.

Don't worry. The important thing is for you to be back up and running, and for the registry entry to match your install location. Let us know how you get on.

Douglas Thompson

https://community.logos.com/discussion/comment/797640#Comment_797640

I think I'm good to go for now. I'd REALLY like to help unravel the mystery of why this happened. I hope your development team can use the creation date of the old Logos.exe file to see if there's an issue with an upgrade from THAT version to the current version. I must admit, I didn't launch Logos for quite some time after initial installation. Close to a year, actually. No telling how many small updates happened in that time.

I won't be the only person who spent a LOT of money buying a base package, only to let it founder for a long period of time before feeling the call of the Holy Spirit (or a 30-day challenge email...but one and the same) to come back...only to potentially find this sort of perplexing issue.

I tend to be a bit more computer literate than many of my peers....this kind of put me in a pickle. I would love to be able to help keep this from happening to anyone else.

JT (alabama24)

https://community.logos.com/discussion/comment/797641#Comment_797641

I hope your development team

For clarification: Mark isn't an employee. Faithlife employees are designated by a green Faithlife badge under their avatar.

I didn't launch Logos for quite some time after initial installation. Close to a year, actually. No telling how many small updates happened in that time.

Updates to the software engine happen at least once every six weeks.

Mark Barnes

https://community.logos.com/discussion/comment/797641#Comment_797641

I would love to be able to help keep this from happening to anyone else.

Just to let you know that I contacted a Faithlife developer on your behalf to take a look at this thread. After doing so, he replied to say that he's confident it wasn't a problem with the installer, so it shouldn't happen to anyone else.

Jim Goos

https://community.logos.com/discussion/comment/800441#Comment_800441

Thanks for this post. I had the same problem this morning. Logos installed an update on Monday morning, but when I tried to run Logos this morning I received the message that an update was required (to Logos 6.9 or later). I right-clicked the Logos shortcut icon, which referred to the installation on my D drive, where it has been running in the past.

I also checked the C drive and found an installation dated Monday in the App Data folder. When I opened Logos from there, it worked perfectly.

In light of the above, I don't understand why this update installed in the default folder rather than the one on the D drive, where previous updates have installed. However, the new installation works. I will delete the old shortcut icon and create a new one from the C drive.