Help with hidden install
Hi Guys,
Im after some advice. I have a vendor msi which i've created a mst and running it through a command line shortcut. The issue is when running the silent command line half way through the installation the application launches a install called "virtual fotress runtime file installation" ("vfrun61ai" for short) and you have to manually run through this install before it will compete the origanal install.
I've tried installing "vfrun61ai" before running my vendor msi but it still wants to run through the install.
I've also removed it from the install sequence but that just throws up a error on install.
has anyone see this and managed to get round it with have to run a script or simalar?
Any help is much appreciated.
many thanks,
Luke
Im after some advice. I have a vendor msi which i've created a mst and running it through a command line shortcut. The issue is when running the silent command line half way through the installation the application launches a install called "virtual fotress runtime file installation" ("vfrun61ai" for short) and you have to manually run through this install before it will compete the origanal install.
I've tried installing "vfrun61ai" before running my vendor msi but it still wants to run through the install.
I've also removed it from the install sequence but that just throws up a error on install.
has anyone see this and managed to get round it with have to run a script or simalar?
Any help is much appreciated.
many thanks,
Luke
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
Luke,
I would suggest that instead of removing the nested install from the sequence, you actually condition the Custom Action that executes it with an impossible to meet condition (1=2 for example). This will have a lot less impact on the installer and might avoid the errors you're getting.
If this does not help, the next step would be to dive into the installer logs to identify where exactly the installation fails. This might point you in the direction of other actions that depend on the nested install having run before.
Rgds,
PJ
I would suggest that instead of removing the nested install from the sequence, you actually condition the Custom Action that executes it with an impossible to meet condition (1=2 for example). This will have a lot less impact on the installer and might avoid the errors you're getting.
If this does not help, the next step would be to dive into the installer logs to identify where exactly the installation fails. This might point you in the direction of other actions that depend on the nested install having run before.
Rgds,
PJ
Posted by:
LukeHarte0103
13 years ago
Thanks for getting back to me.
I managed to get it work. i removed the custom action that was calling the install. I then packaged the "vfrun61ai" application to come down as a dependency for PensionsLite. Deployed it down to a test machine and all see to be fine.
Thanks again for the help!!!
I managed to get it work. i removed the custom action that was calling the install. I then packaged the "vfrun61ai" application to come down as a dependency for PensionsLite. Deployed it down to a test machine and all see to be fine.
Thanks again for the help!!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
