DebbieL wrote: InstallShield adds ISSetupFilesExtract automatically to your project when you add one or more files in the Support Files view. It gets scheduled very early in the UI and Execute sequences. If you don't need to use support files in your installation, you could simply schedule the CheckIfPatchInstalled described in that thread very early in both sequences. Thank you very much, I'll give that a try. ... View more

yossiz wrote: Did you check KB article Q112546 ? Thanks for the info, but that doesn't help with using the Automation framework. That's only running on the command line. ... View more

TechGuy wrote: Thank you for the reply but my executable is not a msi. It is done as an installshield project (install script .exe). If it's a setup.exe try the /debuglog switch on the command line. ex. setup.exe /debuglog This will create the log in the same folder as the installer. Otherwise you will need to specify the path to a writable folder: ex:Setup.exe /debuglog"C:\temp\package.log" ... View more

Debbie, Thank you very much for the suggestions. I tried both... added the debugpath to the registry as described. After reading the steps pointed to by the link you send, I did notice I was missing the SCiLexxer.dll file. I added that to my debug machine. Still nothing happened. The install ran through as normal. Jim ... View more

DebbieL wrote: KB article Q112187 explains how. That KB Article explains a workaround for IS2010 but I'm working with IS2011. I've tried this workaround with IS2011 and I'm still not able to debug deferred InstallScript custom actions. ... View more

hari14singh wrote: yes through windbg.exe. Attach to the instance of MSIEXEC.exe that is running in the system logon session. Enable the break on create process event filter (tools -> event filters -> Create Process -> enabled -> not handled) and module load (little noisy you may skip this) Is there not a way to do this using the ISDbg.exe (InstallShield Debugger)? ... View more

Johannes_T wrote: I do somethig similar, only a setup.rul with declare ... program START: ... endprogram I do everything "manually", show dialogs, copy files and much, much more. You don't really have to use events. You can show the status window with something like this: Enable(STATUS); StatusUpdate (ON, 10); SetStatusWindow (10, "We're doing useful things..."); // Do something useful... SetStatusWindow (20, "..."); Disable(STATUS) Check the SetStatusWindow Example in the manual. HTH, Johannes How are you doing your deploy? Are you using the Ant Tasks that come with OC4J? Do you have any examples you can share? I'm in the process of beating my head into a wall trying to make some sense of this mess. :confused: This is the code I'm scrapping my head against: Deploying ${deploy.ear} to ${targetenv} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" file="${deploy.ear}" deploymentName="${oc4j.deployment.name}" bindAllWebApps="default-web-site" logFile="${log.dir}/deploy.log"/> Undeploying ${oc4j.deployment.name} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" deploymentName="${oc4j.deployment.name}" logFile="${log.dir}/undeploy.log"/> Redeploying ${deploy.ear} to ${targetenv} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" file="${deploy.ear}" deploymentName="${oc4j.deployment.name}" logFile="${log.dir}/redeploy.log"/> Thanks in advance! 🙂 ... View more

I need to specifically check for Windows 2003 Enterprise Server Service Pack 2. ... View more