silent install issue
Hi guys,
I’m having a issue when trying to silently install a application, here is the problem:
When trying to install PensionsLite v1.03 through a command line shortcut the vendor .msi installs up to a point, at this point it launches another install (vfrun61ai) which does not install silently. To get past this you have to run through the dependent install manually, which obviously defeats the purpose of the silent install.
I have tried the following:
Install vfrun61ai before running the msi. This failed
Remove the dependency within the msi by applying a mst. This corrupted the msi.
So my question is has anyone seen this before and how did they get round the problem?
All help is much appreciated.
Luke
I’m having a issue when trying to silently install a application, here is the problem:
When trying to install PensionsLite v1.03 through a command line shortcut the vendor .msi installs up to a point, at this point it launches another install (vfrun61ai) which does not install silently. To get past this you have to run through the dependent install manually, which obviously defeats the purpose of the silent install.
I have tried the following:
Install vfrun61ai before running the msi. This failed
Remove the dependency within the msi by applying a mst. This corrupted the msi.
So my question is has anyone seen this before and how did they get round the problem?
All help is much appreciated.
Luke
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Install vfrun61ai before running the msi. This failedWhat failed? Presumably you mean that it failed to see that the dependency was installed already and didn't stop the execution of the extra install? My guess would be that you left in the Custom Action which executes it.
Remove the dependency within the msi by applying a mst. This corrupted the msi."corrupted the msi" how? More likely, you have applied an incorrect or incomplete change via the transform.
Find the CA which runs the install by executing the MSI non-silently and monitoring the log for when the extra install starts. Once you know its name, apply an impossible-to-meet condition (I normally use 0=1) to its execution via your transform. Then make sure your deployment successfully runs the dependency first. You may want to add your own check to your transform so that your package fails "cleanly" if the dependency is missing.
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.