custom install
hi all,
i have a vendor msi which i've done a mst. but i can't install the features i want.
when i run it manually, in the dialog, there is a treeview where i can select the options i want to install. usually, i note the features name and put them on the command prompt with ADDLOCAL=...
but this package is not working. if i run it manualy, it installs fine. but from the command prompt with /qb, i'm getting prompted that some dll could not register.
here's the command line i tried;
msiexec /i Q6045Install.msi TRANSFORMS=QISoftLimitedQIS6045EN.mst ADDLOCAL=QIS,Utilities /qb
how can i fix this? someone has a clue?
thanks!
i have a vendor msi which i've done a mst. but i can't install the features i want.
when i run it manually, in the dialog, there is a treeview where i can select the options i want to install. usually, i note the features name and put them on the command prompt with ADDLOCAL=...
but this package is not working. if i run it manualy, it installs fine. but from the command prompt with /qb, i'm getting prompted that some dll could not register.
here's the command line i tried;
msiexec /i Q6045Install.msi TRANSFORMS=QISoftLimitedQIS6045EN.mst ADDLOCAL=QIS,Utilities /qb
how can i fix this? someone has a clue?
thanks!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
captain_planet
13 years ago
Darkfang refers to the Install Level of the Windows Installer. INSTALLLEVEL can be specified in the Property table as a numeric (Integer) value. A feature is installed only if the feature level value (contained in the 'Level' column of the feature table) is less than or equal to the current install level. If INSTALLLEVEL is not specified, the install level defaults to 1.
If setting the INSTALLLEVEL property does not work, you may need to check your InstallUISequence for important Custom Actions which you're skipping. Using the /qb switch in your command line will skip the InstallUIsequence. If you run it without the /qb switch and it works without error, this could be why. In which case you may need to run the 'skipped' action in the InstallExecuteSequence instead. This should get you started with your investigation anyhow....
If setting the INSTALLLEVEL property does not work, you may need to check your InstallUISequence for important Custom Actions which you're skipping. Using the /qb switch in your command line will skip the InstallUIsequence. If you run it without the /qb switch and it works without error, this could be why. In which case you may need to run the 'skipped' action in the InstallExecuteSequence instead. This should get you started with your investigation anyhow....
Posted by:
rmroshan
13 years ago
Create a log file while installing in UI mode and verify the value of ADDLOCAL property and pass the same while installing in /qb or /qn. and also verify the Feature level and Install Level values as suggested above
Posted by:
timmsie
13 years ago
Another thing to look out for is entries in the "condition" table:
http://msdn.microsoft.com/en-us/library/aa368014(VS.85).aspx
I've had a vendor app recently where I changed InstallLevel and tried ADDLOCAL but couldn't get the features I wanted installed and it was because of entries in the condition table
http://msdn.microsoft.com/en-us/library/aa368014(VS.85).aspx
I've had a vendor app recently where I changed InstallLevel and tried ADDLOCAL but couldn't get the features I wanted installed and it was because of entries in the condition table
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
