Mendix Administration.SaveNewAccount throws Internal server error when creating a new Team Member

0
Hi everyone,I'm using Mendix Studio Pro 10.24.8 and I'm having an issue when creating a new Team Member.I created a custom New Team Member page that contains the following fields:Full nameEmailUsernameUser roleLanguageProfile pictureNew passwordConfirm passwordThe Save button is configured as follows:On click: Call a microflowMicroflow: Administration.SaveNewAccountWhen I click Save, I get the following popup:"An error occurred, please contact your system administrator."The Console shows:An error occurred while executing an action of Expenses.TeamMember_New_Administrator.actionButton1: Internal server error The Administration.SaveNewAccount microflow is the standard one from the Administration module and contains:Retrieve AccountCheck if passwords matchSet password and save accountDelete AccountPasswordDataClose pageThe passwords match correctly, and I have also tried using different usernames, but the same error still occurs.I have already checked:Passwords matchDifferent usernameSave button correctly calls Administration.SaveNewAccountUnfortunately, the console only reports Internal server error and does not provide the actual cause.Does anyone know what could be causing this?Could it be related to:Missing or incorrect association?Account object not being created correctly?Security or access rules?Incorrect page context?Something else?Any help would be greatly appreciated.Thank you!
asked
1 answers
0

The "Internal server error" popup is only a generic client message. The actual exception should be available in the Runtime Console or Application.log.


A few things I would check:

  • Make sure the required associations (such as User Role and Language) are correctly set before calling Administration.SaveNewAccount.
  • Check whether you've customized the page and removed any required attributes or validations expected by the microflow.
  • Enable Set Log Levels for the Administration module to TRACE or DEBUG and reproduce the issue. The runtime log should reveal the actual exception instead of just "Internal server error".


Could you also share:

  • The complete runtime error from the console (stack trace).
  • A screenshot of your custom page.
  • Whether TeamMember is a specialization of Administration.Account or a separate entity.


That will make it much easier to identify the root cause.

answered