Issue

After restoring a database from production, attempting to change the MxAdmin password fails with the following error message displayed in the front end:

Configuring administrative account failed. Please verify that the password you filled in adheres to the password policy as configured in your model.

The application logs show the following error:

runtime-container/6dhwjWARNINGCore: Admin user role does not exist. Try starting the runtime first so that modeled user roles are synchronized with the database.

Environment

Applications hosted in Mendix Cloud

Cause

This issue occurs due to a synchronization mismatch between the restored database and the runtime environment. When a database is restored from production to another environment, the user roles and administrative account configuration may not be properly synchronized with the current runtime model, leading to password policy validation failures even though the MxAdmin account exists.

Solution / Workaround

To successfully reset the MxAdmin password after a database restore, follow these steps to ensure the Mendix runtime can synchronize user roles:

1. Stop the environment.
2. Restore the database.
3. Start the environment. This crucial step allows the Mendix runtime to synchronize the modeled user roles (including MxAdmin) with the newly restored database.
4. Change the password, ensure the password you are trying to set meets the MxAdmin password requirements: at least 8 characters including a special character, capital letter, and number.

Alternative workaround: If the database is already restored and still experiencing this issue, deploying a new package will resolve it. Deploying a new package forces a fresh synchronization of model objects to the database.

Additional information

NA