> For the complete documentation index, see [llms.txt](https://docs.viesus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viesus.com/support/error-codes/nodejs.md).

# Node.js Error Codes

Return codes from the VIESUS Node.js module — what each code means and when it occurs.

The Node.js module returns an integer after each enhancement call:

* **`> 0`** — enhancement succeeded; the value is the processing time in milliseconds.
* **`< 0`** — enhancement failed; the value is one of the error codes below.

For symptom-based troubleshooting, see [Troubleshooting](/support/troubleshooting.md).

***

## Error codes

<table><thead><tr><th width="170">Code</th><th>Description</th></tr></thead><tbody><tr><td>-1</td><td>Init failed</td></tr><tr><td>-2</td><td>GUID wrong</td></tr><tr><td>-3</td><td>Internal error</td></tr><tr><td>-4</td><td>Loading image not possible</td></tr><tr><td>-5</td><td>Can't open file</td></tr><tr><td>-6</td><td>File not found</td></tr><tr><td>-7</td><td>File is empty</td></tr><tr><td>-8</td><td>Mem open internal error</td></tr><tr><td>-9</td><td>Enhancement failed — contact <a href="mailto:support@viesus.com">support@viesus.com</a> for further investigation</td></tr><tr><td>-10</td><td>Parameter file not found</td></tr><tr><td>-11</td><td>Parameter file empty</td></tr><tr><td>-12</td><td>Output format not supported</td></tr><tr><td>-13</td><td>Error writing result file</td></tr></tbody></table>

### Additional errors

<table><thead><tr><th width="170">Code</th><th>Description</th></tr></thead><tbody><tr><td>-126</td><td>Enhancement failed — image was already enhanced</td></tr><tr><td>-378</td><td>Enhancement failed — wrong GUID entered</td></tr></tbody></table>

Codes below **`-18`** (other than the named codes above) indicate internal errors. Contact <support@viesus.com> if you receive one.


---

# 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.viesus.com/support/error-codes/nodejs.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.