Topic
  • 10 replies
  • Latest Post - ‏2015-10-06T19:57:29Z by Bowser
Kareem Naguib
Kareem Naguib
65 Posts

Pinned topic problem with turning admin mode on in Maximo

‏2013-08-29T22:16:24Z |

Hello Professionals,

 

I have a problem with turning on Admin mode after we have installed Maximo Enterprise Asset Management 7.5.0.4,

After the installation, i tried to create GL Component, but when i try to turn on admin mode, it stuck and don't display anything, refresh status button don't display anything too, 

i tried to use setadminmode.bat to turn it on but it display a message that admin mode is pending turning on, 

what may cause this problem?

 

Thanks in advance

  • Kareem Naguib
    Kareem Naguib
    65 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-08-30T12:51:17Z  
    BMXAA4030I - Starting to set Admin Mode ON.
    BMXAA4004I - Administration mode is pending (turning on) for this server.
    BMXAA4013I - Setting maxvar ADMINRESTART to ON.
    BMXAA4008I - Notifying users to sign out.
    BMXAA4036W - All users will be logged out in 1 minutes. Save your work.

     

    the above messages are the messages appeared after clicking turn on admin mode

  • bgbaird
    bgbaird
    281 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-08-30T14:49:52Z  
    BMXAA4030I - Starting to set Admin Mode ON.
    BMXAA4004I - Administration mode is pending (turning on) for this server.
    BMXAA4013I - Setting maxvar ADMINRESTART to ON.
    BMXAA4008I - Notifying users to sign out.
    BMXAA4036W - All users will be logged out in 1 minutes. Save your work.

     

    the above messages are the messages appeared after clicking turn on admin mode

    Kareem,   Are you running clustered servers?  If so, try it after stopping all but one server.  If that fixes it, try going into the admin mode logged in to a specific server, rather than the cluster.  I've run into issues a couple of times on 7.5.0.3 with admin mode not being really good at cluster awareness.

    Also, I know this was an issue in some earlier releases.  Maybe it reared its head again:

    http://www-01.ibm.com/support/docview.wss?uid=swg1IZ40000

    Brian

  • Kareem Naguib
    Kareem Naguib
    65 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-08-30T17:29:44Z  
    • bgbaird
    • ‏2013-08-30T14:49:52Z

    Kareem,   Are you running clustered servers?  If so, try it after stopping all but one server.  If that fixes it, try going into the admin mode logged in to a specific server, rather than the cluster.  I've run into issues a couple of times on 7.5.0.3 with admin mode not being really good at cluster awareness.

    Also, I know this was an issue in some earlier releases.  Maybe it reared its head again:

    http://www-01.ibm.com/support/docview.wss?uid=swg1IZ40000

    Brian

    Brian, thank you very much for your support, you are always supporting me,

    I'm running on single server, and i think the problem described in the link you mentioned is exactly mine,

    what are your suggestions to overcome this problem?

  • Kareem Naguib
    Kareem Naguib
    65 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-08-31T10:54:35Z  
    • bgbaird
    • ‏2013-08-30T14:49:52Z

    Kareem,   Are you running clustered servers?  If so, try it after stopping all but one server.  If that fixes it, try going into the admin mode logged in to a specific server, rather than the cluster.  I've run into issues a couple of times on 7.5.0.3 with admin mode not being really good at cluster awareness.

    Also, I know this was an issue in some earlier releases.  Maybe it reared its head again:

    http://www-01.ibm.com/support/docview.wss?uid=swg1IZ40000

    Brian

    I found the below errors in systemout.log file 

    do you have any idea how to resolve them

    [8/31/13 13:45:46:856 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:856 [INFO] [MXServer] [] BMXAA4036W - All users will be logged out in 1 minutes. Save your work.
    [8/31/13 13:45:46:871 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:856 [ERROR] [MXServer] [] BMXAA6448E - Cache ADMINMODE initializaiton failed. Log out and then log in again to refresh your database connection.
    psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date.
    at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99)
    at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61)
    at psdi.mbo.MboValue.validate(MboValue.java:1698)
    at psdi.mbo.MboValue.setValue(MboValue.java:890)
    at psdi.mbo.MboValue._setValue(MboValue.java:1564)
    at psdi.mbo.MboValue.setValue(MboValue.java:1549)
    at psdi.mbo.Mbo.setValue(Mbo.java:2631)
    at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612)
    at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326)
    at psdi.security.AdminModeManager.reload(AdminModeManager.java:179)
    at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74)
    at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876)
    at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)
    [8/31/13 13:45:46:871 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:871 [ERROR] [MXServer] [] BMXAA0232E - Not a valid expiration date.
    psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date.
    at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99)
    at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61)
    at psdi.mbo.MboValue.validate(MboValue.java:1698)
    at psdi.mbo.MboValue.setValue(MboValue.java:890)
    at psdi.mbo.MboValue._setValue(MboValue.java:1564)
    at psdi.mbo.MboValue.setValue(MboValue.java:1549)
    at psdi.mbo.Mbo.setValue(Mbo.java:2631)
    at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612)
    at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326)
    at psdi.security.AdminModeManager.reload(AdminModeManager.java:179)
    at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74)
    at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876)
    at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)
    [8/31/13 13:45:49:991 EEST] 00000043 SystemOut     O 31 Aug 2013 13:45:49:991 [WARN] [MXServer] [] BMXAA7785W - The property mxe.doclink.usefileprompt does not exist in the MAXPROP or MAXPROPVALUE tables.
    [8/31/13 13:45:53:033 EEST] 00000034 SystemOut     O 31 Aug 2013 13:45:53:033 [INFO] [MXServer] [CID-CRON-5652] Correlation started.
    [8/31/13 13:45:53:049 EEST] 00000034 SystemOut     O 31 Aug 2013 13:45:53:049 [INFO] [MXServer] [CID-CRON-5652] Correlated data: BEGIN InstanceName:AsyncImmediate TaskName:AsyncImmediateJobCron ElapsedTime:16 ms  END
     

     

  • Kareem Naguib
    Kareem Naguib
    65 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-09-01T10:11:29Z  

    I found the below errors in systemout.log file 

    do you have any idea how to resolve them

    [8/31/13 13:45:46:856 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:856 [INFO] [MXServer] [] BMXAA4036W - All users will be logged out in 1 minutes. Save your work.
    [8/31/13 13:45:46:871 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:856 [ERROR] [MXServer] [] BMXAA6448E - Cache ADMINMODE initializaiton failed. Log out and then log in again to refresh your database connection.
    psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date.
    at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99)
    at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61)
    at psdi.mbo.MboValue.validate(MboValue.java:1698)
    at psdi.mbo.MboValue.setValue(MboValue.java:890)
    at psdi.mbo.MboValue._setValue(MboValue.java:1564)
    at psdi.mbo.MboValue.setValue(MboValue.java:1549)
    at psdi.mbo.Mbo.setValue(Mbo.java:2631)
    at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612)
    at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326)
    at psdi.security.AdminModeManager.reload(AdminModeManager.java:179)
    at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74)
    at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876)
    at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)
    [8/31/13 13:45:46:871 EEST] 00000052 SystemOut     O 31 Aug 2013 13:45:46:871 [ERROR] [MXServer] [] BMXAA0232E - Not a valid expiration date.
    psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date.
    at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99)
    at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61)
    at psdi.mbo.MboValue.validate(MboValue.java:1698)
    at psdi.mbo.MboValue.setValue(MboValue.java:890)
    at psdi.mbo.MboValue._setValue(MboValue.java:1564)
    at psdi.mbo.MboValue.setValue(MboValue.java:1549)
    at psdi.mbo.Mbo.setValue(Mbo.java:2631)
    at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612)
    at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326)
    at psdi.security.AdminModeManager.reload(AdminModeManager.java:179)
    at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74)
    at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876)
    at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)
    [8/31/13 13:45:49:991 EEST] 00000043 SystemOut     O 31 Aug 2013 13:45:49:991 [WARN] [MXServer] [] BMXAA7785W - The property mxe.doclink.usefileprompt does not exist in the MAXPROP or MAXPROPVALUE tables.
    [8/31/13 13:45:53:033 EEST] 00000034 SystemOut     O 31 Aug 2013 13:45:53:033 [INFO] [MXServer] [CID-CRON-5652] Correlation started.
    [8/31/13 13:45:53:049 EEST] 00000034 SystemOut     O 31 Aug 2013 13:45:53:049 [INFO] [MXServer] [CID-CRON-5652] Correlated data: BEGIN InstanceName:AsyncImmediate TaskName:AsyncImmediateJobCron ElapsedTime:16 ms  END
     

     

    Any updates?

  • SASHULL
    SASHULL
    393 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2013-09-06T14:46:22Z  

    Any updates?

    Kareem,

     

    I'm pretty sure your error is this: http://www-01.ibm.com/support/docview.wss?uid=swg1IV44530

    There is an IFIX available 7504 IFIX05 that is supposed to resolve it. I don't have an environment where I've encountered this error but that fix should prevent it in the future.

  • Sudhindra Shivanagere
    2 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2015-04-25T04:09:00Z  
    • SASHULL
    • ‏2013-09-06T14:46:22Z

    Kareem,

     

    I'm pretty sure your error is this: http://www-01.ibm.com/support/docview.wss?uid=swg1IV44530

    There is an IFIX available 7504 IFIX05 that is supposed to resolve it. I don't have an environment where I've encountered this error but that fix should prevent it in the future.

    Hi Team,

    We are also facing the same issue and the above mentioned fix will resolve the Admin mode issue completely? or do we need to take any precaution before applying the fix which is mentioned above..

     

    Thanks in advance...

     

    Please find the admin mode log which i have captured..

     

    [4/24/15 23:51:17:449 EDT] 0000001f SystemOut O 24 Apr 2015 23:51:17:449 [INFO] [MXServerUI] [] BMXAA6719I - USER = (SUDHSHIV) SPID = (459) app (null) object (DMPACKAGEDEF) : select count(*) from dmpackagedef where type in (select value from synonymdomain where domainid='DMPKGTYPE' and maxvalue='CHANGE') and active=1 [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA6447I - Reloading ON of ADMINMODE in Maximo cache. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4030I - Starting to set Admin Mode ON. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4004I - Administration mode is pending (turning on) for this server. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4013I - Setting maxvar ADMINRESTART to ON. [4/24/15 23:51:17:551 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:551 [INFO] [MXServerUI] [] BMXAA4008I - Notifying users to sign out. [4/24/15 23:51:17:573 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:573 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (711) app (null) object (BULLETINBOARD) : select * from bulletinboard where subject like 'BMXAA4036W%' and postdate <= { ts '2015-04-24 20:51:16.912' } and expiredate >= { ts '2015-04-24 20:51:16.912' } [4/24/15 23:51:17:781 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:781 [INFO] [MXServerUI] [] select seed, prefix from autokey where autokeyname = 'BULLETINBOARDID' and orgid is null and siteid is null [4/24/15 23:51:17:789 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:789 [INFO] [MXServerUI] [] select bulletinboardid from bulletinboard where bulletinboardid= ? [4/24/15 23:51:17:835 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:835 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (889) app (null) object (PLUSPCUSTASSOC) : select * from pluspcustassoc where ownertable='BULLETINBOARD' and ownerid= 3124 [4/24/15 23:51:17:856 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:855 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (295) app (null) object (SYNONYMDOMAIN) : select * from synonymdomain where ((value= 'DRAFT' ) and (domainid = 'BULLETINSTATUS' )) and (rownum<=1000) [4/24/15 23:51:17:885 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:885 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (972) app (null) object (ALNDOMAIN) : select * from alndomain where ((value= 'BULLETIN' ) and (domainid = 'PMTCOBBSHOWAS' )) and (rownum<=1000) [4/24/15 23:51:17:889 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:889 [INFO] [MXServerUI] [] BMXAA4036W - All users will be logged out in 0 minutes. Save your work. [4/24/15 23:51:17:889 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:889 [ERROR] [MXServerUI] [] BMXAA6448E - Cache ADMINMODE initializaiton failed. Log out and then log in again to refresh your database connection. psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date. at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99) at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61) at psdi.mbo.MboValue.validate(MboValue.java:1698) at psdi.mbo.MboValue.setValue(MboValue.java:890) at psdi.mbo.MboValue._setValue(MboValue.java:1564) at psdi.mbo.MboValue.setValue(MboValue.java:1549) at psdi.mbo.Mbo.setValue(Mbo.java:2631) at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612) at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326) at psdi.security.AdminModeManager.reload(AdminModeManager.java:179) at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74) at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876) at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994) [4/24/15 23:51:17:890 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:890 [ERROR] [MXServerUI] [] BMXAA0232E - Not a valid expiration date. psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date. at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99) at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61) at psdi.mbo.MboValue.validate(MboValue.java:1698) at psdi.mbo.MboValue.setValue(MboValue.java:890) at psdi.mbo.MboValue._setValue(MboValue.java:1564) at psdi.mbo.MboValue.setValue(MboValue.java:1549) at psdi.mbo.Mbo.setValue(Mbo.java:2631) at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612) at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326) at psdi.security.AdminModeManager.reload(AdminModeManager.java:179) at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74) at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876) at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)

     

     

    Thanks,

    Sudhindra

  • bgbaird
    bgbaird
    281 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2015-04-27T12:05:29Z  

    Hi Team,

    We are also facing the same issue and the above mentioned fix will resolve the Admin mode issue completely? or do we need to take any precaution before applying the fix which is mentioned above..

     

    Thanks in advance...

     

    Please find the admin mode log which i have captured..

     

    [4/24/15 23:51:17:449 EDT] 0000001f SystemOut O 24 Apr 2015 23:51:17:449 [INFO] [MXServerUI] [] BMXAA6719I - USER = (SUDHSHIV) SPID = (459) app (null) object (DMPACKAGEDEF) : select count(*) from dmpackagedef where type in (select value from synonymdomain where domainid='DMPKGTYPE' and maxvalue='CHANGE') and active=1 [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA6447I - Reloading ON of ADMINMODE in Maximo cache. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4030I - Starting to set Admin Mode ON. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4004I - Administration mode is pending (turning on) for this server. [4/24/15 23:51:17:451 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:451 [INFO] [MXServerUI] [] BMXAA4013I - Setting maxvar ADMINRESTART to ON. [4/24/15 23:51:17:551 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:551 [INFO] [MXServerUI] [] BMXAA4008I - Notifying users to sign out. [4/24/15 23:51:17:573 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:573 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (711) app (null) object (BULLETINBOARD) : select * from bulletinboard where subject like 'BMXAA4036W%' and postdate <= { ts '2015-04-24 20:51:16.912' } and expiredate >= { ts '2015-04-24 20:51:16.912' } [4/24/15 23:51:17:781 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:781 [INFO] [MXServerUI] [] select seed, prefix from autokey where autokeyname = 'BULLETINBOARDID' and orgid is null and siteid is null [4/24/15 23:51:17:789 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:789 [INFO] [MXServerUI] [] select bulletinboardid from bulletinboard where bulletinboardid= ? [4/24/15 23:51:17:835 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:835 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (889) app (null) object (PLUSPCUSTASSOC) : select * from pluspcustassoc where ownertable='BULLETINBOARD' and ownerid= 3124 [4/24/15 23:51:17:856 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:855 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (295) app (null) object (SYNONYMDOMAIN) : select * from synonymdomain where ((value= 'DRAFT' ) and (domainid = 'BULLETINSTATUS' )) and (rownum<=1000) [4/24/15 23:51:17:885 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:885 [INFO] [MXServerUI] [] BMXAA6719I - USER = (MAXADMIN) SPID = (972) app (null) object (ALNDOMAIN) : select * from alndomain where ((value= 'BULLETIN' ) and (domainid = 'PMTCOBBSHOWAS' )) and (rownum<=1000) [4/24/15 23:51:17:889 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:889 [INFO] [MXServerUI] [] BMXAA4036W - All users will be logged out in 0 minutes. Save your work. [4/24/15 23:51:17:889 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:889 [ERROR] [MXServerUI] [] BMXAA6448E - Cache ADMINMODE initializaiton failed. Log out and then log in again to refresh your database connection. psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date. at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99) at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61) at psdi.mbo.MboValue.validate(MboValue.java:1698) at psdi.mbo.MboValue.setValue(MboValue.java:890) at psdi.mbo.MboValue._setValue(MboValue.java:1564) at psdi.mbo.MboValue.setValue(MboValue.java:1549) at psdi.mbo.Mbo.setValue(Mbo.java:2631) at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612) at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326) at psdi.security.AdminModeManager.reload(AdminModeManager.java:179) at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74) at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876) at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994) [4/24/15 23:51:17:890 EDT] 00000027 SystemOut O 24 Apr 2015 23:51:17:890 [ERROR] [MXServerUI] [] BMXAA0232E - Not a valid expiration date. psdi.util.MXApplicationWarningException: BMXAA0232E - Not a valid expiration date. at psdi.app.bulletinboard.FldDatePair.validate(FldDatePair.java:99) at psdi.app.bulletinboard.FldBBExpireDate.validate(FldBBExpireDate.java:61) at psdi.mbo.MboValue.validate(MboValue.java:1698) at psdi.mbo.MboValue.setValue(MboValue.java:890) at psdi.mbo.MboValue._setValue(MboValue.java:1564) at psdi.mbo.MboValue.setValue(MboValue.java:1549) at psdi.mbo.Mbo.setValue(Mbo.java:2631) at psdi.security.AdminModeManager.logoutUsers(AdminModeManager.java:612) at psdi.security.AdminModeManager.setAdminON(AdminModeManager.java:326) at psdi.security.AdminModeManager.reload(AdminModeManager.java:179) at psdi.mbo.MaximoCacheWrapper.reload(MaximoCacheWrapper.java:74) at psdi.server.MXServer.reloadMaximoCache(MXServer.java:876) at psdi.server.MXServer$AdminModeThread.run(MXServer.java:994)

     

     

    Thanks,

    Sudhindra

    Sudhindra, ALWAYS take precautions before applying ANY HF, FP, or Version upgrade!  I've been doing this a while, and always test and validate in a true development environment.  I would recommend having a minimum of 3 environments.  Production, Pre-Production, and Test/Development (I have 3 Dev environments).  In my case, everything happens in  a Development space first.  This includes fixes, patches, upgrades, and ALL work I do as well.

    Brian.

  • Sudhindra Shivanagere
    2 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2015-04-27T12:20:30Z  
    • bgbaird
    • ‏2015-04-27T12:05:29Z

    Sudhindra, ALWAYS take precautions before applying ANY HF, FP, or Version upgrade!  I've been doing this a while, and always test and validate in a true development environment.  I would recommend having a minimum of 3 environments.  Production, Pre-Production, and Test/Development (I have 3 Dev environments).  In my case, everything happens in  a Development space first.  This includes fixes, patches, upgrades, and ALL work I do as well.

    Brian.

    Thanks Brian. 

  • Bowser
    Bowser
    97 Posts

    Re: problem with turning admin mode on in Maximo

    ‏2015-10-06T19:57:29Z  
    • SASHULL
    • ‏2013-09-06T14:46:22Z

    Kareem,

     

    I'm pretty sure your error is this: http://www-01.ibm.com/support/docview.wss?uid=swg1IV44530

    There is an IFIX available 7504 IFIX05 that is supposed to resolve it. I don't have an environment where I've encountered this error but that fix should prevent it in the future.

    To avoid this problem, "Number of Minutes for User Logout" must be 2 or greater, otherwise the EXPIREDATE will be before the POSTDATE on the generated BULLETINBOARD record.

     

    But you're probably reading this because you haven't avoided the problem. In that case, the solution in Oracle SQL terms is:
    update maxpropvalue set propvalue = '2' where propname = 'mxe.adminmode.logoutmin';
    commit;
    -- then restart Maximo.

    (If memory serves: DB2 users should be able to use nearly the same syntax. SQL Server users will have to preceed the update with 'begin tran adminmodefix', remove the semicolon from the update, and replace the 'commit;' with 'commit tran adminmodefix'.)