> 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.md). # Troubleshooting Symptom-first troubleshooting for GeoDin - find your error message or problem area, get the cause and the fix, with diagnostics for everything else. Find your symptom below. Each problem area has its own page with the error messages, causes, and fixes; quick answers to frequent stumbling blocks are directly on this page. ## Find your problem area | Your problem involves... | Go to | | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | Opening a database, lock errors, moved files, sharing data | [Database connection problems](/support/troubleshooting/database-connections.md) | | "Object type not installed", dictionary errors | [Object type and dictionary problems](/support/troubleshooting/object-types-and-dictionaries.md) | | Licenses not active, network licenses, gray modules | [Licensing problems](/support/troubleshooting/licensing.md) | | Install, start, or update failures | [Installation and update problems](/support/troubleshooting/installation-and-updates.md) | | Layouts, graphic elements, depth scales | [Layout and graphic problems](/support/troubleshooting/layouts-and-graphics.md) | | Network dongle (GeoDin 7-9.0) | [Configure network dongle access](/support/troubleshooting/configure-network-dongle-access-geodin-7-9.0.md) | | "Update incomplete" on every start (up to 10.1) | [Update incomplete message](/support/troubleshooting/update-incomplete-message-until-geodin-10.1.md) | ## Quick answers ### AGS import into an SQL database fails In client/server (SQL) databases the AGS table structure must exist before an AGS file can be imported. Create a dummy object of the AGS object type first - this creates the tables - then run the import. See [AGS import](/importing-data/ags-import.md). ### A method button does not react to a click Methods in the method list start on a **double-click**, not a single click. ### Umlauts (Ä, Ö, Ü, ß) are garbled in a map layer The layer's codepage is wrong. In the layer properties under **General**, set **From codepage** to `65001` (UTF-8). ### A new map asks to install object types Maps are stored via two document object types. Online, the Map Manager installs them automatically when you confirm the prompt. Offline, install the object types **(DOC) GeODin Karte** and **(DOC) GeODin Thema** before creating your first map. ### Users keep changing shared template maps On client/server databases you can restrict users to SELECT-only on the document tables - but this affects all documents, since every document's content lives in the table `GEODIN_ADC_ADCDATA`. The lighter alternative for any database type: save the template map as an external `.GGM` file via **Save document as** and re-insert it if the shared copy is ever changed. ### Below-detection-limit values need a minus sign in reports Values under the detection limit display with `<` by default. For reports that need them as negative values, either enable **Allow negative values** on the parameter in the Datatype Manager, or use a conditional macro in the report (example for parameter WAS:AL): ``` $%COND[#WAS:AL#like'<%']'-'$%CALC[$WAS:AL$*1@.2] ``` ### Problems with SEP data (German state-authority deliveries) SEP1 / SEP3 topics - conversion, the exchange database, and KSYS coordinate-code errors - are covered in depth on the German support portal, which is the authoritative home for SEP content: [SEP1 to SEP3 conversion](https://support.geodin.com/hc/de/articles/360022314873-Konvertierung-von-SEP1-nach-SEP3), [SEP3 exchange database](https://support.geodin.com/hc/de/articles/115003373465-Import-externer-SEP3-Daten-mit-der-SEP3-Austausch-Datenbank), and KSYS cleanup for [SEP1](https://support.geodin.com/hc/de/articles/360012769899-Altdaten-der-SEP1-Objektarten-%C3%BCbernehmen-KSYS-bereinigen) / [SEP3](https://support.geodin.com/hc/de/articles/115003069829-SEP3-Bohrungen-in-ein-anderes-Projekt-%C3%BCbernehmen-KSYS-bereinigen). For the SEP object types themselves, see [Aufschluss Bohrdatenbank SEP 3](https://support.geodin.com/hc/de/articles/360016072840-Aufschluss-Bohrdatenbank-SEP-3) and [Benutzer-, Komplett- und Standardaufschluss (SEP 1)](https://support.geodin.com/hc/de/articles/360016072820-Benutzer-Komplett-und-Standardaufschluss-SEP-1) on the same portal. ### Coordinates change when the coordinate system differs When an object's coordinate system differs from the map or export target, GeoDin converts the coordinates automatically without prompting. If exact agreement with survey coordinates matters, keep source data and outputs in the same EPSG-coded system, and see [Coordinate systems and EPSG](/maps/coordinate-systems-and-epsg.md) for how GeoDin resolves systems. *** ## Diagnostics: SQL protocol The **SQL protocol** records all database operations performed by GeoDin for later analysis. The protocol captures the actions executed, their execution time, and whether they succeeded. It is especially useful when debugging newly developed complex SQL queries. ### Starting and stopping the protocol Start the protocol from the **Information** menu with **Start SQL protocol**. All SQL commands executed afterwards are recorded. To stop the protocol, select the same menu item - it is now labelled ![Stop SQL protocol](https://3138966068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOh9veY55xgALNVUW8siX%2Fuploads%2Fgit-blob-db5e13f0165aa6654c08cfce032d451edb0cf880%2Fstop-sql-protocol.png?alt=media) **Stop SQL protocol**. The recorded protocol is then displayed in a separate window and can be saved as a text file. You can also toggle the protocol with the keyboard shortcut **Alt+S**, without using the menu. If no entry here solves your problem, capture the SQL protocol around the failing action and send it with your request to [Get support](/support/get-support.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geodin.com/support/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.