MSP error
I am having trouble patching Adobe Acrobat Reader 7.0.8. Created transform using Adobe provided transform. Installed using msiexec /i "adobe.msi" Transforms=adobe.mst /qb. Installs fine. But when I run msiexe /p "rdr708.msp" REINSTALLMODE=OMUS REINSTALL=ALL /qb, I get "The upgrade patch cannot be installed by the windows installer.....". However if I install by just clicking on msi the patch works. Do i have to patch the msi using /a approach? Shouldn't I just be able to run the msp after installing the msi?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
AngelD
18 years ago
ORIGINAL: aogilmor
I have noticed that some vendors do not create proper administrative installs, so don't be too discouraged if all this doesn't work for you. just do the install and patch sequentially on the client side - . I have not tried adobe 7 yet myself.
If AdminUISequence and/or AdminExecuteSequence tables are missing the administrative install will not work in UI and/or not UI, so by importing these fromout an MSI template should solve the admin-install.
Posted by:
aogilmor
18 years ago
first, looks like you may have a typo. "msiexe"
also, /update is now used for Windows Installer (3.0 and above) (/p is for 2.0 and below)
If possible, you SHOULD run the msp against the administrative or network source ( /a) That way when a new client is installed they will get the patch as well - no need to run 2 setups.
also, /update is now used for Windows Installer (3.0 and above) (/p is for 2.0 and below)
If possible, you SHOULD run the msp against the administrative or network source ( /a) That way when a new client is installed they will get the patch as well - no need to run 2 setups.
Posted by:
chandlerbing
18 years ago
yeah, that's probably a typo. Anyways, I did an administrative install. msiexec /a "adobe reader 7.0.8.msi". Then I did msiexec /update "rdr708.msp" /a "<path to msi file>" and I still that damn error. Clean vm image so don't know if that's an issue.
Posted by:
aogilmor
18 years ago
that is curious. append /l*v <log file path> to enable verbose logging and see what you come up with. also, msiexec /a "adobe reader 7.0.8.msi" should prompt you for a network target path, which should generate a new administrative install MSI. You want to apply the patch to the target MSI, not the original "adobe reader 7.0.8.msi" that you created the administrative install from.
I have noticed that some vendors do not create proper administrative installs, so don't be too discouraged if all this doesn't work for you. just do the install and patch sequentially on the client side - . I have not tried adobe 7 yet myself.
let us know how it works. just mind the syntax (LOL).
OG
I have noticed that some vendors do not create proper administrative installs, so don't be too discouraged if all this doesn't work for you. just do the install and patch sequentially on the client side - . I have not tried adobe 7 yet myself.
let us know how it works. just mind the syntax (LOL).
OG
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.