Most failures show a BMXAA message. The table below lists each symptom and what to do. Our lab also saw a “hang” that was not a hang.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that all 15 messages below, the backup check box and the Admin Mode settings are present with the same text (17 November 2026). The behaviour in the rows marked “Yes” was tested in our lab on Maximo 7.6.1.0 (3 and 4 November 2026: two Admin Mode on/off cycles and three applies on our own test object); we have not re-run it on Maximo Application Suite 9.1. Rows marked “Docs” were not reproduced on either version. The command-line steps are different on Maximo Application Suite 9.1 (see below).
IBM’s page: IBM’s current Maximo Manage documentation gives the same steps: “select Manage Admin Mode from the action menu”, “Click Turn Admin Mode ON”, “click Refresh Status to view the messages”, then “Select the Apply Configuration Changes action”.
Last checked: 17 November 2026
| Symptom | Message | What to do | Seen in lab? |
|---|---|---|---|
| Apply refused at once | BMXAA0578E Admin Mode required | Turn Admin Mode on first. Also shown for a new non-persistent attribute. | Yes |
| Apply refused | BMXAA0574E backup check box | Tick Do you have a current backup (and have one). | Yes |
| Apply refused | BMXAA0631E must run from command line | On Maximo 7.6: use the configdb tool with the server down. On Maximo Application Suite 9.1 this is different (see below). | Docs |
| Apply refused | BMXAA0576E nothing to configure | There are no pending changes. | Docs |
| Edits refused | BMXAA0572E configuration in process | Wait; use Refresh Status. | Docs |
| Admin Mode never comes on | BMXAA4011I and BMXAA9680I for each cron task | A long-running cron task or escalation is still working. Stop it. | Docs |
| Status box stuck on a countdown line | – | Not a hang. Click OK on any open pop-up and Refresh Status, or close and reopen the dialog. Check the real state before you cancel anything. | Yes |
| REST and integration calls fail during Admin Mode | HTTP 400 BMXAA3851E | Expected. Retry after Admin Mode is off (BMXAA4033I). | Yes |
| Cannot turn Admin Mode off | BMXAA8668E configuration still running | Wait for the configuration to end. | Docs |
| Several servers in a cluster | BMXAA3994W mixed Admin Mode | Run the change with one server only. | Docs |
| SQL error during apply | BMXAA0663E | Read the configuration log (on Maximo 7.6, in the tools log folder). | Docs |
| Migration Manager package | BMXAA6298E / BMXAA8239E | Plan package deployment around Admin Mode. | Docs |
What we observed in our lab: IBM support material says that clicking Apply without Admin Mode for a structural change appears to do nothing. On Maximo 7.6.1.0 we got a BMXAA0578E pop-up at once; if you see nothing, look for a pop-up behind the dialog. And the Admin Mode Status box sat on “All users will be logged out in 2 minutes” for 13 minutes although Admin Mode had been on for most of that time.
The Database Configuration steps and the messages above are the same. What is different is everything outside the application. Maximo Application Suite runs Maximo Manage in containers, so there is no application server to stop by hand and no tools folder to open. IBM’s documentation, APIs for administrative utilities, describes requests that stop and start the Maximo Manage pods and download log files. The same page says: “Do not use the SetAdminMode command-line interface from Manage tools to set the admin mode. The SetAdminMode command-line interface is not available in Maximo Application Suite setup as of now. You must use the Maximo Application Suite user interface or use the REST APIs to manage the admin mode.” We have not run a command-line configuration on Maximo Application Suite 9.1, so we do not describe one here.
On a Maximo 7.6.1.0 lab system we turned Admin Mode on and off twice and ran three applies on a test object of our own. We recorded every message and read the Admin Mode settings with read-only queries. The other messages come from the system’s message table and IBM’s documentation; those rows are marked “Docs”. On Maximo Application Suite 9.1 we read the messages, labels and Admin Mode settings; we did not turn Admin Mode on or apply anything there. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.
This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.