> 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-errors/unable-to-log-into-command-centre-clie.md).

# Unable to log into Command Centre Client on a workstation, but Configuration Client works fine

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › Unable to log into Command Centre Client on a workstation, but Configuration Client works fine

Four scenarios can cause this.

## Scenario 1: UTC time mismatch between server and workstation

The server or workstation is set to the wrong region or is not in sync. Log indicator:

```
An error occurred authenticating the workstation ftitem: c1b8005008x Workstation connected with incorrect certificate
```

Check the server and workstation Time Zones and Locale. In PowerShell, get the actual UTC time:

```powershell
[System.DateTime]::UtcNow
```

![PowerShell UTC time output](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3d7d61a2bc498e640320e62afe01fc78f36367c0%2FSECHUB-CCS-ERR-CC-CLIENT-NO-LOGIN-01.jpg?alt=media)

Compare the two systems; they must be within a few minutes of one another.

## Scenario 2: license file contains more than one Encryption entry

Check the license file on the server. If there are two entries for Encryption:

```
EncryptionOn=0
EncryptionOn=1
```

then this is likely the issue. Contact Technical Support to alter the license.

## Scenario 3: custom-defined Locale in use, or unsupported language

The Configuration Client crashes with logs such as:

```
User name: 'Master'. Workstation: 'TESTING'
Exception #e51dcc0. Code: e06d7363, Location: 0x76243502
KERNELBASE.dll!RaiseException() + 98
VCRUNTIME140.dll!CxxThrowException() + 102
```

Check the system's Locale and language to verify the language is supported by Command Centre.

## Scenario 4: Configuration Client will not open on the server from the desktop link, but opens through the Command Centre Client

Command Centre logs show:

```
CCFT[194c:0b6c], TRACE, GGLWebSocket::ConnectionResponseReady started.
CCFT[194c:0b6c], TRACE, GGLWebSocket::ConnectionResponseReady reached return
CCFT[194c:1120], TRACE, Workstation Software Version 8800918
CCFT[194c:1120], TRACE, CWAD::Logon - User name: 'system', Workstation: 'DESKTOP-DUMMY'
CCFT[194c:1120], EXCEPTION, Unhandled Exception #f2e75a6. Code: e06d7363, Location: 0x7597E022
```

This indicates the Windows user account and the service user account have different Locales.

1. Right-click the **Time** in the system tray and select **Adjust date/time**.
2. Under **Related Settings**, select **Additional date, time & regional settings**.
3. Under **Region**, select **Change date, time, or number formats**.
4. Select the **Administrative** tab.

![Regional settings Administrative tab](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-46fd39d422e275f73e67457eeeaa7d4c99ab1ed6%2FSECHUB-CCS-ERR-CC-CLIENT-NO-LOGIN-02.jpg?alt=media)

5. The new and welcome screens are not the same. Select both **Welcome screen and system accounts** and **New user accounts**.
6. Select **Apply**.

![Applying locale to system and user accounts](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-689aab6d43d234d3328b6abe95f8afe2984dc68a%2FSECHUB-CCS-ERR-CC-CLIENT-NO-LOGIN-03.jpg?alt=media)

This sets the system and user account to the same value and should resolve the login issue.

***

🔗 **Related**

* [Workstation Connected with Incorrect Certificate](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/workstation-connected-with-incorrect-c.md). The certificate error named in the Scenario 1 log line.
* [Command Centre Errors - The Configured Server is not Trusted by this Client](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-the-configured-s.md). The other client-side trust failure that blocks login.
* [Command Centre Errors - Client running in Task Manager but login screen is not showing up](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-client-running-i.md). When the client starts but never draws its login screen.


---

# 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-errors/unable-to-log-into-command-centre-clie.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.