IBM Support

Getting BMXAA3851E error when logging in to Maximo even when Admin Mode is OFF

Technical Blog Post


Abstract

Getting BMXAA3851E error when logging in to Maximo even when Admin Mode is OFF

Body

Hello everyone! I want to share a certain scenario and how to resolve the BMXAA3851E error message when logging in to Maximo even if "Admin Mode" is not enabled. This case would be most applicable if you recently upgraded Maximo 6.x to Maximo 7.1.x. I know that this Maximo versions are old and obsolete but I just want this information out there because we never know who we might help, right?

 

After upgrading your environment from Maximo 6.x to Maximo 7.1.x, you are unable to access Maximo. You can already see the Maximo Log in Page and can enter your credentials but when you sign in, you get the following error:

 

BMXAA3851E - Connecting to the server has been temporarily disabled.

 

Usually, you get this message when you try to log in to Maximo while "Admin Mode" is ENABLED. Below are some documents explaining the BMXAA3851E error message and how to resolve it.

 

BMXAA3851E - Connecting to the Server Has Been Temporarily Disabled

Connecting to the server has been temporarily disabled with Admin Mode Off

"Admin Mode" function in Maximo 7.x

 

So you tried turning off the "Admin Mode" through the UI, manually turning it off using the SetAdminMode.bat command, and also verified that "Admin Mode" is already OFF in your database. However, you still can not log in to Maximo and getting the BMXAA38513 message.

 

RESOLUTION:

First, check the MAXSESSION and LOGINTRACKING tables to see if there are any records in them by running the following queries against your database.

 

- Select * from maxsession;
- Select * from logintracking;

 

If there are records in them, you can truncate them just to make sure we have clean tables. You can learn more about the MAXSESSION table here. Now try to log in and if the issue still persist, proceed with the next step.

 

Since you just upgraded from Maximo 6.x to Maximo 7.1, there are some cases where the "defaultvalue" for the LOGINTRACKING.ATTEMPTRESULT attribute in your database was not updated. To verify this, run the following queries below:

 

- Select objectname, attributename, domainid, defaultvalue From maxattribute Where objectname='LOGINTRACKING' And attributename='ATTEMPTRESULT' ;

- Select objectname, attributename, domainid, defaultvalue From maxattributecfg Where objectname='LOGINTRACKING' And attributename='ATTEMPTRESULT' ;

 

If the two queries above will return a "0" or "1" for the defaultvalue column then it was not updated when you upgraded to Maximo 7.1.x.  In Maximo 6.x, a defaultvalue of "0" or "1" would be valid. But In Maximo 7.1.x, the defaultvalue column was changed to AlphaNumeric and the valid values are described in this document.

 

To correct this, we can set the defaultvalue to have the out-of-the-box value of NULL. To do this, run the update statements below:

 

- Update maxattribute set defaultvalue=NULL Where objectname='LOGINTRACKING' And attributename='ATTEMPTRESULT' ;

- Update maxattributecfg set defaultvalue=NULL Where objectname='LOGINTRACKING' And attributename='ATTEMPTRESULT' ;

 

Go ahead and try to log in to Maximo. You should now be able to log in to your application without any issues.

 

That would be it for my first blog in 2017!

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11130421