> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/getting-started/troubleshooting/you-dont-have-a-license-for-this-feature-warning.md).

# You don't have a license for this feature warning

## Problem

The licence appears as activated and valid, but the tool still cannot be used. This issue may occur when old or expired licence files remain on the computer and interfere with the currently active licence.

## **Solution**

First, open **Arkance Dock** and confirm that there are no other active licences besides the licence you have just activated.

Then navigate to the following folder:\
C:\ProgramData\AGA-CAD\TOOLS 4 BIM\\*\[Revit version]*\\*9237574730d0ae82aebacb4df458b8cca01b7111* *\[this code is unique for everyone]*

{% hint style="info" %}
Replace **\[Revit version]** with the relevant Revit version. The final folder name is unique to each computer or licence installation and may differ from the example shown below.
{% endhint %}

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FXtrFQhImcUTlU3FKblJX%2Fimage.png?alt=media&amp;token=b2185132-2e8b-42ca-84ad-acc2c245eebd" alt=""><figcaption></figcaption></figure>

The folder should contain only the current, valid, and unexpired `.lic` file. If it contains any additional `.lic` files, delete the obsolete or expired files.

After removing the unnecessary licence files restart Revit. The old licences should no longer interfere, and the tools should work as expected.


---

# 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.besmart.software/getting-started/troubleshooting/you-dont-have-a-license-for-this-feature-warning.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.