Creating a silent install of IBM WebSphere TX Design Studio using a Response file and creating a log with this command:

C:\IBMWTXDS\Setup.exe -s -f1C:\MyDir\IBMWTXDesignStudio.iss -f2C:\MyLogs\IBMWTXDS-ISS.log

It works fine when I am logged in and run the command. Then I try to use our Deployment Tool, Marimba, to install it. I am logged off the PC and it should run using the System Account. It creates the IBMWTXDS-ISS.log file, but never finishes the install. From a different PC I browse to the log file and open it. There are a few lines, but no ReturnCode listed. A few minutes later the install finishes and I see in the log file a ReturnCode of 0. Which means good.

The application installs sucessfully, however it does not seem to finish until I remotely open and close the log file. What the heck? Why would the install start a log file, but then not finish until I remotely open and close the log file? My next step is to try it w/o a log file, but that is nonsense.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I tried it without a log file, same result. Maybe this is just a timing issue.

I'm using Wise Script to script the kick-off of the Setup.exe install and using Pause statments in it to wait for the application to finish installing and then checking for sucess. Checking the Wait check-box in Wise does not work. Perhaps the Pause statements in my Wise Script are causing the Setup.exe install of the application to pause also. I have not had this problem before, but this may be an unusual situation where it is happening. I'll need to find a different way for my for my Wise script to pause while the Setup.exe finishes its installation and then check for sucess.
Answered 02/11/2011 by: zartan24
Senior Yellow Belt

Please log in to comment
I had faced similar issue in one of the wrapper package. WiseScript doesn't wait for the target thread (setup.exe) to complete.
Are you using MSI wrapper or just the WiseScript executable through Marimba?
Answered 02/14/2011 by: WiseAppPackager
Purple Belt

Please log in to comment
Instead of using the WiseScript Pause command, my Friend wrote this WiseScript code to ping to the Local Host in a Hidden window. Each ping is about 1 second and he does 60 of them. _ISDel.exe is the process running while the program is installing.

Set Variable ProcessInUse = in-use
while ProcessInUse = in-use
Check In-Use File C:\IBM\_ISDel.exe and put value into ProcessInUse
If ProcessInUse = in-use, then write "Still running" to log.
Execute program in hidden window: %sys32%\cmd.exe /c ping -n 60 > nul

I'm using a WiseScript EXE thru Marimba. WiseScript does not wait for the install to finish, but it does wait for the uninstall to finish. Weird. The solution my friend gave me worked. Moving forward...
Answered 02/15/2011 by: zartan24
Senior Yellow Belt

Please log in to comment