> 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-connection-issues/command-centre-connection-issues-u-3.md).

# Unable to log into Configuration Client

[Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › Unable to log into Configuration Client

When dealing with DCOM-related issues, **apply the fix to both the server and the workstation, followed by a full system restart.** Newer versions have moved away from DCOM (v7.90 and above).

Download the **DCOM utility** from the File Transfer Site, located in `Command Centre and Associated Files > Utilities > DCOM Utility`. Extract it to the `\Command Centre\Bin` folder and run as admin.

## Enabling DCOM after upgrading to v8.XXX

Upgrading to v7.90 (and particularly v8.XX) disables DCOM on the server, which also disables OPC.

1. Change the `ServerUrl` registry key from `wss://servername:8905` to `dcom://servername`, then restart the Command Centre Services.
2. On every workstation in use, edit `C:\Program Files (x86)\Gallagher\Command Centre\ConfigClient\CCFT.exe.config` and change `wss://servername:8905` to `dcom://servername`.
3. Obtain `FT DCom Setup.exe` from an older version of Command Centre and run it in the Bin folder with **Legacy DCOM Settings** (it is no longer supplied on the install media). If you do not have access to the FT DCOM utility, contact Technical Support.

> **Important:** If the FT DCOM Setup tool is run, the computer it is run on must be restarted for the changes to take full effect. **Important:** If the OPC connection is on the server, step 1 (registry change) is needed; after restarting the services and establishing the OPC connection, the settings can be reverted back to `wss://servername:8905`. This reverts DCOM to active for workstations and re-enables OPC alarms and events.

***

🔗 **Related**

* [OPC Connections 7.90 and higher - DCOM changes](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-opc-c.md). The DCOM transport change behind OPC connectivity.


---

# 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-connection-issues/command-centre-connection-issues-u-3.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.