When does MSP fails to update MSI?
Hello,
I am updating adobe reader 9 with 9.1.3.
Current situation is that
- Adobe reader 9 is installed in PC already
- and I need to adjust some registry setting of main installation(MSI) + apply patch 9.1.3 via SMS.
When I apply 9.1.3 "alone" via SMS, it updates well. My only problem is how to adjust setting of main installation.
To adjust setting, I tried several methods as below.
1. Adjusted Adobe's 9.1.3 Msp
--> it failed as soon as I apply saying "unexpected termination".
possible reason is that digital certificate becomes invalid.
2. I created my own patch based on msi and applied "my own msp + 9.1.3"
--> failed exactly the same way with #1. I wonder what could be the reason for failure. is it because Adobe set something in the main package not to be updated via UNKNOWN patch?
Pls. help me :)
Ps) As a workaround for adjusting some registry value.
- We used Vbscript and worked fine but when user repairs via Add/Remove programs
old registry value came back from msi. (shortcut repair is OK)
- As a last resort, I can make AIP but then I have remove and install whole package...
I am updating adobe reader 9 with 9.1.3.
Current situation is that
- Adobe reader 9 is installed in PC already
- and I need to adjust some registry setting of main installation(MSI) + apply patch 9.1.3 via SMS.
When I apply 9.1.3 "alone" via SMS, it updates well. My only problem is how to adjust setting of main installation.
To adjust setting, I tried several methods as below.
1. Adjusted Adobe's 9.1.3 Msp
--> it failed as soon as I apply saying "unexpected termination".
possible reason is that digital certificate becomes invalid.
2. I created my own patch based on msi and applied "my own msp + 9.1.3"
--> failed exactly the same way with #1. I wonder what could be the reason for failure. is it because Adobe set something in the main package not to be updated via UNKNOWN patch?
Pls. help me :)
Ps) As a workaround for adjusting some registry value.
- We used Vbscript and worked fine but when user repairs via Add/Remove programs
old registry value came back from msi. (shortcut repair is OK)
- As a last resort, I can make AIP but then I have remove and install whole package...
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
This subject has been done to death here already. Please read the recent posts concerning AR, particularly one where the poster says he skipped over 9.1.1.
Posted by:
faithkim
14 years ago
Hi, Vbscab,
My explanation was not enough. In fact,
I made AIP patched upto 9.1.2 and this AIP version is installed on Client. Now I have 2 things to do.
- 1st : applying 9.1.3 to client via SMS --> it works fine
- 2nd : need to change preference setting via adjusting registry key
(my users want to enable "display pdf in browerser" option)
To achieve 2nd task, I tried 2 methods.
1. I included required registry key changing 9.1.3 msp directly to do 2 above tasks in one shot but failed
--> whenever I change any content of 9.1.3, it fails to install.
2. So, I just deployed 9.1.3 as it is and made my own msp based on 9.1.2 AIP
--> this is also failed, showing the same error message like #1 case.
I wonder how i can change setting of adobe via Patch method in this case....
Thanks in advance.
My explanation was not enough. In fact,
I made AIP patched upto 9.1.2 and this AIP version is installed on Client. Now I have 2 things to do.
- 1st : applying 9.1.3 to client via SMS --> it works fine
- 2nd : need to change preference setting via adjusting registry key
(my users want to enable "display pdf in browerser" option)
To achieve 2nd task, I tried 2 methods.
1. I included required registry key changing 9.1.3 msp directly to do 2 above tasks in one shot but failed
--> whenever I change any content of 9.1.3, it fails to install.
2. So, I just deployed 9.1.3 as it is and made my own msp based on 9.1.2 AIP
--> this is also failed, showing the same error message like #1 case.
I wonder how i can change setting of adobe via Patch method in this case....
Thanks in advance.
Posted by:
funnyproffy2
14 years ago
You can't edit an MSP directly. An MSP is a Windows Installer Patch file which
represents the delta between the target and update images. E.g. Orca provides the
ability to view the changes made by a MSP.
If you need to alter what an MSP does, you will have to rebuild the patch itself
(using tools like patchwiz.dll and msimsp.exe) by first making the necessary
change in the update image. Have a look at:http://msdn.microsoft.com/en-us/library/aa370324(VS.85).aspx
for more info about msimsp.exe
represents the delta between the target and update images. E.g. Orca provides the
ability to view the changes made by a MSP.
If you need to alter what an MSP does, you will have to rebuild the patch itself
(using tools like patchwiz.dll and msimsp.exe) by first making the necessary
change in the update image. Have a look at:http://msdn.microsoft.com/en-us/library/aa370324(VS.85).aspx
for more info about msimsp.exe
Posted by:
anonymous_9363
14 years ago
Exactly right.
So, faithkim, to make your change, you need to create and apply a transform to the 9.1.3 MSI.
So, faithkim, to make your change, you need to create and apply a transform to the 9.1.3 MSI.
Posted by:
faithkim
14 years ago
Thanks guys.
I will try Vbscab's proposal first (Funnyporffy2, i will try yours later :) )
By the way, one more advice please. I wrote in previous post as below.
2. So, I just deployed 9.1.3 as it is and made my own msp based on 9.1.2 AIP
--> this is also failed, showing the same error message like #1 case.
Here I didn't alter 9.1.3 msp directly, and I said I made my own msp.
I made this msp via Quick patch in AdminStudio with version 9.1.3.1 based on "9.1.2 AIP". and install command was msiexec /p... 9.1.3 msp; 9.1.3.1 msp /qn
but failed with same error. Any advice for the possible reason for failure? is it because 9.1.3.1 is based on 9.1.2 AIP (must be 9.1.3 AIP??)
I will try Vbscab's proposal first (Funnyporffy2, i will try yours later :) )
By the way, one more advice please. I wrote in previous post as below.
2. So, I just deployed 9.1.3 as it is and made my own msp based on 9.1.2 AIP
--> this is also failed, showing the same error message like #1 case.
Here I didn't alter 9.1.3 msp directly, and I said I made my own msp.
I made this msp via Quick patch in AdminStudio with version 9.1.3.1 based on "9.1.2 AIP". and install command was msiexec /p... 9.1.3 msp; 9.1.3.1 msp /qn
but failed with same error. Any advice for the possible reason for failure? is it because 9.1.3.1 is based on 9.1.2 AIP (must be 9.1.3 AIP??)
Posted by:
anonymous_9363
14 years ago
Any advice for the possible reason for failure?Yes! Use a transform for changes like this, not a patch.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.