Facing Error: Executing Runtime Operation Failed for Security Reasons: xxxxx After Moving to Different Environment

0
Hello all,   My Mendix application was initially deployed on-premise in a single server, but we recently moved it to a staging environment with a three-server setup: Database Server App Server (where Mendix Service Console is installed) Web Server The application is strictly for internal users and is not accessible from the internet. Both the old (working) and new servers are internal-only.   Issue: After migrating to the new setup, I am encountering the following error upon login: "Executing runtime operation failed for security reasons: xxxxx" The xxxx is a random string every time.   Additionally, in the Mendix console, I see the following message: "User 'MxAdmin' attempted to execute runtime operation "xxxx" but does not have the required permissions" I am unable to perform any actions in the application. Clicking any button results in the same error, and this issue affects all user roles, not just the admin. Even in overview pages, no data is displayed, although the records exist in the database.   What I Tried: Verified the database—data is present. Created new users via the REST service (using Postman) and confirmed I can create and retrieve user details without issues. Cleared browser cache. Tried logging in through a private/incognito window. Checked project security settings—no issues, as the same deployment package works fine in the old server. Has anyone encountered this issue before? Any suggestions on what could be causing this error in the new environment?   Thanks in advance!
asked
2 answers
1

The issue is resolved, the web folder was not updating in the web server after the deployment so I copy it manually after every deployment to fix this issue.

answered
0

To translate a query-id or operation-id to a readable xpath or microflow, you can take a look in the mda file. After unzipping, there should be a 'deployment/model' folder containing both operations.json and queries.json.

You can check the required user roles in these files as well for a given operation id or query id. Verify your own user roles by inspecting the class on the body element in your browser, for example: on this forum I only have "user" as user role.

image.png

Hopefully this helps you in the right direction!

Good luck!

answered