> 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/keyset-does-not-exist-configuration-cl.md).

# Keyset Does Not Exist (Configuration Client fails to log in)

This error can show up after upgrading. The Configuration Client will not log in and pops up "Keyset does not exist", while the Command Centre Services start fine. It appears when the Command Centre certificate is not updated during the upgrade (a permission issue).

Trace log examples:

```
TRACE, C:\__w\543\s\Elmo\Common\CngCapiBridge.cpp(25): Keyset does not exist (80090016)
2023-02-15 17:52:43:366, CCFT[1038:2814], TRACE, C:\__w\543\s\Elmo\Common\ClientAuth.h(57): Keyset does not exist (80090016)
2023-02-15 17:52:43:366, CCFT[1038:2814], TRACE, An error occurred authenticating the workstation ftitem: 8009001608x Keyset does not exist
```

## Resolution

Rename the Friendly Name of the Gallagher Command Centre Client certificate located in **Local Computer → Gallagher Applications → Certificates**.

![Gallagher Applications certificate store](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7c6ff00970df4fe22c4db6c0ace40e3998b99aab%2FSECHUB-CCS-ERR-KEYSET-CONFIG-01.png?alt=media)

Open the properties of the certificate and change the Friendly Name (one letter will do).

![Certificate Properties, Friendly Name field](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d5e906dfae4cf7223a81d607b60d663b945cbe8b%2FSECHUB-CCS-ERR-KEYSET-CONFIG-02.png?alt=media)

Then go to the install media under `Utilities/Workstation Certificate Installer`, follow the Release Note, and use the utility.

![Workstation Certificate Installer location in the media](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e7987c3baff0d88c5fd01a4bbc17bcd18baa33b6%2FSECHUB-CCS-ERR-KEYSET-CONFIG-03.png?alt=media)

After running the utility you should be able to log into the Configuration Client and Command Centre. You may need to restart the Command Centre Services.


---

# 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/keyset-does-not-exist-configuration-cl.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.