INFO: Install/Upgrade Warning: "Logos Bible Software 4 COM Launcher"

This post is For Information Only in case someone gets this error in the future and finds this when searching on the error message.

I was running an application which uses the Logos4 COM API to interact with the Logos4 application.

My Logos4 downloaded an update, but as the other application was still running, the upgrade process gave this warning report.

I expect most users would work out or guess what might be going on. But in case not, I have posted this in the hope it might be useful to someone one day.

Solution: Close the other application that interacts with Logos4 if possible, then click OK for the upgrade to process.

In the event that you just click OK, and leave it to sort itself out, it might be OK, but it will be safer and more sure if you can close the other application first.

P.S. Thanks to the Logos Team that this condition is detected by the installer, rather than some bad outcome ...

Find more posts tagged with

Comments

Rosie Perera

Hi Jim, could you also put this on the wiki somewhere? That's the best place for information to direct people to in the future, as it won't get lost amongst thousands of posts. I would suggest linking it in somewhere from http://wiki.logos.com/Logos_4_COM_API, perhaps create a Troubleshooting page linked from the introductory material on that main COM API page somewhere, and then post this nice graphic and your explanatory comments on that Troubleshooting page. It can be expanded and broken down into more sub-pages later if necessary.

JimTowler

https://community.logos.com/discussion/comment/141566#Comment_141566

Yes, maybe thats a good idea.

However, it needs to be somewhere where it can be found, or it serves no use.

Anyone looking on the COM API page already knows the answer.

I'm thinking of someone in the future thats using "Sue's Ace Lessions for New Christians" and really has no clue that there is any connection with something called "COM API".

Rosie Perera

https://community.logos.com/discussion/comment/141572#Comment_141572

Yes, maybe thats a good idea.

However, it needs to be somewhere where it can be found, or it serves no use.

Anyone looking on the COM API page already knows the answer.

It wouldn't be so much for people looking on the COM API page but for MVPs and other advanced forum users who answer people's questions, to have an easy link they can find to direct puzzled users to. Granted you're the only person I know of (so far) who has been using COM API at all, so you might end up being the only one ever answering people's questions about COM API issues, and you'd know how to find this thread and point people to it, but the rest of us would have a hard time finding it again.

JimTowler

https://community.logos.com/discussion/comment/141581#Comment_141581

Granted you're the only person I know of (so far) who has been using COM API at all

Taking Bob's comments at face value, it seems there are people somewhere working on commercial products ...

If so, they don't seem to be speaking or seeking support here. Maybe they have a direct line to the guys hacking the code.

(I spent rather a long time last night downloading the most recent Windows and ..NET SDK and 2 GB of docs, so I can attempt to drive Windows Media Player 11 via API calls. I want to see if I can get my Audio ESV working with ESV in Logos4. I expect that in a few days I might have them tracking at verse-level to see and hear the ESV. Something I will value and use, I expect. If it works well, I'm sure others would want it too, but they would first need to purchase one of the many Audio Bible products - there are many of them, and for sometimes more than one per version. I've seen them for at least KJV, NIV, TNIV and ESV. Others too I expect.)

Back to the point here: I think I'll come back in due course, and write some stuff for a Wiki page. Until then, this page can serve some use maybe.