Vendor MSI over-riding MST feature install levels.
Afternoon, i'm encountereing a problem with applying an mst to a vendor msi.
I have enabled one of the features (changed the install level) to enable it by default.
When run the msi seems to override this install level and deisable it. I've even created another mst without changing any feature settings and enabled the feature using a response transform . When run the same happens.
I've checked the admin and user sequesnces incase there is any differences. Also checked the CA's but cannot see anything making this change. The install level is 100 and the feature is set to 1.
Anyone got any ideas with how vendor msi's cause the above headache?
cheers for any ideas.
I have enabled one of the features (changed the install level) to enable it by default.
When run the msi seems to override this install level and deisable it. I've even created another mst without changing any feature settings and enabled the feature using a response transform . When run the same happens.
I've checked the admin and user sequesnces incase there is any differences. Also checked the CA's but cannot see anything making this change. The install level is 100 and the feature is set to 1.
Anyone got any ideas with how vendor msi's cause the above headache?
cheers for any ideas.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
aogilmor
17 years ago
hey tobes, it may be that this feature is disabled for a reason. make a copy of the MSI and edit the feature directly. Then run it manually and see if you get the same result.
I have seem things like this before - one common scenario is the installshield MSI that requires the installshield binaries to pass the properties.
I have seem things like this before - one common scenario is the installshield MSI that requires the installshield binaries to pass the properties.
Posted by:
AngelD
17 years ago
Could you verify that there's no condition in the Condition table changing the feature level.
Posted by:
TOBES_UK
17 years ago
ORIGINAL: aogilmor
hey tobes, it may be that this feature is disabled for a reason. make a copy of the MSI and edit the feature directly. Then run it manually and see if you get the same result.
I have seem things like this before - one common scenario is the installshield MSI that requires the installshield binaries to pass the properties.
Cheers for the help. I have already changed the feature directly by lowering the install level to the required level to install.
Feature is set to (not changed from the vendors settings)
FAVOUR LOCAL
INSTALL LEVEL 1
NOT VIS
DIS ADV
NOT REQ
0 CONDITIONS.
Still get the same result.
Posted by:
aogilmor
17 years ago
I've packaged this app, and they told me they dont' support extracting the MSI and using a transform. However, they do offer a silent install using the EXE. Ask them for some documentation on that. it was pretty straightforward.
Posted by:
TOBES_UK
17 years ago
ok, big cheers for that info. Prob i've got is I need to deploy the s/w via Radia so going to be a bit tricky.
Posted by:
TOBES_UK
17 years ago
OK thanks for the replies and i'm now getting there slowly. Installs ok with the use of a transform. Only issue now is that deploying from Radia seems to install with different Custom Actions being triggered. Will have to compare the 2 logs (Radia and non-Radia) installs to see what the actual differences are.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.