> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/find-app-host-and-message-bus-logs-and-versions.md).

# Find App Host and Message Bus logs and versions

Find log files, raise the log level and check installed versions for the App Host, its modules and the Message Bus.

**Applies to:** Command Centre vEL9.40 and later (Message Bus) · vEL9.50 and later (App Host; compatible with vEL9.40 for out-of-band installation where required)

Use these steps to find App Host, module and Message Bus log files and versions. For what these services are, see [App Host and Message Bus](https://help.security.gallagher.com/knowledge-hub/products/cc-software/reference/app-host-and-message-bus.md).

### Log file locations

| Service          | Default log location                                                        | Written by                                                                                                                                                                                        |
| ---------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Message Bus      | `%ProgramData%\Gallagher\Message Bus\Command Centre\Logging\MessageBus.log` | The embedded NATS runtime. Not sent as telemetry to the Diagnostics Service.                                                                                                                      |
| App Host         | `%ProgramData%\Gallagher\AppHost Service\service.log`                       | The App Host's Serilog file sink. The App Host may also send telemetry (traces, metrics and structured log events) to the Diagnostics Service, which collects it with other diagnostic telemetry. |
| App Host modules | `%ProgramData%\Gallagher\<Module Name>\<Log File Name>.log`                 | Each module                                                                                                                                                                                       |

The log files are the files with the extension `*.log` inside these folders.

{% hint style="info" %}
From Support Log Tool version 9.40.48, the tool collects logs from the App Host, the Message Bus and, if they are installed, two modules: the **Cardholder Location module** and the **ASSA Abloy Integration module**. For any other module, **open the log folder by hand**.
{% endhint %}

### Open the log folder

1. Right-click the **CCFTServiceManager** and select **Diagnostic → Open Log Folder**.

   ![The Command Centre Service Manager tray menu with Diagnostic expanded and Open Log Folder highlighted.](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-de84f1df9508c6af7b4eefcb5a870e5d4322779d%2FDEV-GUIDANCE-apphost-msgbus-02-service-manager-open-log-folder.png?alt=media)
2. Go up one folder level, to `C:\ProgramData\Gallagher`.

   ![File Explorer at This PC > Local Disk (C:) > ProgramData > Gallagher, showing the folders AppHost Service, Cardholder Location Module, Command Centre, Message Bus and Minidump.](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a972f4c03bf200e668234340c9fac36859fe7b51%2FDEV-GUIDANCE-apphost-msgbus-03-programdata-gallagher-folders.png?alt=media)
3. Open the relevant folder and find the `*.log` file.

### Change where the logs are written

**App Host:** change the `"Serilog:WriteTo:Args:Path"` setting in the App Host configuration file, then restart the **Gallagher Command Centre AppHost Service**. By default the configuration file is `C:\Program Files\Gallagher\AppHost Service\Bin\appsettings.json`.

**Message Bus:** the log file location and the JetStream data storage location are both set in the Message Bus configuration file, `MessageBus.conf`. It is typically in one of these locations:

* `C:\Program Files\Gallagher\Message Bus\Command Centre\MessageBus.conf`
* `C:\Program Files (x86)\Gallagher\Command Centre\Message Bus\MessageBus.conf`

Restart the **Gallagher Command Centre Message Bus** Windows service after changing them. The entries are near the bottom of the file:

```json
"jetstream": {
"enabled": true,
"store_dir": "<folder path>"
},
"logfile": "<log file path>"
```

* `store_dir` defines where JetStream persists Message Bus data. Replace `<folder path>` with the folder you want to use.
* `logfile` defines where Message Bus log output is written. Replace `<log file path>` with the full path of the log file. By default it is `%ProgramData%\Gallagher\Message Bus\Command Centre\Logging\MessageBus.log`.

The Message Bus release note's example writes each backslash in a path as `\\`.

### Raise the Message Bus log level

1. Open `MessageBus.conf` (see the locations above).
2. Add these values for `debug` and `trace_verbose`:

   ```json
   ...

   "debug": true,
   "trace_verbose": true
   }
   ```
3. Restart the Message Bus using the Service Manager for the change to take effect.
4. Check for the additional log messages in the Message Bus log file, by default `%ProgramData%\Gallagher\Message Bus\Command Centre\Logging\MessageBus.log`.

{% hint style="danger" %}
**Undo this change** and restart the Message Bus when troubleshooting is complete. Debug logging generates significant logging volume, which may quickly use up available disk space.
{% endhint %}

### Find the installed App Host version

Version detection will be added to the FTSupportTool in a future release. Until then, use the methods on this page for the App Host, the Message Bus and modules.

1. Locate the App Host assembly: `C:\Program Files\Gallagher\AppHost Service\Bin\Gallagher.Security.AppHost.dll`
2. Right-click the `.dll` file and select **Properties**.
3. Open the **Details** tab.
4. Locate the **Product version** field.

The part of the Product version before the `+` is the installed App Host version. In this example it is 3.1.2.

![Gallagher.Security.AppHost.dll Properties, Details tab. File version 3.1.2.10000; Product version 3.1.2+5fd3acc2258e072f7ca09373ea2… highlighted.](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-223939638195b363ee7fdd85f5830de472e949f0%2FDEV-GUIDANCE-apphost-msgbus-04-apphost-dll-product-version.png?alt=media)

### Find the installed Message Bus version

Where you can, quote the **Gallagher Command Centre Message Bus** version. Read it with this PowerShell command:

```powershell
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object DisplayName -eq 'Gallagher Command Centre Message Bus' | Select-Object DisplayName, DisplayVersion
```

The Message Bus log also records the version of the underlying NATS server when the Message Bus starts. Open the log, by default `%ProgramData%\Gallagher\Message Bus\Command Centre\Logging\MessageBus.log`, and look for the startup lines.

![Two MessageBus.log lines: "\[4940\] 2026/07/01 10:51:13.844826 \[INF\] Starting nats-server" followed by "\[4940\] 2026/07/01 10:51:13.844826 \[INF\]   Version:  2.12.2".](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d8b01c01163a6f64747b1eb113a5f9a5e99d3daf%2FDEV-GUIDANCE-apphost-msgbus-05-nats-startup-version-log.png?alt=media)

{% hint style="info" %}
The startup line gives the NATS server version (2.12.2 in the example). It is a different number from the Message Bus version in the release notes (0.8.3, 0.9.0 or 0.9.2).
{% endhint %}

### Find the installed module version

Modules may log their version at startup or provide another way to find the installed version. Unless the module says otherwise, use the same method as the App Host:

1. Locate the module's `ModuleManifest.json` file in its App Host module folder.
2. Read the value of the `AssemblyName` property. It names the assembly (`.dll`) whose version is the module version.
3. Right-click that `.dll` file and select **Properties**.
4. Open the **Details** tab.
5. Locate the **Product version** field. The part before the `+` is the installed module version.

For example, the Cardholder Location Module is located by default at `C:\Program Files\Gallagher\AppHost Service\Modules\Cardholder Location Module`. Its `ModuleManifest.json` is:

```json
{
  "ModuleName": "Gallagher Cardholder Location Module",
  "AssemblyName": "Gallagher.Security.AppHost.CardholderLocation.dll"
}
```

So the assembly file is `C:\Program Files\Gallagher\AppHost Service\Modules\Cardholder Location Module\Gallagher.Security.AppHost.CardholderLocation.dll`. In this example the module version is 2.0.8.

![Gallagher.Security.AppHost.CardholderLocation.dll Properties, Details tab. File version 2.0.8.10000; Product version 2.0.8+d1a6bd280ac7fc86841862069a7… highlighted.](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ebf727a8318a40907e04e4a125cca6cd6dcbb45f%2FDEV-GUIDANCE-apphost-msgbus-06-module-dll-product-version.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/find-app-host-and-message-bus-logs-and-versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
