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.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

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

Answers

0
what does a plain msiexec /a [PATH\MSI] do?

i think my officeXP AIP patch commandline went something like this... change appropriately.

msiexec /p [PATH\MSP] /a [PATH\MSI] SHORTFILENAMES=TRUE /qb!- /L*v [PATH\LOG]
Answered 08/18/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
plain msiexec /a generates "Installation does not support Administrative install"
Answered 08/18/2009 by: ogeccut
Black Belt

Please log in to comment
0
any logging? what's in the log file? have u looked @ the MSI structure... is it a wrapper that is trying to launch a separate installer? is this mercury/hp loadrunner by any chance?
Answered 08/18/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
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.


msiexec.exe /update filename.msp /qn
Answered 08/18/2009 by: elgwhoppo
Senior Purple Belt

Please log in to comment
0
I seem to recall seeing a similar post a while back. Is there an AdminInstallSequence table? If not, I suspect you'll see this message. It's easy enough to build one in but it involves...directly editing the MSI. In this case, I think it's justified but, as usual, make sure you have a back-up copy.
Answered 08/18/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks for looking into it.

Yes the application is a load runner i think i have it in the first post.

I might have to deliver and vendor msi with msi first and then try to apply a patch.

I will look into AdminInstallSequence table to see if i can enable admin install.

Thank you.
Answered 08/19/2009 by: ogeccut
Black Belt

Please log in to comment
0
My apologies. Please correct 'AdminInstallSequence' to 'AdminExecuteSequence' or 'AdminUISequence'.
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
Hi Michael,
see: http://www.appdeploy.com/messageboards/fb.asp?m=25423
There i have described, how to solve this.
Good luck.
Regards, Nick
Answered 08/21/2009 by: nheim
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity