Summary
How To generate the InstallAnywhere Log for Install, Uninstall, and Build in InstallAnywhere 2011 and later.
Synopsis
This article discusses how to generate an install/uninstall/build log to capture what is occurring during an installation/uninstallation/build, primarily for troubleshooting purposes.
Discussion
Generating an InstallAnywhere Standard Installation Log:
Follow these steps in the InstallAnywhere IDE with your project open:
- Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings.
- Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox
- Check the Install checkbox.
- Under Log Format, select the Plain text format option.
- Build the project.
- Run the installer.
NOTE 1: Plain text format is selected by default, not XML format.
NOTE 2: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.
Generating an InstallAnywhere Standard Installation Log That Includes the Verbose Installation Debug Output:
Follow these steps in the InstallAnywhere IDE with your project open:
- Navigate to the Project > JVM Settings > Installer Settings View > Optional Installer Arguments Section.
- Specify the following value in the Additional Arguments field:
- -Dlax.debug.level=4 -Dlax.debug.all=true
- Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings.
- Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox.
- Check the Install checkbox.
- Under Log Format, select the Plain text format option.
- Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox.
- Build the project.
- Run the installer.
NOTE 1: Verbose debug output refers to more detailed debug output that can be generated by an installer.
NOTE 2: Plain text format is selected by default, not XML format.
NOTE 3: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.
Generating an InstallAnywhere Standard Uninstallation Log:
Follow these steps in the InstallAnywhere IDE with your project open:
- Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings.
- Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox
- Check the Uninstall checkbox.
- Under Log Format, select the Plain text format option.
- Build the project.
- Run the installer.
- Run the uninstaller.
NOTE 1: Plain text format is selected by default, not XML format.
NOTE 2: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.
Generating an InstallAnywhere Standard Uninstallation Log That Includes the Verbose Uninstallation Debug Output:
Follow these steps in the InstallAnywhere IDE with your project open:
- Navigate to the
Project > JVM Settings > Installer Settings View > Optional Installer ArgumentsSection. - Specify the following value in the Additional Arguments field:
-Dlax.debug.level=4 -Dlax.debug.all=true
- Navigate to the
Project > General Settings > Log SettingsSection. For InstallAnywhere versions earlier than 2013, navigate toProject > Log Settings. - Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox
- Check the Uninstall checkbox.
- Under Log Format, select the Plain text format option.
- Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox.
- Build the project.
- Run the installer.
- Run the uninstaller.
NOTE 1: Verbose debug output refers to more detailed debug output that can be generated by an uninstaller.
NOTE 2: Plain text format is selected by default, not XML format.
NOTE 3: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.
Generating a Build Log:
Command Line Build Log
The build output when running a command line build can be redirected by setting the following two properties in the build.lax file. The build.lax file is found in the InstallAnywhere HOME where InstallAnywhere is installed.
lax.stderr.redirect=\\tmp\\buildconsole.txtlax.stdout.redirect=\\tmp\\buildconsole.txt
Setting the properties as shown above will generate a file named buildconsole.txt in the specified directory (C:\\tmp) in Windows. If only a filename is specified as shown below, then the file will be created in the same directory containing the build.lax file.
lax.stderr.redirect=buildconsole.txtlax.stdout.redirect=buildconsole.txt
GUI Build Log
The build output when running a GUI build, through the InstallAnywhere Advance Designer, can similarly be redirected to a file by setting the lax.stdout.redirect and lax.stderr.redirect properties (mentioned above) in the InstallAnywhere.lax file. This file is found in the InstallAnywhere installation directory, where InstallAnywhere is installed.
NOTE: You will need to restart the InstallAnywhere IDE after making the changes in the InstallAnywhere.lax file.
Related Articles
Generating InstallAnywhere Log for Install and Uninstall with InstallAnywhere 2010 and Earlier 18Number of Views Generating InstallAnywhere Build Log for Windows and Linux 14Number of Views Writing to the Install Log of InstallAnywhere 5Number of Views Execute Uninstaller Action Does Not Uninstall 7Number of Views Successfully Authoring a Patch 3Number 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. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago