Stuck In Loop - Update Ready to Install, then No Update Available

BillS · December 2009

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Now, each time I try to start L4, I go thru the loop again... and it won't start.

It WILL let me start if I click NO & don't attempt to install.

Ctrl + clicking on L4 startup icon enters the same loop.

Any ideas?

Blessings!

BIll

P.S. after reading another thread on a similar (but not identical) issue I chose to rebuild index to see if that'd help... Under way, now. It claims 32 hours at present, but the 1st 31 hours will go by in the next 60 minutes. LOL. If only I could get the last hour to go by that fast!

Bradley Grainger (Logos) · December 2009

Bill Stonebraker said:

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Thanks for reporting this; we're investigating the problem right now.

Mark Barnes · December 2009

https://community.logos.com/discussion/comment/66197#Comment_66197

I think the problem is for those who have update channel set to beta. http://downloads.logos.com/LBS4/InstallerBeta/Logos4UpdateScript.lbxdat doesn't appear to have been updated yet.

Rich DeRuiter · December 2009

Bill Stonebraker said:

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Now, each time I try to start L4, I go thru the loop again... and it won't start.

It WILL let me start if I click NO & don't attempt to install.

Ctrl + clicking on L4 startup icon enters the same loop.

Any ideas?

So you can start Logos, if you don't do the update first, right?

What happens if you start Logos that way, let it finish loading and then type "Update Now?" Will it update then?

It's also possible that you have a corrupted MSI file. It will be somewhere in the Logos4 subdirectories. If the above suggestion doesn't work, and you see an MSI file in there, try moving it somewhere outside the L4 sub-directory and run "Update Now" again.

Well, two ideas. Not sure either one will work, but something to try in 32 hours, if indexing alone doesn't fix it. [;)]

Russ Quinn · December 2009

https://community.logos.com/discussion/comment/66211#Comment_66211

I think the fix to all of this is to execute the command "set update channel to default".

Mark Barnes · December 2009

https://community.logos.com/discussion/comment/66214#Comment_66214

I'm pretty sure it's just that TPTB haven't updated the software on the beta server. Downloading manually from http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe fixes the problem. Changing the update channel doesn't (presumably because Logos is already confused by then).

BillS · December 2009

https://community.logos.com/discussion/comment/66218#Comment_66218

Mark Barnes said:
I'm pretty sure it's just that TPTB haven't updated the software on the beta server. Downloading manually from http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe fixes the problem. Changing the update channel doesn't (presumably because Logos is already confused by then).

Mark's analysis / solution was right on for me. Nothing else worked.

THANKS, all!

I guess I got my answer to a much earlier post in another thread where we were all confessing to Compulsive Beta Disorder--I wondered why I'd ever "Set Update Channel to Default". [:D]

Well, I've run out of excuses to avoid work, so it's back at it, now...

Dave Hooton · December 2009

https://community.logos.com/discussion/comment/66218#Comment_66218

Mark Barnes said:
I'm pretty sure it's just that TPTB haven't updated the software on the beta server.

Mark, why do you think it is related to the beta server as opposed to the update channel when one is not on a beta version?

Mark Barnes · December 2009

https://community.logos.com/discussion/comment/66274#Comment_66274

Sorry, I'm not making myself clear. If you have set the update channel to beta, then Logos downloads the latest version from a different location. (It's actually a different folder on the same server, not a different server.) It seems that Logos updated the software referenced by the standard update channel, but didn't update the software referenced by the beta update channel.

This meant that the beta update channel noticed the update, and Logos downloaded it. Or at least it thought it did, but it downloaded the previous version, because the server hadn't been updated with the new version. This, however, wouldn't install because Logos knew it wasn't the new version. Subsequently changing the update channel didn't work, because as far as Logos was concerned, the update was sitting in the updates folder ready to be installed.

The proper 'fix' therefore was for Logos to update the server with the correct file. Downloading the current version from the non-beta location was a workaround.

Dave Hooton · December 2009

https://community.logos.com/discussion/comment/66326#Comment_66326

From what Bradley let slip in PC Beta, if you set the update channel to beta you will receive only beta releases ie. you won't get stable releases, but when 4.0b Beta 1 is released you will be upgraded (with all the consequences that accompany a beta release!).

"set update channel to default" is not the same thing as setting the update channel to stable; it will do that only if you are running a stable release. So the default channel for a beta release is the beta channel, the default channel for a stable release is the stable channel.

Logos should not update the beta channel with a stable release, and why you even got an update from the beta channel is a mystery, but it may account (as you state) for the failure of setting the channel to default. So it emphasises the warning given by Bradley that setting the channel to beta is [quote]definitely a "use at your own risk" command!

Mark Barnes said:
Downloading the current version from the non-beta location was a workaround.

That is the normal way to update or install a stable version ie. http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe

But I'm curious why it is different to http://downloads.logos.com/LBS4/LDLS4Installer/Logos4Setup.exe which I have always used?

NOTE: Being on my holiday dial-up is preventing me from testing any of these commands + not updating my 4.0a RC1 & 4.0 SR-7 installations.

Mark Barnes · December 2009

https://community.logos.com/discussion/comment/67409#Comment_67409

Sorry to disagree [:)]

Dave Hooton said:
if you set the update channel to beta you will receive only beta releases ie. you won't get stable release

No, setting the update channel to beta will always give you the latest version, whether that is beta or stable. I got SR-2, for example, even though the bug prevented me from getting SR-1.

Dave Hooton said:
"set update channel to default" is not the same thing as setting the update channel to stable;

You can't set update channel to stable. It's default or beta only.

Dave Hooton said:
That is the normal way to update or install a stable version

No, the normal way for existing users is for the program to auto-update or to manually update through "update now". That was broken because SR-1 hadn't been properly published to the beta channel.

As to the two different URLs, Logos recently changed to the shorter form. I don't know why.

Dave Hooton · December 2009

https://community.logos.com/discussion/comment/67439#Comment_67439

Mark Barnes said:
No, setting the update channel to beta will always give you the latest version, whether that is beta or stable. I got SR-2, for example, even though the bug prevented me from getting SR-1.

I've asked Bradley to clarify this.

Mark Barnes said:

Dave Hooton said:
"set update channel to default" is not the same thing as setting the update channel to stable;

You can't set update channel to stable. It's default or beta only.

That wasn't the intention of the statement. It's just that some people could interpret "default" as meaning "stable".

Mark Barnes said:
No, the normal way for existing users is for the program to auto-update or to manually update through "update now".

Clarification: it is the only way if the normal update channels are not working.

Mark Barnes · January 2010

https://community.logos.com/discussion/comment/67456#Comment_67456

Dave Hooton said:
That wasn't the intention of the statement. It's just that some people could interpret "default" as meaning "stable".

OK, I see. Though, of course, in the context of the current version, that is what it means. Basically, there are two RSS feeds published by Logos. Once contains just release versions, the other release and beta. Switching the update channel just changes which feed Logos looks like. When running a beta, Logos looks at the beta RSS feed for updates. When running a non-beta (including Release Candidates), Logos looks at the stable feed, unless you specify the beta.

Bradley Grainger (Logos) · January 2010

https://community.logos.com/discussion/comment/67523#Comment_67523

Mark Barnes said:

Dave Hooton said:
That wasn't the intention of the statement. It's just that some people could interpret "default" as meaning "stable".

OK, I see. Though, of course, in the context of the current version, that is what it means. Basically, there are two RSS feeds published by Logos. Once contains just release versions, the other release and beta. Switching the update channel just changes which feed Logos looks like. When running a beta, Logos looks at the beta RSS feed for updates. When running a non-beta (including Release Candidates), Logos looks at the stable feed, unless you specify the beta.

This is an accurate summary.

Our current policy is to publish 4.0a SR releases to the "beta" channel (to help the users who forgot to go back to "stable") until 4.0b beta testing starts.

Dave Hooton · January 2010

https://community.logos.com/discussion/comment/69692#Comment_69692

Bradley Grainger said:

Mark Barnes said:

Dave Hooton said:
That wasn't the intention of the statement. It's just that some people could interpret "default" as meaning "stable".

OK, I see. Though, of course, in the context of the current version, that is what it means. Basically, there are two RSS feeds published by Logos. Once contains just release versions, the other release and beta. Switching the update channel just changes which feed Logos looks like. When running a beta, Logos looks at the beta RSS feed for updates. When running a non-beta (including Release Candidates), Logos looks at the stable feed, unless you specify the beta.

This is an accurate summary.

Our current policy is to publish 4.0a SR releases to the "beta" channel (to help the users who forgot to go back to "stable") until 4.0b beta testing starts.

Mark,

I just noticed this response when looking back from Bradley's latest response at http://community.logos.com/forums/p/9459/75671.aspx#75671.

I was wrong in thinking that beta channel only contained beta releases, but because my reason was "historical" I needed proof like the biblical doubting Thomas. Thanks for providing the elements of that proof in being able to study the Beta and Stable feeds.

God bless,

Jan Kleinsmit · January 2010

https://community.logos.com/discussion/comment/76264#Comment_76264

Had a similar problem to Bill.

Downloading manually as suggested by Mark from http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe fixed in a few minutes. Thanks Mark.

As a matter of interest, I live in South Africa where bandwidth is expensive and relatively slow. I am fortunate in that I have access to a 3Mb pipeline and downloading the original and subsequent updates was not really a problem.

I was wondering if there are any fellow South Africans out there who have Logos4 and how they are coping?

By the way, an outstanding product worth all the effort and cost!

Blessings :
Jan Kleinsmit,
Pretoria, SA

Dave Hooton · January 2010

https://community.logos.com/discussion/comment/76284#Comment_76284

JanKleinsmit said:
I was wondering if there are any fellow South Africans out there who have Logos4 and how they are coping?

There are. Just announce yourself in the General forum.

Stuck In Loop - Update Ready to Install, then No Update Available

Comments

Categories