I have downloaded the Trial Version of InstallAware for evaluation.
Now I finished my first setup with a featue "BUDS SERVER". When tried to launch the installation from commandline with (quite mode)
msiexec /i "buds cs.msi" /qn INSTALLDIR=C:\\Programme\\BUDSSERVER ADDSOURCE=BUDS SERVER /L* "logfile.txt"
I get the MSI Error "2711". Feature name (BUDS SERVER) was not found.
Next I changed the feature name to BUDS_SERVER. When I renamed the feature name within the visual -> feature, I got 2 features, the old one and the new one. Somehow strange but never the less I changed alle existing variables within the script too and then I had the correct changed feature.
I was in hope that the Blank in my first featue name (BUDS SERVER) was not alowed in MSI. I still get the same error.
If I chose not the quite mode means
msiexec /i "buds cs.msi" INSTALLDIR=C:\\Programme\\BUDSSERVER ADDSOURCE=BUDS SERVER /L* "logfile.txt"
I get at first a Message with the same MSI error but I can process the installation.
What do I wrong?
Thank for answering my question.
MSI Cammandline
I got an answer by email but want post it to the forum as well.
>Certainly.
>You can run setups in silent mode with InstallAWARE using the /s >command
>line parameter.
>You can specify logfiles using the /l=<path to log> command line >parameter.
>You can designate the values of pre-defined script variables using the >form
>VARIABLE=VALUE, such as TARGETDIR=C:\\Program.
>All these are parameters to the setup executable (and not the MSI file >using msiexec).
>
>Examples:
>
>1) To install the product with logging into c:\\data,
>
>setup.exe /s /l=c:\\data\\log.txt TARGETDIR=c:\\data
>
>2) To uninstall the product
>
>setup.exe /s MODIFY=FALSE REMOVE=TRUE
>
>You can of course read command line parameters from your installation >script and also drive your setup logic accordingly.
>Certainly.
>You can run setups in silent mode with InstallAWARE using the /s >command
>line parameter.
>You can specify logfiles using the /l=<path to log> command line >parameter.
>You can designate the values of pre-defined script variables using the >form
>VARIABLE=VALUE, such as TARGETDIR=C:\\Program.
>All these are parameters to the setup executable (and not the MSI file >using msiexec).
>
>Examples:
>
>1) To install the product with logging into c:\\data,
>
>setup.exe /s /l=c:\\data\\log.txt TARGETDIR=c:\\data
>
>2) To uninstall the product
>
>setup.exe /s MODIFY=FALSE REMOVE=TRUE
>
>You can of course read command line parameters from your installation >script and also drive your setup logic accordingly.
Stefan
Who is online
Users browsing this forum: Google [Bot] and 32 guests