Maximo Open Forum

 View Only

 Not able to login to manage after upgrade

  • Administration
Poonam Aswani's profile image
Poonam Aswani posted 07-03-2025 05:07

Hello Maximo Folks,

We have upgraded from 7.6 to MAS 9. Now after upgrade, users are not getting synced to Manage from MAS. We modified existing user/ created a new user but they are failing to sync. Hence, we are not able to login to manage. Any suggestions/ideas which can lead to resolution would be helpful.

Aaron Paroulek's profile image
Aaron Paroulek posted 07-03-2025 11:40

Hi Poonam - We had a similar issue recently in our environment in an attempted upgrade to 9.1.  We found that there was a reference to a System Property called: mxe.useradmin, which was undefined in our system (with an Oracle back-end).  With this missing System Property, the MASUSERSYNC Cron Task would run and do nothing.  We went ahead and updated the value, like this:

UPDATE maxpropvalue SET propvalue = 'maxadmin' WHERE propname = 'mxe.useradmin';

After we re-ran the MASUSERSYNC Cron Task, we found that our users had synced over to Core.

Hopefully this work for your as well.

Aaron Paroulek

Maven Asset Management

Poonam Aswani's profile image
Poonam Aswani posted 07-04-2025 04:11

Hi @Aaron Paroulek, Couldnt reply to your answer, hence posting this way!
I am using db2, should this property exist in db2 also?

Also, this property doesnt exist itself in db2 currently, so shall I insert it in maxprop table, and if yes how will it refresh/take effect? I assume it was existing in your system but not updated with correct value.

Thanks for providing your inputs!

Aaron Paroulek's profile image
Aaron Paroulek posted 07-07-2025 10:25

Good morning - Yes, I think I would try to add the property directly to the maxprop and maxpropvalue tables, even for DB2 (although this did exist for us in Oracle already).  As far as refreshing the property, we were running this update statement to make sure our Cron Task ran: update crontaskinstance SET active = 1 WHERE crontaskname = 'MASUSERSYNC'; 

We would then just delete the Cron pod, so it would start itself back up, taking the new property values and running our cron task again.  If you aren't using any bundles, then you should be OK to delete your All pod, so everything is refreshed.

Aaron Paroulek

Maven Asset Management

Related Content