> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-lite-v7-open-en/windows/clienteff/codigos-de-resultado-de-clienteff.md).

# ClienteFF return codes

The ClienteFF command returns the following result codes:

| **Code** | **Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **0**    | **Successful result.**                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **1**    | **Syntax error**. The call has not been made with the appropriate parameters.                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **2**    | **Configuration profile error**. In the call, usernames or application names that are not found in the configuration profiles have been used; the names are in the profiles, but they are not of the appropriate type according to the request made (remote-type user in a signing call, etc.); not all the required data for each element has been configured in the profiles (user without associated keystore, application for which the necessary directories have not been indicated, etc.). |
| **3**    | **License error**. License is missing or is not valid.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **4**    | **No signatures have been made or found**. The signature could not be correctly performed during signing mode, or no signed files were found to verify during verification mode                                                                                                                                                                                                                                                                                                                   |
| **5**    | **Incorrect signature error**. The server returns that the signature is incorrect (it has been tampered with, the CA of the signing certificate is not trusted, the certificate has expired, etc.).                                                                                                                                                                                                                                                                                               |
| **6**    | **Incorrect signature error due to profiles**. The signature is correct; however, the last check performed with the configuration profiles was not passed (the certificates used to sign do not correspond to any of the certificates associated with the application, none of the provided rules was met, the signing mode is not the expected one, etc.). It is necessary to consult *\[application data directory* *]/TMP.XD/\[file name].ctrl* for more information, see section 3.2.5.       |
| **7**    | **Product configuration error**. The configuration file SignatureServices/conf/xades.properties cannot be found, or cannot be interpreted.                                                                                                                                                                                                                                                                                                                                                        |
| **8**    | **Error creating files or directories**. Lack of permission to create the TMP.XD directory under the file directory or the .ctrl files that go in that folder                                                                                                                                                                                                                                                                                                                                     |
| **9**    | **Error during the signing or verification process.** All or part of the signatures could not be performed correctly, or all or part of the verifications were not correct. Consult the log file for more information about the files that caused the error and the type of error, which will be one of those already described, that occurred in them.                                                                                                                                           |

From batch files, it is possible to capture this result using:

echo %errorlevel%


---

# 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://docs.editran.onesait.com/documentacion-editran/publico-editranff-lite-v7-open-en/windows/clienteff/codigos-de-resultado-de-clienteff.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.