> 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/the-salto-re-sync-failed-and-no-change.md).

# The Salto Re-sync failed, and no changes were made.

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › The Salto Re-sync failed, and no changes were made.

| Error content                                       | Description                                                                     |
| --------------------------------------------------- | ------------------------------------------------------------------------------- |
| The Salto Re-sync failed, and no changes were made. | A door was removed in Salto, and a re-sync is then attempted in Command Centre. |

![Error: the Salto re-sync failed, and no changes were made](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c4230908c7b2d2c08a10b0d5f6eb51fdfb1aa66f%2FSECHUB-CCS-ERR-SALTO-RESYNC-01.png?alt=media)

## Resolution

Check the Command Centre Trace logs for the following errors:

```
CCNTSad[03d0:3044], TRACE, [73521] Write 16448 [24] failed. C13A0052: This item cannot be deleted as it is assigned to an Access Group. {17 ms}
CCNTSad[03d0:3044], TRACE, CWriteLock::CommitHR failed: This item cannot be deleted as it is assigned to an Access Group. (c13a0052)
CCNTSad[03d0:3044], TRACE, C:\build\Elmo\CCFTSalto\SaltoServer.cpp(721): Throwing Error c13a0052 This item cannot be deleted as it is assigned to an Access Group.
CCNTSad[03d0:3044], TRACE, C:\build\Elmo\CCFTSalto\SaltoServer.cpp(928): failed with code c13a0052 This item cannot be deleted as it is assigned to an Access Group.
CCNTSad[03d0:3044], TRACE, C:\build\Elmo\CCFTSalto\SaltoServer.cpp(509): DoResync(session) failed with code c13a0050 The Salto Re-sync did not complete successfully, though some changes were made.
CCNTSad[03d0:3044], TRACE, C:\build\Elmo\Common\FTItem\FTItemBase.cpp(2651): failed with code c13a0050 The Salto Re-sync did not complete successfully, though some changes were made.
```

This indicates the door deleted from within Salto still exists in Command Centre and is still assigned from within Access Groups on the Salto Access tab.

In the first log line, **`Write 16448`** gives the **FTItemID** of the door in Command Centre that was deleted in the Salto system but cannot be deleted in Command Centre because items, usually Access Groups, are still associated with it.

1. Open the **Find Tool** and, under the description, enter two left square brackets `[[` followed by the FTItemID from the Command Centre log.

![Find Tool locating the access zone by FTItemID](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-882c766f2bc3801f76caf4234485c175f503d3fc%2FSECHUB-CCS-ERR-SALTO-RESYNC-02.jpg?alt=media)

2. Once you have found the Access Zone, remove these doors from the Access Groups.
3. Perform the re-sync again.

***

🔗 **Related**

* [Message: notifySystemRegistered failed for DVR 1. Reason: type identifier is empty](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/message-notifysystemregistered-failed.md). The other third-party integration error in this section.


---

# 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/the-salto-re-sync-failed-and-no-change.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.