You can activate tracing for the Packager, the Installer, or both. Tracing for the Installer can be activated on any number of target computers.
For diagnostic purposes, you can optionally record the activities of the Packager in a trace file, called trace.txt, on the Packaging Computer. The trace file is available in the trace subdirectory of the Packager installation directory. If necessary, the Packager creates backup files called trace.ba0, trace.ba1, and so on. The trace.txt file always contains the recent information.
To enable the trace for the Packager, select Tools, Options from the Packager main menu and select Enable Trace on the appearing Options dialog. To disable the Packager trace, clear the Enable Trace check box on the Options dialog. Protocol and Error messages are always written into the trace files, even if the trace feature is not enabled.
For diagnostic purposes, you can specify that the activities of the Installer should be recorded in a trace file located on the target computer.
To specify this for the target computer you want to trace, select the agent configuration procedure 'SM Installer: Enable Trace' from the Properties menu of the software delivery agent plug-in in the DSM Explorer.
To transfer the trace file contents to the output file of the job, use the agent activate procedures 'SM Installer: Get Latest Trace' or 'SM Installer: Get All Traces'.
Trace information is also created for the installation of user-specific items. To query this information, use the agent activate procedure 'SM Installer: Get User Trace'.
Instead of using a trace, you can query user-specific history by issuing the agent activate procedure 'SM Installer: Get User History'.
The same mechanism is used to record activities of the Microsoft Installer (MSI) during installation of converted MSI products. This MSI trace consists of up to three parts:
|
Copyright © 2013 CA.
All rights reserved.
|
|