> 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/licensing.md).

# Licensing problems

Symptom-first fixes for license issues. For the full activation and renewal procedures, see [Activate your license](/installation-and-licensing/activating-your-license.md) and [Renew licence](/installation-and-licensing/renew-licence.md).

## License was renewed or paid, but GeoDin still shows it expired

A renewal, extension, or post-payment unlock happens on the license server side - your GeoDin client must still pick up the new entitlement:

* **Individual (single-user) license:** from release 15.3.18.482 the license updates automatically at GeoDin startup while the device is online. On older releases, update it manually as described in [Renew licence](/installation-and-licensing/renew-licence.md).
* **Professional (network) license:** the refresh is always manual - follow [Renew licence](/installation-and-licensing/renew-licence.md).

Licenses are time-limited (typically one year). Request the renewal in good time via [support](/support/get-support.md).

## Network software license is not recognized for some users

If some users cannot run GeoDin against a shared network license, check three things: the license file must grant **write permission** to every user, the `LicProtector313.dll` must be up to date on each client (or on the terminal server), and the license file must have been activated before first use.

## No GeoDin dongle found - LicProtector313.dll not registered (until GeoDin 9.0)

This is legacy guidance for the dongle-based licensing used until GeoDin 9.0. It is a different problem from the network license `LicProtector313.dll` check above - that one covers an up-to-date DLL on a shared network license; this one covers a missing or unregistered DLL on a dongle installation.

* Check whether `LicProtector313.dll` exists in the `BIN` folder of your GeoDin installation.
* If it exists, check the date of `geodin.exe`. If it is older than 2014-05-08, download the current program build for your GeoDin version from the GeoDin download archive.
* If `LicProtector313.dll` is missing, download it, unpack the archive, and place the files in the `BIN` folder of your GeoDin installation.
* If the DLL is present and `geodin.exe` is the newer build, run `register_admin.cmd` in the `BIN` folder as administrator (right-click > **Run as administrator**).
* If that fails, copy both `LicProtector313.dll` and `register_admin.cmd` to a local folder on the machine and run `register_admin.cmd` again from there.

## GIS Extension functions are grayed out

The GIS Extension's base functions (connecting to a GeoDin database, creating map layers) work without a license. The functions that write GeoDin data require a GeoDin installation plus a license for the **GIS Extension** module. If the advanced functions are grayed out, the module license is missing - see [Get support](/support/get-support.md) to extend your license.


---

# 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/licensing.md?ask=<question>&goal=<endgoal>
```

`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.