/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Can't find source when running modify/change action

10/06/2011 1568 views
Hi all. I am having an issue when performing a modify/change action. The steps I am following are:

- install msi
- in ARP, modify the install and add a feature. no issues here
- install patch
- in ARP, modify the install and add a feature, the install looks for an uncompressed file which doesn't exist as my original install is compressed, error 1308/1309.

Any thoughts as to why this might happen? Please let me know if I can provide any info to help troubleshoot. Thank you!
0 Comments   [ + ] Show comments

Comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

0
How are you making the modifications? To the MSI or are you using an MST. If your using an MST, it probably made a CAB file or it is looking for the files. Either way, both must be in the same directory as the MST.
Answered 10/06/2011 by: jmaclaurin
Third Degree Blue Belt

0
Thanks for the reply. I am modifying the msi via a patch (msp). Although a patch is made up internally as a mst and a cab, I am not using an mst directly. The issue is after I apply the patch and try to perform a modify and change features. The "modify" I am performing in Add/Remove Programs (Programs and Features) is sometimes called Change and sometimes called Modify, not sure why there is a difference :)
Answered 10/06/2011 by: barron35
Yellow Belt

0
Enable Windows Installer logging in verbose mode. The resulting log will help you identify the recalcitrant component.
Answered 10/07/2011 by: VBScab
Red Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ