For the complete documentation index, see llms.txt. This page is also available as Markdown.

Unable to log into Configuration Client

Command Centre - Connection Issues › 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

Last updated

Was this helpful?