Applying a patch to the msi
I have a vendor msi "LoadRunner 9.5" and a vendor msp "9.5.1" I am trying to to apply that patch to a vendor msi using
msiexec /a <original .msi file and location> /p <.msp file
But when trying to run admin install i get that "Installation does not support Administrative install"
Is there any way around it?
Thank you.
msiexec /a <original .msi file and location> /p <.msp file
But when trying to run admin install i get that "Installation does not support Administrative install"
Is there any way around it?
Thank you.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
kiptek
14 years ago
Posted by:
ogeccut
14 years ago
Posted by:
kiptek
14 years ago
Posted by:
elgwhoppo
14 years ago
I wrote a wise script to do this exact thing for QTP 9.5. I could send you the WSE via email if you're interested. In hindsight, it's kind of an ugly script. I can do much better now that I did back then. All the QTP .msp files place a hotfix readme in %PROGRAM_FILES%\HP\QuickTest Professional\HotfixReadmes, so I keyed off that. Here's an example of my logic:
If file "%PROGRAM_FILES%\HP\QuickTest Professional\HotfixReadmes\QTP_00539.txt" doesn't exist
msiexec.exe /update patch_00547.msp /qn
End if
Make sure the EXE and msp files are in the same directory. My wise script is a bit more detailed, and actually kills QTP if it's not there and makes sure that the ISScript engine DCOM components is set to run with launching user instead of interactive, sometimes that can mess up the install.
I think the short answer you may be looking for is this, unless you are trying to slipstream the patch into the installation.
If file "%PROGRAM_FILES%\HP\QuickTest Professional\HotfixReadmes\QTP_00539.txt" doesn't exist
msiexec.exe /update patch_00547.msp /qn
End if
Make sure the EXE and msp files are in the same directory. My wise script is a bit more detailed, and actually kills QTP if it's not there and makes sure that the ISScript engine DCOM components is set to run with launching user instead of interactive, sometimes that can mess up the install.
I think the short answer you may be looking for is this, unless you are trying to slipstream the patch into the installation.
msiexec.exe /update filename.msp /qn
Posted by:
anonymous_9363
14 years ago
Posted by:
ogeccut
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
nheim
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.