> 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/command-centre-errors-no-mapping-betwe.md).

# No mapping between account names and security IDs was done

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › No mapping between account names and security IDs was done

**Error:** "No mapping between account names and security IDs was done."

This is typically found during an upgrade.

![Error: no mapping between account names and security IDs was done](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8132c4d1113e0145835baeef4605ad3bed81696f%2FSECHUB-CCS-ERR-SID-MAPPING-01.png?alt=media)

## Resolution

Use RegEdit to open the server's registry. Rename the registry key **Command Centre** to **Command Centre.old**, then attempt the upgrade again. You may need to reboot.

> **Note:** The server will now treat this as a fresh install, and the installer may complain that the Command Centre databases are present and it cannot create new ones.

If the installer complains about existing databases:

1. Verify you have a valid recovery code.
2. Detach and copy the databases to a safe location.
3. Perform the install. This installs blank databases.
4. Detach the newly created databases and move them to a temp location.
5. Move the original databases back to where they were and attach them.
6. Apply the recovery code.

The services should start with the new install.


---

# 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/command-centre-errors-no-mapping-betwe.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.