IBM Support

IJ28833: FIRST LOG IN USING TOKEN LICENSING WITH ANYWHERE PERMISSION FAILS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:
    User occasionally sees a white screen when logging in
    to Maximo.
    Error displayed in logs.
    [10/12/20 7:54:46:903 EDT]
    00000211 SystemOut O 12 Oct 2020 07:54:46:865 [ERROR]
    [MAXMOBILE2] [] Token License: Failed while loading application
    startcntr for USERIDMAXADMIN
    java.lang.NullPointerException
    	at
    psdi.app.tokenlic.TokenLicenseUtil.findListOfFeaturesForCurrentU
    ser(TokenLicenseUtil.java:925)
    	at psdi.app.tokenlic.TokenLicens
    eUtil.loadApp(TokenLicenseUtil.java:714)
    	at psdi.webclient.syst
    em.controller.SystemEventHandler.loadapp(SystemEventHandler.java
    :204)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMe
    thodAccessorImpl.java:90)
    	at sun.reflect.DelegatingMethodAccess
    orImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    	at
    java.lang.reflect.Method.invoke(Method.java:508)
    PERFORMANCE
    ISSUE:
    NA
    STEPS TO REPRODUCE:
    Maximo 761, setup token
    licensing, install Anywhere, log in as user with anywhere
    permission
    CURRENT ERRONEOUS RESULT:
    White screen
    EXPECTED
    RESULT:
    log in successfully
    ADDITIONAL INFO:
    NA
    ENVIRONMENT
    (SYSTEM INFO):
    App Server	IBM WebSphere Application Server
    9.0.5.5
    Version
    IBM Maximo Asset Management Scheduler 7.6.7.3
    Build 20190514-1348 DB Build V7673-78 HFDB Build HF7673-14
    IBM
    Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
    V7640-12
    IBM Tpae Integration Framework
    7.6.1.1-MIF_7611_IFIX.20200402-1009 Build 20190422-1259 DB
    Build V7611-01
    IBM Maximo APM - Asset Health Insights 7.6.1.1
    Build 20190813-2128 DB Build V7611-19
    IBM Maximo for
    Transportation 7.6.2.5-20200814-1625 Build 20180730-2210 DB
    Build V7625-10 HFDB Build HF7625-17
    IBM Maximo Archiving with
    Optim 7.6.0.0 Build 20150819-0849 DB Build V7600-01
    Tivoli's
    process automation engine 7.6.1.1-IFIX20200724-1613 Build
    20190514-1348 DB Build V7611-365 HFDB Build HF7611-28
    IBM
    Maximo Asset Management Work Centers 7.6.0.4 Build $build$ DB
    Build V7604-119
    IBM Maximo Spatial Asset Management
    7.6.0.5-20200728-1718 Build 20190522-1410 DB Build V7605-09
    HFDB Build HF7605-07
    IBM Maximo Asset Management 7.6.1.1 Build
    20190514-1348 DB Build V7611-01
    IoT Connection Utility 7.6.0.2
    Build 20190426-2206 DB Build V7602-07
    IBM Maximo Health, Safety
    and Environment Manager 7.6.1.0-20200805-1125 Build
    20161020-0816 DB Build V7610-01
    TPAE OSLC Object Structure
    7.6.4.0 Build 20200219_092917-0500 DB Build V7640-04
    Server
    OS	Linux 3.10.0-1127.19.1.el7.x86_64
    Server DB	DB2/LINUXX8664
    11.1 (SQL11014)
    LOCAL FIX: N/A
    SECURITY IMPACT (Y/N): N
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who have access to ANYWHERE                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * After Application server restart, login of users fail when   *
    * users have access to ANYWHERE. If a user who doesn't have    *
    * access to ANYWHERE logs in then the issue gets resolved and  *
    * users who have access to ANYWHERE can also login.            *
    ****************************************************************
    

Problem conclusion

  • _The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release TPAE 7.6.1.3_
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ28833

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-20

  • Closed date

    2021-03-17

  • Last modified date

    2021-03-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MAXIMO SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
18 March 2021