> 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/deployment-resources/support-tools-and-troubleshooting/support-log-tool.md). # Support Log Tool Collect Command Centre, Windows, SQL, and controller logs for Technical Support. The Support Log Tool collects all Command Centre logs, Command Centre minidumps, Windows Application and System logs, the FTSupportTool text file, SQL error logs, and selected controller error logs. It is not on the install media because it is constantly updated. Download it from the Gallagher File Transfer Site or Technical Support. Place it in an empty folder on the server or workstation. Decompress it and run `SupportLogTool.exe`. Administrator access may be required. Enable trace if it is off. Select Minidumps or Controller Logs if requested. The Additional Config tab adds SQL performance information, PIV information, Pending Changesets, and Changesets. If controller logs are included and the default Diagnostic password has changed in 8.40+, enable web browsing on the target controllers for at least 5 minutes from the Status & Overrides tab. Select **Collect Logs**. A new timestamped folder with a `CCFT Log` prefix is created. Zip it and send it to Technical Support. See [Diagnostic Logs](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/troubleshoot/command-centre-diagnostic-logs/README.md). ![Support Log Collection Utility, Command Centre logs tab — Collect Logs button, Enable trace logging, Include Minidump files, Include Controller Logs](https://3862776825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feem9HLOjc53n2VxEz3Cq%2Fuploads%2FuI4ApHwKtBsEamJtyRn2%2FSECHUB-iut-support-log-tool-01-command-centre-logs-tab.png?alt=media\&token=b2e85173-8084-4532-a08d-42cafa4e9868) ![Support Log Collection Utility, Additional Config tab — Diagnostic password (only required from 8.40 if changed from default), plus SQL Server performance info, PIV Information, Pending Changesets and Changesets, with a warning that Changesets can collect a large amount of data](https://3862776825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feem9HLOjc53n2VxEz3Cq%2Fuploads%2FLGWpaMepbPc8L01WOEOK%2FSECHUB-iut-support-log-tool-02-additional-config-tab.png?alt=media\&token=f47df09e-8b44-4411-8f94-2c5fbc236a37) The Support Log Tool collects all Command Centre logs, Command Centre minidumps, Windows Application and System logs, the FTSupportTool text file, SQL error logs, and selected controller error logs. It is not on the install media because it is constantly updated. Download it from the Gallagher File Transfer Site or Technical Support. Place it in an empty folder on the server or workstation. Decompress it and run `SupportLogTool.exe`. Administrator access may be required. Enable trace if it is off. Select Minidumps or Controller Logs if requested. The Additional Config tab adds SQL performance information, PIV information, Pending Changesets, and Changesets. If controller logs are included and the default Diagnostic password has changed in 8.40+, enable web browsing on the target controllers for at least 5 minutes from the Status & Overrides tab. Select **Collect Logs**. A new timestamped folder with a `CCFT Log` prefix is created. Zip it and send it to Technical Support. See [Diagnostic Logs](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/troubleshoot/command-centre-diagnostic-logs/README.md). ![Support Log Collection Utility, Command Centre logs tab — Collect Logs button, Enable trace logging, Include Minidump files, Include Controller Logs](https://3862776825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feem9HLOjc53n2VxEz3Cq%2Fuploads%2FuI4ApHwKtBsEamJtyRn2%2FSECHUB-iut-support-log-tool-01-command-centre-logs-tab.png?alt=media\&token=b2e85173-8084-4532-a08d-42cafa4e9868) ![Controller 6000 Properties, Status and Overrides tab — the Enable WWW Connections override (set For 5 Minutes) used to allow controller-log collection](https://3862776825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feem9HLOjc53n2VxEz3Cq%2Fuploads%2FywAOS3V4mg8asGRgSZjF%2FSECHUB-iut-support-log-tool-03-controller-enable-www-override.png?alt=media\&token=6fd876a3-b493-4208-8e86-4b22998d1f94) --- # 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/deployment-resources/support-tools-and-troubleshooting/support-log-tool.md?ask=&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.