Bug: 4.0b Beta 7: Still having persistent infinite download problems

Thanks, Bryan. I have not seen this problem on the last two betas (10 and 11) so I'd kind of thought maybe it was fixed, whatever it was. But it's happening again for Beta 12, so I have the opportunity to gather some more data for you.

Bryan Albert said:

1.  How long have you waited for the download to make progress? The default pause before retrying is ten minutes. (I'd guess that you have waited longer than ten minutes, though I thought I ought to ask.)

I've waited hours! Multiple times.

Bryan Albert said:

2.  What sorts of work-arounds have you had success with? For example, if you restart your computer, does the download succeed? 

I can't remember off the top of my head, but I'm going to wait to answer that until I've spent some time gathering info on when it doesn't work. If I work around it right away again, that won't help you.

Bryan Albert said:

3.  Since you're handy with bitsadmin.exe, what happens if, when the download is stalled, at your Command Prompt you type "bitsadmin /reset" (without the quotes)? The Logos 4 Indexer icon in your System Notification Area should disappear. If you were to then issue the Logos 4 "update now" command, it should try downloading the update again. If you do this a number of times, does it always fail, or might it eventually actually succeed begin downloading the file? 

I think this is one of the things that has worked around the problem for me in the past (possibly also with a machine reboot), but will get back to you on it...

Bryan Albert said:

4.  Please gather some data for us: type "update now" in the Logos command window to initiate a download. (If your Logos is already up to date, see the special instructions below). Then type in your Command Prompt "bitsadmin /list" to get the guid for the download job, pretend it was {A8ECFE28-B800-4E1A-8C91-BAD46C772328}, then, when it's showing TRANSIENT_ERROR, type "bitsadmin /info {A8ECFE28-B800-4E1A-8C91-BAD46C772328} /verbose and past the output back here. Hopefully it will contain some useful clues. 

Here's the output from that:

C:\Windows>bitsadmin /list

BITSADMIN version 3.0 [ 7.0.6001 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

{24F0B512-9F1A-4731-BEF0-13FB5544CE90} 'Logos 4: Update:152' TRANSIENT_ERROR 2 /

 3 347130 / 40499706

Listed 1 job(s).

C:\Windows>bitsadmin /info {24F0B512-9F1A-4731-BEF0-13FB5544CE90} /verbose

BITSADMIN version 3.0 [ 7.0.6001 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

GUID: {24F0B512-9F1A-4731-BEF0-13FB5544CE90} DISPLAY: 'Logos 4: Update:152'

TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: RLP-DESKTOP\Rosie Perera

PRIORITY: FOREGROUND FILES: 2 / 3 BYTES: 347130 / 40499706

CREATION TIME: 2/24/2010 8:31:00 PM MODIFICATION TIME: 2/24/2010 9:11:04 PM

COMPLETION TIME: UNKNOWN ACL FLAGS:

NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3

RETRY DELAY: 600 NO PROGRESS TIMEOUT: 1209600 ERROR COUNT: 6

PROXY USAGE: PRECONFIG PROXY LIST: NULL PROXY BYPASS LIST: NULL

ERROR FILE:    http://downloads.logos.com/LBS4/InstallerBeta/Logos4.msi -> C:\Users\Rosie Perera\AppData\Local\Logos4\Data\wmkts0os.hzs\UpdateManager\Installers\152\Logos4.msi

ERROR CODE:    0x80072ee4 - An internal error occurred in the Microsoft Windows HTTP Services

ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.

DESCRIPTION:

JOB FILES:

        334672 / 334672 WORKING http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe -> C:\Users\Rosie Perera\AppData\Local\Logos4\Data\wmkts0os.hzs\UpdateManager\Installers\152\Logos4Setup.exe

        12458 / 12458 WORKING http://downloads.logos.com/LBS4/InstallerBeta/Logos4UpdateScript.lbxdat -> C:\Users\Rosie Perera\AppData\Local\Logos4\Data\wmkts0os.hzs\UpdateManager\Installers\152\Logos4UpdateScript.lbxdat

        0 / 40152576 WORKING http://downloads.logos.com/LBS4/InstallerBeta/Logos4.msi -> C:\Users\Rosie Perera\AppData\Local\Logos4\Data\wmkts0os.hzs\UpdateManager\Installers\152\Logos4.msi

NOTIFICATION COMMAND LINE: none

Peercaching flags

         Enable download from peers      :false

         Enable serving to peers         :false

CUSTOM HEADERS: NULL

C:\Windows>

Bryan Albert said:

If your Logos 4 is already up to date, you can fake it out by using a special update channel we made for you. Type into your Logos 4 command window "set update channel to rosie", which should cause it to think that there's a download available.

How cool is that! I have my own private update channel! [H]  I'll try it if I need it.

Now on to try out item #3...

OK, I let the update run for nearly an hour with no progress, finally gave up and ran "bitsadmin /reset" and then "update now." Again it waited for a LONG time, at least 20-30 minutes, but it did finally start downloading and completed fine. Unfortunately I wasn't able to capture any more data long the way to see what was hanging it up before the percentages started incrementing. I did not have to reboot my machine at any time.

I will try the special rosie update channel next...

Had the same results with that. I did "update now" three times. First time I let it run for a long time (30 min or so), and it was stuck at 0% the whole time. Canceled it by running "bitsadmin /reset" and tried "update now" again. Next time I let it run until bitsadmin reported ERROR COUNT: 3, then canceled it again using "bitsadmin /reset". Ran it a third time and it's still stuck at 0%. The error code and other info given by "bitsadmin /info guid /verbose" was essentially the same as that posted above. I'm going back to the default update chanel now.

Hope this helps. I'd really like to see you figure this out, because it might be the cause of some other people's update problems too.

Let me know if there's any other info I can collect for you either with the rosie channel or next time there is a real beta update.

UPDATE: The third try on the rosie update channel did finally start downloading and got as far as 99% before I canceled it. You had told me it would try to download Beta 11, but I'm on Beta 12 already and I didn't want it to mess up anything, so that's why I canceled it.