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

# General error messages

What to do about generic or unclassified GeoDin error messages that do not point to a specific known cause.

This page is the home for generic error messages that do not carry enough information to point to a specific, known cause. If your message matches one of the other troubleshooting pages, use that page instead - the steps below are for messages that do not fit anywhere else.

## Access violation

Unfortunately, this message does not carry precise diagnostic information - the numbers it displays do not reliably identify the cause.

* First, close GeoDin completely and open it again. The underlying error can persist in the background even after you dismiss the dialog, so the message may reappear on a later, unrelated action that has nothing to do with the original cause.
* If the message keeps recurring, contact [support](https://docs.geodin.com/support/get-support.md) and describe:
  * Which action triggered the error.
  * What you did immediately before it appeared.
  * Which methods or windows were open in the background at the time.

Unsaved edits left open in another input mask, followed by a switch to a different method, are a common factor - mention this if it applies to your case. This detail helps support reproduce and resolve the problem faster.


---

# 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.geodin.com/support/troubleshooting/general-error-messages.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.
