# Read Installation Logs for Company Apps and Scripts

> Open the installation logs for a Company App or script on a Windows endpoint and find the line that explains why the installation failed.

Source: https://docs.capaone.com/capaone/troubleshooting/read-installation-logs-for-company-apps-and-scripts/  
Product: CapaOne — a separate CapaSystems product; do not apply this page to any other.

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

1. Go to **Windows → Applications** and open the **Company Apps** or **Scripts** tab.
2. Open the app or script and select the **Endpoints** tab.
3. 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

| 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

1. The agent receives an `Install` or `Uninstall` command for the app or script.
2. The agent downloads the generated script, `Install.ps1` or `Uninstall.ps1`, and `PSlib.psm1`.
   CapaOne generates the script from the PowerBricks in the sequence. You don't upload it.
3. The script runs the PowerBricks in order. **Download Content** downloads the files under
   **Source Files** to the endpoint.
4. 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

### 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

| 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. |

## Related

- [Assign and Redeploy Windows Applications](/capaone/application-manager/assign-and-redeploy-windows-applications/)
- [Create a Company App](/capaone/application-manager/create-a-company-app/)
- [Script or Company App Install Fails Because a File Is Missing](/capaone/troubleshooting/script-or-company-app-install-fails-because-a-file-is-missing/)
