Hi, trying to package the above application. I have applied a number of changes to the vendor .msi via transform that are required for company standards. On the following command executed from a .cmd file I get and error saying I am unathorised to install the app.

msiexec /i msiname.msi TRANSFORMS=mstname.mst

If i run the same syntax using full paths to the files from a command line the install works fine.

There is a launch condition thats been added by me and the table entries APPSEARCH, REGLOCATOR table entries are there and the reg entries are present on the PC the app is being installed on so it should install. There are also no condition on the Launchconditions standard action in the sequence.

I've checked the log and the install is definately failing at the launch condition which is added via transform and must be left to meet the company packaging standards. Any suggentions on finding a solution?
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
As the launch condition is preventing an installation while non-full path is used it could be interesting to know what you have as the LaunchCondition condition and related AppSearch entries.
Answered 02/12/2008 by: AngelD
Red Belt

Please log in to comment
0
Ok Thanks for the reply, I'll post up the actual table entries tomorrow as I'm at home now.

FYI The final MST is a result of 3 inhouse MST templates being merged via an inhouse (VB) company application to a bnewly created UI MST.

The vendor .msi was packaged using Wise. I'll also check tomorrow to see if the Appsearch action is before the Launchcondition action in the sequesnce as IIRC WPS defaults to them being the other way round and Appsearch is needed 1st in the sequence. Mind you this would affect the installation using full-paths too.
Answered 02/12/2008 by: TOBES_UK
Senior Purple Belt

Please log in to comment
0
I have now solved this. The cause was as suspected. The vendor .msi created in WPS had set the Launchcondition action to a low sequence and the merged inhouse .mst had applied the Appsearch action after the Launchcondition. Changed Appsearch to be actioned before Launchcondition and it installs.
Answered 02/13/2008 by: TOBES_UK
Senior Purple Belt

Please log in to comment
0
Copy your 'Windows Application' template and make that sequence change to the copy, then use THAT for future projects. I'm still in the dark as to why WPS's default is the way it is. BTW, you need to copy the template because future updates may walk over changes made to the default. One of the INIs (can't recall which, but it'll be obvious) controls which template gets used so edit that, too (having made a back-up, of course)
Answered 02/13/2008 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

Copy your 'Windows Application' template and make that sequence change to the copy, then use THAT for future projects. I'm still in the dark as to why WPS's default is the way it is. BTW, you need to copy the template because future updates may walk over changes made to the default. One of the INIs (can't recall which, but it'll be obvious) controls which template gets used so edit that, too (having made a back-up, of course)


Cheers :)
Answered 02/14/2008 by: TOBES_UK
Senior Purple Belt

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