Verification Failed
Classified711
17 Jul 2010
Getting a verification failed when using the AP office 2007 updater.
It looks to be an MD5 hash mismatch. Should be easy enough to fix.
I have attached the log file for you to look at.
Thanks for all the hard work.
It looks to be an MD5 hash mismatch. Should be easy enough to fix.
I have attached the log file for you to look at.
Thanks for all the hard work.
Attached Files
-
apup.txt (2.72K)
downloads: 7
dkdk_it
20 Jul 2010
Please can you re-run APUP?!?
I'm checking the new script file and I'm reading this:
ExpectedSize is right...
I'm checking the new script file and I'm reading this:
Spoiler
ExpectedSize is right...
_def_x_
21 Jul 2010
@Classified711
Your log shows an outdated Office script -> autopatcher_off_07_glb_20100608.script - the latest is -> autopatcher_off_07_glb_20100713.script, if in fact you ran APUP and the log generated is from July 17, 2010.
If rerunning APUP, selecting the Office 2007 script still gets you last months script you may have a web cache issue - talk to your ISP or who ever is in charge of your internet connection. I threw both links in a download manager that is capable of displaying the file size in bytes - it matches the latest script... and the expected md5 matches - the latest script (20100713) appears to be correct here.
This is common with static links - MS keeps the file names and links the same from month to month, only the file size and md5 will change, the latest Office script seems to have the latest information, you are downloading from an old script for some reason, strange you don't have more errors.
Anyway, this is my guess.
Your log shows an outdated Office script -> autopatcher_off_07_glb_20100608.script - the latest is -> autopatcher_off_07_glb_20100713.script, if in fact you ran APUP and the log generated is from July 17, 2010.
If rerunning APUP, selecting the Office 2007 script still gets you last months script you may have a web cache issue - talk to your ISP or who ever is in charge of your internet connection. I threw both links in a download manager that is capable of displaying the file size in bytes - it matches the latest script... and the expected md5 matches - the latest script (20100713) appears to be correct here.
This is common with static links - MS keeps the file names and links the same from month to month, only the file size and md5 will change, the latest Office script seems to have the latest information, you are downloading from an old script for some reason, strange you don't have more errors.
Anyway, this is my guess.
Classified711
21 Jul 2010
Thanks guys,
I re-ran APUP a couple of times and also ran a verification against the MD5 checksums. All checked out.
That is why I thought the expected Hash may have been incorrect.
Will re-test and provide feedback in a few hours.
I re-ran APUP a couple of times and also ran a verification against the MD5 checksums. All checked out.
That is why I thought the expected Hash may have been incorrect.
Will re-test and provide feedback in a few hours.
