Maximo Open Forum

Expand all | Collapse all

Unable to login to Maximo Anywhere

  • 1.  Unable to login to Maximo Anywhere

    Posted 19 days ago
    Dear Team,

    We are unable to login to Maximo Anywhere as the login screen keeps rounding.Having set the device to USB debug mode,below are the messages observed from logs,Can someone please suggest what is the step we could do to resolve the issue

    name: "storeNotFound", messageKey: "storeNotFound", params: Array(1), stack: "Cannot find the store called stagingTransactionQue…tion/no_backup/www/default/dojo/dojo.js:2:280291)"}messageKey: "storeNotFound"name: "storeNotFound"params: ["stagingTransactionQueue"]stack: "Cannot find the store called stagingTransactionQueue↵ at Object._getStore (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/store/PersistenceManager.js:193:11)↵ at Object.getStageTransactionRecords (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/store/PersistenceManager.js:1003:21)↵ at Object._flushStageTransactions (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/model/PushingCoordinatorService.js:373:23)↵ at Object.flush (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/model/PushingCoordinatorService.js:60:9)↵ at Object._synchronizeToTheServer (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:94:37)↵ at Object.connectDetected (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:58:9)↵ at file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:47:12↵ at _7da (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:280291)"__proto__: Object "Cannot find the store called stagingTransactionQueue
    at Object._getStore (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/store/PersistenceManager.js:193:11)
    at Object.getStageTransactionRecords (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/store/PersistenceManager.js:1003:21)
    at Object._flushStageTransactions (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/model/PushingCoordinatorService.js:373:23)
    at Object.flush (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/model/PushingCoordinatorService.js:60:9)
    at Object._synchronizeToTheServer (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:94:37)
    at Object.connectDetected (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:58:9)
    at file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:47:12
    at _7da (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:280291)
    ----------------------------------------
    rejected at _7e0 (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:280932)
    at _7da (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:280543)
    at _7d4 (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:280155)
    at _7d9.resolve (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:281616)
    at Object._reportConnectionStatus (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/_DeviceConnectivityChecker.js:201:28)
    at Object.onSuccess (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/_DeviceConnectivityChecker.js:65:31)
    at onConnectSuccess (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:8565:12)
    at Object.bound [as onSuccess] (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:1023:27)
    at klass.onSuccess (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:3800:26)
    at klass.onWlSuccess (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:3773:12)
    ----------------------------------------
    Error
    at Promise.then._7e7.then (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:282104)
    at Object.<anonymous> (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/js/platform/comm/ConnectionHeartBeat.js:45:28)
    at HTMLDocument.<anonymous> (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/dojo/dojo.js:2:292076)
    at dispatchForgroundEvent (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:16658:18)
    at Channel.<anonymous> (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/worklight.js:16651:5)
    at Channel.fire (file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/cordova.js:813:23)
    at file:///data/user/0/com.ibm.iot.maximoanywhere.workexecution/no_backup/www/default/worklight/cordova.js:226:49"
    #Mobility

    ------------------------------
    Mahadevan Ramakrishnan
    Tata Consultancy Services
    ------------------------------


  • 2.  RE: Unable to login to Maximo Anywhere

    Posted 18 days ago
    We've never seen anything like this with our Anywhere customers nor can I think of any IBM posted issue like it. Purely a guess based on the messages in the logs but it seems like the JSON store wasn't able to be created successfully on the device. We've seen issues in the past where certain versions of the underlying Operating system (such as Android 4.4) had issues with certain versions of Anywhere but it's been a while since we've seen that so assuming you're on recent product (Anywhere 7.6.3/7.6.3.1/7.6.4) I would assume you'd be fine.

    Unfortunately in a scenario like this it's best to work with IBM as they'll need to understand exactly what version is deployed (including any IFIXes), how the apps were built, how it was customized, how they're being deployed (via MDM or being installed from appcenter), what version of OS you're using on your devices, etc. The database side of Anywhere is much deeper than almost anyone outside of the IBM development team would be informed about.

    ------------------------------
    Steven Shull
    Projetech
    ------------------------------



  • 3.  RE: Unable to login to Maximo Anywhere

    Posted 11 days ago
    Thanks Steven for your inputs.We are on version 7.6.3.1 and the app was working fine after applying the Interim fix 002 for a few days before it crashed down.We have no clue of the issue from the USB debug level logs and hence had posted it on the forum.

    Also we have to deploy the same apk onto the production environment as the customer has not agreed for enabling the internet access on the production environment due to which we are unable to build the apk file in the production envirornment after aplying the Ifix.With such an unstable behavior of the app from the pre-production environment,we are worried in applying the same onto the production environment.

    We cleared the cache,uninnstalled and re-installed but no luck all these days and after doing a build mobile first and redeploying the anywhere war file,it started working few days back and hence it is all the more strange behavior.

    ------------------------------
    Mahadevan Ramakrishnan
    Tata Consultancy Services
    ------------------------------



  • 4.  RE: Unable to login to Maximo Anywhere

    Posted 17 days ago
    I'm going to agree with Steven, we don't yet have enough information, just a lot of assumptions.  Like when you report this to IBM, we too need to know:
    • the Maximo Anywhere version
    • what device and it's OS
    • if it's pulled from the app/play store or native built
    • what changes have been made before this issue

    I haven't come across this issue before either.  I'm going to assume that this is on Android and it's a native build as you can't debug a play store version.  Have you been able to login at any time before making the last change?  Have you coded any JS correctly?  Have you cleared the apps cache and storage on the device?

    Regards, Craig

    ------------------------------
    Craig Kokay
    ISW
    ------------------------------



  • 5.  RE: Unable to login to Maximo Anywhere

    Posted 11 days ago
    Thanks Craig for your inputs.We are on version 7.6.3.1 and the app was working fine after applying the Interim fix 002 for a few days before it crashed down.We have no clue of the issue from the USB debug level logs and hence had posted it on the forum.

    Also we have to deploy the same apk onto the production environment as the customer has not agreed for enabling the internet access on the production environment due to which we are unable to build the apk file in the production envirornment after aplying the Ifix.With such an unstable behavior of the app from the pre-production environment,we are worried in applying the same onto the production environment.

    We cleared the cache,uninnstalled and re-installed but no luck all these days and after doing a build mobile first and redeploying the anywhere war file,it started working few days back and hence it is all the more strange behavior.

    ------------------------------
    Mahadevan Ramakrishnan
    Tata Consultancy Services
    ------------------------------



  • 6.  RE: Unable to login to Maximo Anywhere

    Posted 15 days ago
    Dear Mahadevan,

    Please ensure that your WAR file is successfully in deployed Folder. 
    Check the Worklight Administrator Console
    Check the Updates of Mobile Platform Environment 
    Check the User administration Groups at WAS Server
    Run the Rest API to POST/GET Method 

    Thanks 
    Adnan Sheeraz


    ------------------------------
    Adnan Sheeraz
    Ora-Tech
    ------------------------------



  • 7.  RE: Unable to login to Maximo Anywhere

    Posted 11 days ago
    Dear Adnan,

    We deployed the anywhere war file after running the build mobile first and also did the build all.
    Can you pls let me know what exactly we have to check in the worklight console as it is reflecting the timestamp of the build correctly.Also,please let us know how we can fire the rest api command to do the POST/GET method.

    regards,
    Mahadevan

    ------------------------------
    Mahadevan Ramakrishnan
    Tata Consultancy Services
    ------------------------------



  • 8.  RE: Unable to login to Maximo Anywhere

    Posted 10 days ago


    Dear,

    Please check the OSLC Response in order to get if in JSON record is retrieving or not.

    http://Your's IP:9080/maximo/oslc/os/mxasset?_lid=Username&_lpwd=****&lean=1&oslc.pageSize=10
    BR
    Adnan Sheeraz



    ------------------------------
    Adnan Sheeraz
    Ora-Tech
    ------------------------------