3 replies to this topic

[WillEllen]

One file for Office 2003 (KB923618 about 120,000 KB) had verification issues during download with AP. I downloaded it directly from MS and placed it in the proper AP folder with the others using the same format. AP fails to recognize this file during an install.

Is there a way to edit something so AP will install the update and will not attempt to download the same file again? I am using dialup and every time I do an update check AP starts to do a 7 hour download for this file.

Thanks much

Will

[_def_x_]

Hi WillEllen...

This file is over 120MB, on dialup it can get corrupted (depending on the tool used), have you checked the md5 hash?
-> Office2003SP3-KB923618-FullFile-ENU.exe -> md5hash: 1466A88A6863FF6C1E87212AEEA5CAB5

If the hash is wrong, APUP will remove the file and start again from the beginning.

Quote

I downloaded it directly from MS and placed it in the proper AP folder with the others using the same format.

I'm not sure exactly what you mean by this but APUP should have allready created a folder for this file, if you tried downloading
it using APUP. You would only have needed to remove the partial download (incomplete file) from the folder and moved your new
file to this folder.

This is the folder the file should go in:
...\...\modules\Office2003\!SP3KB923618_enu.apm_files

I'm on dialup as well and large downloads I always get using a download manager, I move the file to the given folder, but I always
let APUP create the folder first (you can do it yourself but the name must match exactly the name in the script). I always verify
the file as well or it will get removed and the download will begin again.

So, if you downloaded a complete file (md5hash is a match) and you also downloaded the associated "apm" file for this update, there
might be a detection issue. I don't have Office installed so my module won't load.

I would re-run APUP, it should detect the file in the folder and move on (if you did things correctly), and you should get a "Finish" tab
(without error) to "Exit" APUP. When you run AutoPatcher, it should load the Office 2003 module, and show it as Official. If all these steps
work for you but "No" 923618 appears as an update, this is a detection issue.

Let us know exactly the status of your Office module etc and we will go from there.

Also, it is a good idea to run apup.exe /log (select the module you are having troubles with) to create a log file and post it in here.

Mike

[WillEllen]

gUiTaR_mIkE, on May 7 2009, 04:00 AM, said:

Hi WillEllen...

This file is over 120MB, on dialup it can get corrupted (depending on the tool used), have you checked the md5 hash?
-> Office2003SP3-KB923618-FullFile-ENU.exe -> md5hash: 1466A88A6863FF6C1E87212AEEA5CAB5

If the hash is wrong, APUP will remove the file and start again from the beginning.


I'm not sure exactly what you mean by this but APUP should have allready created a folder for this file, if you tried downloading
it using APUP. You would only have needed to remove the partial download (incomplete file) from the folder and moved your new
file to this folder.

This is the folder the file should go in:
...\...\modules\Office2003\!SP3KB923618_enu.apm_files

I'm on dialup as well and large downloads I always get using a download manager, I move the file to the given folder, but I always
let APUP create the folder first (you can do it yourself but the name must match exactly the name in the script). I always verify
the file as well or it will get removed and the download will begin again.

So, if you downloaded a complete file (md5hash is a match) and you also downloaded the associated "apm" file for this update, there
might be a detection issue. I don't have Office installed so my module won't load.

I would re-run APUP, it should detect the file in the folder and move on (if you did things correctly), and you should get a "Finish" tab
(without error) to "Exit" APUP. When you run AutoPatcher, it should load the Office 2003 module, and show it as Official. If all these steps
work for you but "No" 923618 appears as an update, this is a detection issue.

Let us know exactly the status of your Office module etc and we will go from there.

Also, it is a good idea to run apup.exe /log (select the module you are having troubles with) to create a log file and post it in here.

Mike

md5 sum was verified correct and file was placed in folder as suggested but AP does not select for installation. I successfully downloaded the file this time using AP with no problems (log OK); file’s md5 verified and AP created the correct folder.

AP still will not list for installation. Perhaps because this is a Service Pack. At least AP does not try to re-download it anymore.

Thanks much for your help.

Will

Edited by WillEllen, 08 May 2009 - 02:25 PM.

[_def_x_]

Quote

AP fails to recognize this file during an install.

Are you saying that AutoPatcher won't install the service pack even though it has been selected by you (this is different than detection)?
Also, I would check the service pack (and nothing else) when trying to install.

Quote

AP still will not list for installation.

Is the file listed in the list of available updates (just not checked for installation), or is it not listed at all (missing/invisible)?

Your posts are a mesh of "download", "detection", and "installation" issues. BTW, using "AP" for both "download" and "installation"
issues is a bit confusing, AutoPatcher is not APUP. I point this out because other people read these posts so it is best to be clear.

Quote

(1) re-run APUP, it should detect the file in the folder and move on..., and you should get a "Finish" tab
(2) When you run AutoPatcher, it should load the Office 2003 module, and show it as Official.
(3) Let us know exactly the status of your Office module etc and we will go from there.

You really didn't answer any of these so it is hard to say what the problem is.

You could open up the associated "apm" file for the service pack and verify the "detection" parameters to see if they conflict with your
system -> [DetectionRegistry] / [DetectionFile] / [OfficeComponents]

Mike

Edited by gUiTaR_mIkE, 09 May 2009 - 03:16 AM.