---
title: "TYPO3 Exception 1289918325"
manual: "TYPO3 Exceptions"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3exceptions:typo3-exception-1289918325"
source: "Exceptions/1289918325.rst"
rendered: "2026-10-13T16:58:17+00:00"
---

# TYPO3 Exception 1289918325 {#typo3-exception-1289918325}

> [!NOTE]
> Below, the TYPO3 community may have provided additional information or
> solutions for this exception. However, these may or may not apply to your
> particular case. If you can provide more information, you should come back
> here and add your experience and solution steps to this issue once you have
> resolved it.
>
> General TYPO3 troubleshooting tips can be found in the *Troubleshooting*
> section in the menu. You can also ask questions and receive support in the
> [TYPO3 Questions category on talk.typo3.org](https://talk.typo3.org/c/typo3-questions/).
>
> To add your experience, click "Edit on GitHub" above and follow the
> ["Edit on GitHub" workflow](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/EditOnGithub.html#docs-contribute-github-method).
> Also check out
> [our tip on Coding Style and reST](https://docs.typo3.org/permalink/t3exceptions:tip-about-rest-coding-style).

## #1289918325: Module 'my_module' is not configured. {#1289918325-module-my-module-is-not-configured}

This message appears when trying to load a module from BE context
menu. The module was configured in `Route.php` and loaded via
`BackendControllerHook`.

This problem appears when changing a module name or when old module names are
still cached (for example when upgrading the TYPO3 core or extensions).

The solution is to clear all caches (either via the install tool or if that
does not help via manually removing the files in `typo3temp`).