Summary
The InstallScript Debugger does not debug deferred, commit, or rollback InstallScript custom actions.Symptoms
The InstallScript Debugger does not debug deferred, commit, or rollback InstallScript custom actions.
This applies to the following Project Types:
- Basic MSI
- InstallScript MSI
Cause
The InstallScript Debugger checks the value of the ISSCRIPTDEBUG property to determine whether to debug the InstallScript in an installation. However, deferred, commit, and rollback InstallScript custom actions cannot access this property (or most of the Windows Installer properties). Therefore, the InstallScript Debugger ignores deferred, commit, and rollback InstallScript custom actions.
Workaround
In order to be able to use the InstallScript Debugger to debug deferred, commit, or rollback InstallScript custom actions:
- Download the Debug.zip file from the attachments section below. Extract file and add the Registry data to the client you intend to debug InstallScript custom actions.
- Double-click the file and select 'Yes' to continue.
The following registry keys will be created:
HKEY_CURRENT_USER\Software\InstallShield\ISEngine15.0 HKEY_CURRENT_USER\Software\InstallShield\ISEngine16.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine17.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine18.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine19.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine20.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine21.0
HKEY_CURRENT_USER\Software\InstallShield\ISEngine22.0In addition, a DWORD value called DebugISCustomActions with data 00000001 is created under each key. These keys are for version 2009 through version 2015 of the InstallShield product.
This enables you to use the InstallScript Debugger to debug deferred, commit, and rollback InstallScript custom actions.
Note: Even without this registry change, you can use the InstallScript Debugger to debug immediate InstallScript custom actions. If you do apply this registry change, the InstallScript Debugger launches for all InstallScript custom actions, regardless of what you have set for the ISSCRIPTDEBUG property.
Additional Information
InstallShield 2015 Release Notes
For detailed information about possible migration issues that may occur when you migrate projects that were created with InstallShield 11.5 and earlier to InstallShield 12, see:
Upgrading Projects from InstallShield 11.5 or Earlier
For more information about the InstallScript Debugger, see:
InstallScript Debugger
Related Articles
Debug InstallScript Custom Action Running Deferred In System Context. 4Number of Views Access SUPPORTDIR from a Deferred, Rollback, or Commit Custom Action 5Number of Views Logging An InstallScript MSI Project 361Number of Views Access SUPPORTDIR from an InstallScript Custom Action 6Number of Views Create a 64-bit Windows Registry Entry via an InstallScript Custom Action 9Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago