3 Replies Latest reply on Jun 1, 2012 3:00 AM by Gilles Portal

    Setup.exe failing with Installshield switches

    jpozucek Apprentice

      I am trying to push a package based on InstallShield that uses a setup.iss response file.


      I create a distribution package based on  \\servername\path\setup.exe with the following switches on the Install/Uninstall options screen:


      /s /f1"\\servername\path\setup.iss"  (quotes are required)


      This fails with and "Unknown Error Code".  If I remove the switches the setup.exe runs but it requires user input.


      I've even tried creating a batch file and using a batch file distribution package but it still fails.  Saying that sdclient.exe or the program was terminated at the client. 


      Nothing remotely helpful in the logs in either case.


      However if I run the batch file directly it completes using the setup.iss file.


      Does LANDesk support InstallShield switches?  I need to push this to several hundred devices and so far have not had luck with one.


      Any suggestions would be welcome.


      ~ Jim

        • 1. Re: Setup.exe failing with Installshield switches

          If the install is running under the local system account, then it won't be able to connect to the UNC path.


          If the setup.iss file is in the same directory as the setup.exe, then just leave the path out, for example:

          /s /f1"setup.iss"

          • 2. Re: Setup.exe failing with Installshield switches



            when you use software distribution avoid scripts or parameters that refers to network path.

            If you need there files add them them to the Additional Files section so they are downloaded to the client an everything will be local.

            When a Software Distribution task runs it normally runs under LocalSystem with none or limited access to network resources.



            • 3. Re: Setup.exe failing with Installshield switches
              Gilles Portal Apprentice

              I m agree whith that. I use a lot of these install features, and the issue is always a path problems. The best way for me, is to create the iss file from a sample computer, and from the landesk deployment path, (C:\program files\Landesk\....) and test it on this computer. If it is working fine copy the binaries on the correct path on your packages server, and then create the packages. It will work fine too when deploying the packages. Be care of the numbers of space car in the command line.