In brief I have the following issue:

I have an original msi for my product that clients install. I then also have a minor upgrade msp file that clients can install to fix software bugs. But when a repair is performed after a minor upgrade was done, the repair fail to replace missing files that were not included in the minor upgrade msp. So let say a client has installed my product (original msi), and then installed the msp (minor upgrade) at a later stage. Then at some other stage after the msp, he accidentally delete a file that was not patched by the msp, it wouldn't get reinstalled by a repair. When a file that has been patched by the msp, is deleted and a repair is performed, it reinstalls that file perfectly.

It appears to me that the repair only repairs from the msp and not the original msi, and because the file that wasn't patched, is not in the msp, it cannot find the file to repair it. But a file that has been patched by the msp, is in the msp and therefor gets repaired correctly. Could someone please shed some more light on this issue and make suggestions on what I am doing wrong? The error I get in my log looks as follows: MSI (s) (30:78) [10:09:16:583]: Product: MyProduct -- Error 1309.Error reading from file: C:\Documents and Settings\MyUser\Desktop\MyProduct\Installation\Setup\x86\program files\MyProduct\MyFile.dll. System error 3. Verify that the file exists and that you can access it.

Kind regards,

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


IMHO, In this case may be slipstreaming can help you:
1) Do administrative installation with "PATCH=mypath.msp"
3) Upgarde your original package with package (1).
Answered 03/14/2011 by: itolutions
Purple Belt

Please log in to comment