> 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/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-fault-finding-using-the-test-harness.md). # Controller API - fault finding using the test harness Isolate Controller API connection problems with the supplied Test Harness. When Command Centre struggles to connect to a third-party external system, stop the third-party system and run the **Test Harness**. It is installed with the Controller API, in the same folder as `GallagherFTCAP.dll`. The harness simulates the comms path between the third-party system and the Command Centre server, and reads the port from `GallagherFTCAPI.ini`. It is useful when the third-party system has minimal logging. > ⚠️ The service using the Controller API DLL **must not be running**. The harness takes its place. ## Reading the results * **"E\_Pending"** means: verify that `Commandcentre.lic` is in `C:\Windows` on the harness PC (the exact same licence as the server, or a valid ini if 7.80+), that the controller is online, and that the External System and Item names match Command Centre exactly. * **"Gallagher FT Controller API is not ready to accept events against the Specified Source"** means a missing or mismatched ESI identifier, a mis-configured External System, a comms problem (including an unmatched licence), or the component has not finished registering event sources yet. *** 🔗 **Related** * [Controller API - FTCAPI Error Messages](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-ftcapi-error-messages.md). Registration and port errors. * [Controller API - FTCAPI.ini File](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-ftcapi.ini-file.md). The ini the harness reads. --- # 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/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-fault-finding-using-the-test-harness.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.