Setup.exe -s -SMS
I have an application that has an InstallShield installer for it. I have run Setup.exe -r and created my Setup.iss file. But, when I then try to run this in silent mode it fails.
I run setup.exe -s -SMS and nothing happens. If I run Setup.exe -SMS it does launch the apps so it is the -s that is killing it. I have tried running this from an unc and from a mapped drive letter and neither one works. I have Admin rights on my machine as well so I know tha is not the issue.
I ran it and forced Setup.exe to create a log file and all the log file has in it is this:
[InstallShield Silent]
Version=v6.00.000
File=Log File
[ResponseResult]
ResultCode=-5
And from what I have read ResultCode=5 means I don't have a response file. But I did create a response file and I placed this setup.iss file in the exact same location as the Setup.exe file (which has always worked for me in the past)
So why would the -s silent switch not work?
Thanks.
Thanks.
I run setup.exe -s -SMS and nothing happens. If I run Setup.exe -SMS it does launch the apps so it is the -s that is killing it. I have tried running this from an unc and from a mapped drive letter and neither one works. I have Admin rights on my machine as well so I know tha is not the issue.
I ran it and forced Setup.exe to create a log file and all the log file has in it is this:
[InstallShield Silent]
Version=v6.00.000
File=Log File
[ResponseResult]
ResultCode=-5
And from what I have read ResultCode=5 means I don't have a response file. But I did create a response file and I placed this setup.iss file in the exact same location as the Setup.exe file (which has always worked for me in the past)
So why would the -s silent switch not work?
Thanks.
Thanks.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
13 years ago
Posted by:
icbrkr
13 years ago
Posted by:
mhsl808
13 years ago
I figured it out. It was a rights issue on the server where I had the source files. I moved my source files to a different share and then it all worked. What is odd is the log file, which pointed to the response file as the issue. The setup.exe kicked off from this same server yet it did not like the .iss file. Very odd but it is all working now.
Thanks.
Thanks.

so that the conversation will remain readable.