merging .msp with .msi
When i type this commond,
msiexec /A "C:\ap\adobe_acrobat_08\Extracted source\AcroStan.msi" /P "C:\ap\adobe_acrobat_08\Extracted source\AcrobatUpd810_efgj_incr.msp" SHORTFILENAMES=TRUE
I m getting error as:
Upgrade patch cannot be installed by windows service installer bcz the program to be upgrade may be missing or the upgrade patch may update a different version of program.
could you please help me in this regard.
msiexec /A "C:\ap\adobe_acrobat_08\Extracted source\AcroStan.msi" /P "C:\ap\adobe_acrobat_08\Extracted source\AcrobatUpd810_efgj_incr.msp" SHORTFILENAMES=TRUE
I m getting error as:
Upgrade patch cannot be installed by windows service installer bcz the program to be upgrade may be missing or the upgrade patch may update a different version of program.
could you please help me in this regard.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
The filenames etc look OK but I wonder whether specifying the property SHORTFILENAMES may be causing the problem? I don't know for sure, as I've never tried it (it doesn't really make sense to me for an admin install, and especially not when patching an admin install).
Posted by:
AngelD
16 years ago
Try doing this in two steps.
First do an admin install
Second apply the patch on the admin install MSI
May I ask why you want to create the admin install with short file/directory names as (from the SDK):
Long names are used by the installer if the SHORTFILENAMES property is not set and the target volume supports long names. Short names are used by the installer if the target volume does not support long names.
First do an admin install
Second apply the patch on the admin install MSI
May I ask why you want to create the admin install with short file/directory names as (from the SDK):
Long names are used by the installer if the SHORTFILENAMES property is not set and the target volume supports long names. Short names are used by the installer if the target volume does not support long names.
Posted by:
anonymous_9363
16 years ago
Good catch, Kim. I assumed that the admin install had already been done and the OP was trying to patch it but, as you point out, this error would be displayed if the admin install wasn't present already.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
