Expanding on Tim's message, it looks like you have the system property mxe.AllowLDAPUsers enabled. This tells Maximo to allow any LDAP user even if they don't have a Maximo user record today. If Maximo thinks the user doesn't exist it will go and create the user record. That creation is failing in this case.
I've never liked that system property so I've never enabled it (I'd rather control who uses the Maximo system). Try and find the user account in the MAXUSER table and compare the loginid case to (typically) the SAMAccountName in Active Directory. You want to make sure that matches. Or you can ensure that each loginid is fully uppercase and then enable the mxe.convertloginid system property which will convert it to uppercase before doing a comparison. This helps avoid issues where a user might type maxadmin but it might be Maxadmin in Active Directory.
The last thing to check on the MAXUSER record is the status. Maximo allows you to "DELETE" a user record which changes the status to DELETED and then hides it from the front end. I've seen people do this thinking they can then recreate the record because in most cases in Maximo, deleting a record actually deletes it from the system. But if someone did that for this user you'd be stuck. The only way to fix this is to update the status via the backend to a different status (like ACTIVE) and then add the user back to the necessary security groups (like the EVERYONE/MAXEVERYONE group as well as the necessary AD groups).
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Wed December 22, 2021 06:32 AM
From: Shlomo Shvartz
Subject: User can not Login to Maximo
User can not Login to Maximo,The user is from the AD
If anyone can help me Thanks.
------------------------------
Shlomo Shvartz
------------------------------
#AssetandFacilitiesManagement
#Maximo