> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/fr/knowledge-base/troubleshooting-articles/ioexception-the-process-cannot-access-the-file.md).

# IOException - the process cannot access the file

Corrigez l'erreur IOException - the process cannot access the file sur les enregistrements RDP en ajoutant une variable de date ou d'heure au nom du fichier d'enregistrement.

```
IOException - The process cannot access the file 'C:\Users*User*\AppData\Local\Temp\RDM\record.mp4' because it is being used by another process.
```

### Solution

Cette erreur peut être évitée en ajoutant une variable au nom de votre enregistrement. Ainsi, Remote Desktop Manager n'aura pas de difficulté à tenter d'écraser un enregistrement déjà existant. En général, nous recommandons d'utiliser des variables telles que `$DATE_TEXT$` ou `$TIME_TEXT$` pour identifier l'enregistrement.

Par exemple, si vous avez modifié votre chemin d'accès pour :

*`C:\Users*User\AppData\Local\Temp\RDM\record-$DATE_TEXT$-$TIME-TEXT$.mp4`*

Le nom de votre enregistrement ressemblerait à `record-2202020-100257.mp4`. Cela garantira que chaque enregistrement porte un nom unique.


---

# 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.devolutions.net/rdm/fr/knowledge-base/troubleshooting-articles/ioexception-the-process-cannot-access-the-file.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.