SW Test Automation Framework

I'm not familiar with the workings of Installshield, but by the sound of =
the problem I say my first feeling is that you may be missing some =
environmental variables? Check the internal staf variables against the =
one in windows, and if you miss something out use the env parameter.
=20
Best wishes,
Jon
=20
________________________________
  Jon Bj=F6rkeb=E4ck
  Systems designer, R&D
  Mobeon AB, http://www.mobeon.com

	-----Original Message-----
	From: Tom H Smith [mailto:tomsmith@...
	Sent: den 17 juni 2004 15:52
	To: staf-users@...
	Subject: [staf-users] Using STAF to do remote silent InstallShield =
installs
=09
=09

	I'm trying to use STAF to install a product that uses InstallShield. =
I'm using=20
	the silent-install-with-a-response-file method. It's failing, only on =
Windows.=20
=09
	The first command I tried was:=20
=09
	        # staf <hostname> process start command "<full path to =
InstallShield executable>" \=20
	               parms "-silent -options <full path to response file>" =
wait sameconsole \=20
	               returnstdout returnstderr=20
	               =20
	The InstallShield executable started up, the embedded jre was extracted =
to a subdirectory=20
	of C:\Temp, and it stopped. It just hung. Forever.=20
=09
	The install works fine on the Windows box[es] when run from the command =
line locally=20
	and when run locally with the command line wrapped in a batch file.=20
=09
	It worked perfectly on AIX, Linux, Solaris (8, the only one I tried), =
and HP-UX.=20
=09
	I also tried (on Windows):=20
=09
	        * All commands were, of course, on one line.=20
=09
	        1. Wrapping the command and options in a batch file and calling =
that via:=20
	       =20
	                    # staf <hostname> process start command shell parms =
"<full path to batch file containing \=20
	                       command line>" wait sameconsole returnstdout =
returnstderr=20
	                       =20
	        2. Using STAF to call a shell and passing it the entire command =
line:=20
	       =20
	                # staf <hostname> process start command shell parms =
"<full path to InstallShield executable> \=20
	                       -silent -options <full path to response file>" =
wait sameconsole returnstdout returnstderr=20
	                       =20
	        3. Wrapping the command line in some VBscript to run it via =
WMI, pushing the VBscript out to=20
	           the victim machine, and calling the VBscript from STAF:=20
	           =20
	           # staf <hostname> process start command cscript parms =
"//nologo C:/install.vbs" \=20
	                  wait sameconsole returnstdout returnstderr=20
	                 =20
	           Here's the VBscript:=20
	           =20
	                SET Services =3D getobject("winmgmts:root\cimv2")=20
=09
	                SET oProcess =3D Services.Get("Win32_Process")=20
	               =20
	                SET oInParams =3D =
oProcess.Methods_("Create").InParameters.SpawnInstance_=20
	                oInParams.CommandLine =3D "<full path to InstallShield =
executable> -silent -options <full path to response file>"=20
	               =20
	                SET oOutParams =3D Services.ExecMethod( =
"Win32_Process", "Create", oInParams)=20
	               =20
	                IF oOutParams.ReturnValue =3D 0 THEN=20
	                    wscript.echo "Create method executed successfully." =

	                ELSE=20
	                    IF IsNull(oOutParams.ReturnValue) THEN=20
	                        wscript.echo "Create method failed to execute." =
 =20
	                    ELSE=20
	                        wscript.echo "Create method executed but had =
error " & "0x" & HEX(oOutParams.ReturnValue)=20
	                    END IF=20
	                END IF=20
	               =20
	None of these attempts succeeded. They all produced the exact same =
result. The installer started,=20
	the jre was extracted, and the installer hung. I tried all of them =
remotely and locally on two=20
	different Windows machines (one 2K and one 2003). All failed the same =
way. All worked when NOT=20
	called via STAF.=20
=09
	I know very little about Windows process creation/handling. Is there =
something about the way=20
	processes are created or parameters are passed that could be giving me =
this headache? Has anyone=20
	else run across something similar? If I had any hair, I'd be pulling it =
out...        =20
=09
	Thanks,=20
	Tom                                                          =20
=09
	# Tom H Smith
	# ITM Verification      =20
	# tomsmith@... :: Tom H Smith/Austin/IBM
	# This is an automated response. Do not reply to this mailing.
=09