Read Installation Logs for Company Apps and Scripts
When a Company App or script fails on a Windows endpoint, the installation logs show which step failed and why. This page shows you how to open the logs and what to look for.
Open the logs
Section titled “Open the logs”- Go to Windows → Applications and open the Company Apps or Scripts tab.
- Open the app or script and select the Endpoints tab.
- Open the row menu for the endpoint and select View logs.
On the endpoint, Install.log is in
C:\ProgramData\CapaSystems\COA\Logs\PackageInstaller\<app name> <version>\.
The log files
Section titled “The log files”| File | What it contains |
|---|---|
PackageInstaller.log |
What the CapaOne Agent did with the job: the command it received, the download of the install script, the result, and a Statistics summary with the error code. Start here. |
Install.log |
What the generated install script did: one Started and one Ended line for each PowerBrick, the exit code of each installer, and the final exit code. |
CapaOne.ScriptingLibrary.log |
Every call the PowerBricks made to the scripting library, with their arguments. Use it for detail about a specific brick. |
How a job runs
Section titled “How a job runs”- The agent receives an
InstallorUninstallcommand for the app or script. - The agent downloads the generated script,
Install.ps1orUninstall.ps1, andPSlib.psm1. CapaOne generates the script from the PowerBricks in the sequence. You don’t upload it. - The script runs the PowerBricks in order. Download Content downloads the files under Source Files to the endpoint.
- The script ends with an exit code, and the agent reports the result.
If a PowerBrick fails, the bricks after it don’t run. Find the first brick that failed.
What to look for
Section titled “What to look for”In PackageInstaller.log
Section titled “In PackageInstaller.log”| Line | What it means |
|---|---|
Runspace: Script completed without errors |
The install script ran to the end. |
Script Info: Started <brick> and Script Info: Ended <brick> |
The agent’s view of each PowerBrick. The last Started line without an Ended line is the brick that failed. |
Status: MD5 equals expectation |
Download Content downloaded the app’s files and verified them. |
ErrorCode: in Statistics |
The result of the job, for example SUCCESS (0). |
TransferTime: 0 ms in Statistics |
Nothing was downloaded. Download Content didn’t run. |
In Install.log
Section titled “In Install.log”| Line | What it means |
|---|---|
Started <brick> <version> and Ended <brick> <version> |
One pair for each PowerBrick that ran. |
Shell_Execute: Completed with status: '<code>' |
The exit code returned by an installer. |
The exit code <code> is in the list of handled codes. Action to take: success |
The install brick treated the exit code as a success, based on its Return Code Handles. |
SCRIPT ENDED WITH EXITCODE: <code> |
The final exit code of the script. 0 is success. |