szerby1.5524918496505088E12 asked a question.
My install is very simple - no custom dialog boxes.
But when I do "setup /r" there is no ISS file recorded anywhere on the hard drive.
I tried "setup /r /f1"C:\users\xxx\desktop\setup.iss" just in case this was a windows 7 security issue. Still no luck.
Any ideas? Is this a limitation the express edition?
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
To run an Express installation silently, all you need to do is type the following at the command line:
msiexec /i Product.msi /qn
If your release settings include Setup.exe, you can run the following command:
Setup.exe /s /v"/qn"
I hope that helps.
My build is a single setup.exe
The Setup.exe /s /v"/qn" command makes the windows cursor flash a little, but no install takes place. IS there a log file somewhere that can help tell me what is happening? Is there a flag or another setting in Installshield I need to set?
setup.exe /s /v"/l*v \"c:\My Log File.txt\" /qn"
For more information on logging and the available command-line parameters, see the "Setup.exe" help topic in the InstallShield Express Help Library (available when you press F1 from within the InstallShield Express Edition). It's available in the Reference section of the help (Reference > Command-Line Tools > Setup.exe).
I'm not sure where you found out about the response files for silent InstallScript installations, but it is not documented in the InstallShield Express Edition Help Library. That help system does have a help topic called "Upgrading to the Premier or Professional Editions of InstallShield"; it lists functionality that is not available in the Express edition, but is available in the Premier edition or is available in both the Premier and Professional editions. Although that help topic doesn't list silent response files specifically, it does list that InstallScript support is available only in the Premier and Professional editions.
I hope that helps.
Windows ® Installer. V 5.0.7601.17514
msiexec /Option [Optional Parameter]
Install Options
Installs or configures a product
/a
Administrative install - Installs a product on the network
/j [/t ] [/g ]
Advertises a product - m to all users, u to current user
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log
Equivalent of /l*
Update Options
/update [;Update2.msp]
Applies update(s)
/uninstall [;Update2.msp] /package
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v]
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
setup.exe /s /v"/l*v \"c:\My Log File.txt\" /qn"
setup.exe /s /v/qn /debuglog"C:\users\scott\desktop\silent.log"
With Win7 you need to save to a directory with proper permissions.
The last statement in the log is:
Setup returning 1603
- My application requires .net 4.0 and the install program handles detection and installation just fine. But it looks like it is failing in silent mode. The computer
I am testing on already has .Net 4.0 installed.
The log file also shows this:
"Skipping prerequisite 'Microsoft .NET Framework 4.0 Full.prq' because it was installed before the reboot"
Where next?
I tried changing the directory just in case with the same result.
setup.exe /s /v"*/*l*v \"c:\users\scott\desktop\My Log File.txt\" /qn"
setup.exe /s /v"/l*v \"c:\users\scott\desktop\My Log File.txt\" /qn"
Logfile attached.
" MSI (s) (D0:38) [10:13:41:521]: Product: Snap Will -- Error 1925. You do not have sufficient privileges to complete this installation for all users of the machine. Log on as an administrator and then retry this installation. "
When Windows Installer doesn't display the installation's UI, it also doesn't provide the UAC dialogs or elevate. To resolve the error, launch the installation silently from an elevated Command Prompt window. (Right-click the shortcut for the Command Prompt and then click Run as administrator. Then use the same command line to launch the setup.)