Some files fail Verification
cme4pc
23 Feb 2008
First.... Thanks to the AP team for continuing this project and working to once again provide all of us with a viable offline updating mechanism. Keep up the good work!
Second... Most of the threads here have to do with AutoPatcher failing to launch or complete the downloading process from the MS servers. On the first 2-3 attempts at running APUP, I had similar difficulties but eventually the downloading process completed. IMHO, the downloading process is complicated by the MS servers re-directing amongst themselves, this possibly due to demand on any particular server at any given time, or possibly the location of requested updates changing on the MS side of the process. I doubt that there is anything that can be done on the local/client side to control what MS is doing with their update/download servers. APUP is therefore probably always going to have some element of "hit and miss" as far as successful request-download-verify of all the updates it seeks. Patience is a virtue and frankly, even when manually d/l IT versions of MS updates from their download servers, it's not a 100% perfect process. Much has to do with the fact that MS servers will respond best to requests coming from clients with better/hi speed connections, and dump those that are slow/intermittent. Nothing AP can do about this. Again, good things come to those with good connections and run APUP at times where there is low demand on MS download servers.
Third.... And this is the issue / topic of this thread. I was able to run APUP in a new directory all of it's own (independent of any previous AP installs [old AP]) and after a few times of getting bounced/hung by the MS servers (watched IP request/responses realtime) during the d/l process, APUP completed the downloads. However, I was given the warning that "SOME FILES FAILED VERIFICATION" and the option to proceed at my own risk. I've browsed the folders ..\APUP and all subfolders and everything appears to be in place as far as structure and content. As far as I can tell, all the components / modules / etc. look fine and ready to deploy. So now at long last I'll ask my two questions.....
A. Is the failed verification warning just a error trapping message that indicates the D/L process was interupted at some point and the downloaded files themselves are fine and ready to use?
B. If the downloaded files are in fact corrupted (failed checksum or md5 values or ???) how can one determine which of the updates/modules has failed the verification process. I looked everywhere for a log file or some other history to indicate which of the files fail verification but was unable to find the information.
Thanks in advance and keep up the good work!!!!!
Second... Most of the threads here have to do with AutoPatcher failing to launch or complete the downloading process from the MS servers. On the first 2-3 attempts at running APUP, I had similar difficulties but eventually the downloading process completed. IMHO, the downloading process is complicated by the MS servers re-directing amongst themselves, this possibly due to demand on any particular server at any given time, or possibly the location of requested updates changing on the MS side of the process. I doubt that there is anything that can be done on the local/client side to control what MS is doing with their update/download servers. APUP is therefore probably always going to have some element of "hit and miss" as far as successful request-download-verify of all the updates it seeks. Patience is a virtue and frankly, even when manually d/l IT versions of MS updates from their download servers, it's not a 100% perfect process. Much has to do with the fact that MS servers will respond best to requests coming from clients with better/hi speed connections, and dump those that are slow/intermittent. Nothing AP can do about this. Again, good things come to those with good connections and run APUP at times where there is low demand on MS download servers.
Third.... And this is the issue / topic of this thread. I was able to run APUP in a new directory all of it's own (independent of any previous AP installs [old AP]) and after a few times of getting bounced/hung by the MS servers (watched IP request/responses realtime) during the d/l process, APUP completed the downloads. However, I was given the warning that "SOME FILES FAILED VERIFICATION" and the option to proceed at my own risk. I've browsed the folders ..\APUP and all subfolders and everything appears to be in place as far as structure and content. As far as I can tell, all the components / modules / etc. look fine and ready to deploy. So now at long last I'll ask my two questions.....
A. Is the failed verification warning just a error trapping message that indicates the D/L process was interupted at some point and the downloaded files themselves are fine and ready to use?
B. If the downloaded files are in fact corrupted (failed checksum or md5 values or ???) how can one determine which of the updates/modules has failed the verification process. I looked everywhere for a log file or some other history to indicate which of the files fail verification but was unable to find the information.
Thanks in advance and keep up the good work!!!!!
Cristiano
23 Feb 2008
> how can one determine which of the updates/modules has failed the verification process
pretty easy. just run like this: apup /log
a log will be generated. then, you just need search for "failed", "missing", "queue" to find each failed download
[]s
pretty easy. just run like this: apup /log
a log will be generated. then, you just need search for "failed", "missing", "queue" to find each failed download
[]s
