Taking a look at all the logfiles

Owned by Torben Busk Sørensen
Last updated: Mar 22, 2023 by Rikke Borup
2 min read

Where are they?

When installing a PowerPack, a log folder is created inside the \Client\Logs folder, named after the package, which is ‘The Perfect Package 2.0’ (in Italian); ‘Il pacchetto perfetto 2.0 IT’

 

Inside this folder, all relevant logs are written;

Logfile

Written by

Content

Logfile

Written by

Content

Install.log / Uninstall.log

The installation script (Install.ps1) or uninstallation script (Uninstall.ps1)

This is the logfile created by the Install.ps1 script when calling the Job_Writelog, like; $cs.Job_WriteLog("[Init]: $PackageRoot: '" + $Packageroot + "'")

PowerPackServer.log

The PackageJob inside the Package module inside the BaseAgent

Job initialization, FrontEnd communication, Requests/ responses to/from the Agent script (.cis) as well as package results and logfile zipping/upload

PowerPackClient.log

The PowerPack.exe running the PowerShell Runspace and hence the installation script

Package Info, script parameters for the PowerShell instance and logging as well as Named pipe communications to the BaseAgent

CapaOne.ScriptingLibrary.log

The Scripting Library.dll which is loaded by the installation script

The log for all the scripting library functions that are being called by the installation script

Upon completion, these four (or five) logfiles are zipped and uploaded to the FrontEnd which saves the zip file in the UNITJOB table of the SQL database.

To maintain some compatibility with VBScript-based packages, the Install.log (or Uninstall.log) is copied to the parent log folder to 'Il pacchetto perfetto 2.0 IT.log' which is the name of the package;

How to view them

To view the log files of an installation, you must open the CapaInstaller Console, and find the device on which the package is installed. Then right-click the package and select ‘View Installation Logs…’

This will open the LogViewer and show the four log files from the installation of the package. This dialog is similar to that of a VBScript-based package, except that four tabs are shown at the top of the form, to ease navigation.

Â