please help me setup.exe -r and -s question
I ran setup.exe -r to create a setup.iss file for an uninstallation of an application. Then I reinstalled the app. When I am logged in to the pc as an administrator, and run setup.exe -s (the setup.iss I created to record the uninstall is in the same directory as setup.exe) the application silently uninstalls.
When I package this (the setup.iss is in the same directory as setup.exe and the files of the setup program in my sms package share) in sms 2003, and push it out, it dies and never completes the uninstall on my clients. What could I be doing wrong?
It works locally, but not through sms.
I tried running a start /w \\server\share\setup.exe -s -f1 "\\path to iss) ut that didn't work either
Thanks
When I package this (the setup.iss is in the same directory as setup.exe and the files of the setup program in my sms package share) in sms 2003, and push it out, it dies and never completes the uninstall on my clients. What could I be doing wrong?
It works locally, but not through sms.
I tried running a start /w \\server\share\setup.exe -s -f1 "\\path to iss) ut that didn't work either
Thanks
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
There's no realistic way anyone can help you without much more information. Enable MSI logging on a target workstation by pasting the text below into a .REG file and importing it with RegEdit:
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
Once activated this policy will produce log files, prefixed with 'MSI' followed by 4-6 random alphanumeric characters and with a .LOG extension in %SystemRoot%\TEMP. Note that *all* MSI activity is logged, including advertising so may want to turn it off once you're done.
Since the log files have meaningless names, use your favourite Search tool to locate the one for your product. I normally search for the MSI name in a DOS prompt using FIND - it's simple and quick:
FIND /C /I "[name_of_MSI]" MSI*.log
Once located, open the log in your favourite text editor and then find the text 'Return value 3.' (without the quote) as this is the value returned by almost all error conditions. Post the dozen or so lines above and below that entry and we'l try and determine what's happened.
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
Once activated this policy will produce log files, prefixed with 'MSI' followed by 4-6 random alphanumeric characters and with a .LOG extension in %SystemRoot%\TEMP. Note that *all* MSI activity is logged, including advertising so may want to turn it off once you're done.
Since the log files have meaningless names, use your favourite Search tool to locate the one for your product. I normally search for the MSI name in a DOS prompt using FIND - it's simple and quick:
FIND /C /I "[name_of_MSI]" MSI*.log
Once located, open the log in your favourite text editor and then find the text 'Return value 3.' (without the quote) as this is the value returned by almost all error conditions. Post the dozen or so lines above and below that entry and we'l try and determine what's happened.
Posted by:
spartacus
16 years ago
Posted by:
bkelly
16 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.