How to Capture Debug Output for Windows-Based Installers

Title

Summary

Information on capturing debug output for Windows-based installers.

Synopsis

This article provides information on how to capture debug output for Windows-based installers.

Discussion

To capture debug output from the installer
To view or capture the debug output from a Windows-based installer, hold down the CTRL key immediately after launching the installer until a console window opens. Before exiting the installer, copy the console output to a text file for later review.

On some Windows-based systems, run the installer once while holding the CTRL key down, resetting the scroll-back buffer for the console window, and then quit and run the installation again.

To capture debug output from silent install
If you encounter problems while capturing the console output, try a slightly more convoluted method. (This often is the case on Windows 9x systems because of the limited ability of the console to capture output). First launch the installer and allow it to extract the necessary files. Once it reaches the Preparing to Install panel, when given the opportunity to choose a language or to go to the Windows temp directory, look for a temp folder that starts with a vertical bar (I), followed by many numeric digits (for example?I1063988642). Be sure it is the most recent directory by sorting the directories by their modified date. Open the directory; it should contain a file called sea_loc. Delete this file. Now return to the installer, click OK. At the first opportunity, cancel the installation.

Now go back to the directory inside the temp directory, where the file sea_loc was deleted. There should be another directory called Windows; open it. There should be an .exe file (most likely install.exe). There should also be another file with the same name except it will have a .lax extension. Open it in a text editor and set the lax.stderr.redirect and lax.stdout.redirect properties:

lax.stderr.redirect=output.txt
lax.stdout.redirect=output.txt

After these changes have been made, save the file and launch the .exe. When the installation is complete, the same directory that contains the .lax file should contain an output.txt file. The output.txt file contains the same information that was sent to the console.

Was this helpful?

Support Hub

Product

InstallAnywhere

Visibility

Guest

URL Name

how-to-capture-debug-output-for-windows-based-installers

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

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.

Summary

Synopsis

Discussion

Related Articles

Please wait...

Case id: 00001065