Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Expand all | Collapse all

Asset/Location drilldown fails to open

  • 1.  Asset/Location drilldown fails to open

    Posted Tue December 19, 2023 12:19 PM

    I'm trying to find a starting point to troubleshoot this problem. The asset/location drilldown will no longer open. There's no error message, simply a brief "busy" cursor and then nothing. This happens from the More Actions menu or from a detail menu, and I've found no relevant messages in SystemOut or SystemErr. I also checked the javascript console, but nothing at all appears there.

    I restarted the Maximo server, the browser, cleared browser data, used both Chrome and Edge. Does anyone have any other ideas? Thanks.



    ------------------------------
    Robert Goff
    ------------------------------


  • 2.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 01:13 AM

    Just start thinking - what was done just before that.

    Another idea - check descriptions for some specific characters.



    ------------------------------
    Juris Flugins
    ------------------------------



  • 3.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 03:51 AM

    Hi!

    First of all i propose to check SystemOut.log or messages.log for MAS installation. Probably will be something. 

    Another question is do you open drillDown on the list tab or on an object tab?

    If on the list maybe you have too many objects to be in the structure (lochierarchy for exampple). Try to open it on single object tab.

    Or last idea is that you have somewhere in the hierarchy loop, that makes loading crashes. 

    Anywhay, i think i jvm logs should be something.... 



    ------------------------------
    Andrey Ilinskiy
    ------------------------------



  • 4.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 09:38 AM

    Additional troubleshooting thoughts/questions:

    • What version are you on?
    • Which database is this running on?
    • How many Location records? Asset records? Location Systems? Are those Location Systems "network" type?
    • Is this happening for all users, or just you? (If just you, I'd check your profile and check the box to use the Default Insert Site as a display filter.)
    • Try yet another browser, one that's not Chromium-based.
    • Are you experiencing this error in all applications, or just, say, Work Order Tracking? I.e., can you open the drilldown on the Location field in the Asset application, or the PM application?
    • When you try to open it, are you opening it with the field blank?  If so, what happens if you have a value in the field and then try to drilldown?  For example, assuming you have a fairly-common location hierarchy consisting of building --> floor --> room, put a valid floor value in the Location field and then try to drilldown (instead of starting at the top of the hierarchy).  Or another way to test this -- go to Assets, choose an Asset that has a Location value, and try to open the drilldown on the Location field.
    • Do you have the ability to directly query the database? If so, maybe we here in the community could come up with some simple error-checking queries.  IMO the most likely source of the problem is bad data, as the others have said -- invalid characters, something is wrong in the LOCANCESTOR or LOCHIERARCHY tables, etc.
    • Could someone have done a back-end database UPDATE, INSERT, or DELETE?
    • Check your LIBRARY.XML for invalid syntax.
    • We might have to also check the MAXRELATIONSHIP table to see if any of the relationships to the DRILLDOWN object have been changed or deleted.

    And of course, as Juris said, if it used to work but now it doesn't, ask "what changed?"



    ------------------------------
    Travis Herron
    ------------------------------



  • 5.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 10:48 AM
    These are the same numbers the drilldown worked with the day before.
    Again, the same systems as the day before.
    • The problem occurs with the field blank or filled, from any field or application, and from the action menu item. 
    • Using the browser network monitor, I see doku.js making a query to maximo.jsp with no response.
    • Yes, I can query the database. I've checked the location hierarchy integrity as best I know how, but troubleshooting scripts would be welcome.
    • Only I have write access to the database, and I don't use it; I use MxLoader, and hadn't uploaded anything at the point where the problem started.
    • VSCode highlights no problems in LIBRARY.XML.
    • How can I tell if the drilldown relationships have a problem? 
    I think my next step will be to restore a working backup into a temporary database and start comparing for changes.


    ------------------------------
    Robert Goff
    ------------------------------



  • 6.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 11:27 AM

    I'd still try another not-Chromium-based browser, just to rule out another possibility.  It'd be a lot less work for you if it turns out the problem is Chromium!

    Was this affecting other users as well, or just you?

    If possible, compare your current LIBRARY.XML to an ootb version.  Maybe there is an error there that the IDE can't detect, like a misspelled attribute name or invalid value for an attribute. (I'm really picking on LIBRARY.XML because you said it was edited recently, for the issue you were having with the Desktop Requisitions Inspection Required field.)

    As far as the Drilldown relationships. . .I'm on 7608 with no add-ons and got 82 records from the MAXRELATIONSHIP table where child = 'DRILLDOWN'.  I'm sure there's probably some logic to it, but 65 of the results had whereclause = NULL, cardinality = UNDEFINED, dbjoinrequired = 0; and then 16 had whereclause =  <an empty string>, cardinality = NULL, dbjoinrequired = NULL; and 1 record had whereclause =  <an empty string>, cardinality = UNDEFINED, dbjoinrequired = 0.    

    Anyways, the main point there is that none of the entries should have a whereclause value.

    Another simple something I'd recommend: query the ASSET and LOCATIONS tables based on the changedate being in the last few days or close to when the problem began.  Focus on those records as possibly having some data issues.  Try navigating through those Locations' hierarchies by opening the record and using the Parents and Children tables and moving to those records that way instead of the drilldown.



    ------------------------------
    Travis Herron
    ------------------------------



  • 7.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 11:56 AM

    And do u have anything in SystemOut and SystemErr? 

    Also try to enable info for sql logger to check what last SQL query for it ?



    ------------------------------
    Andrey Ilinskiy
    ------------------------------



  • 8.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 03:49 PM

    I inserted several locations via MxLoader and another user inserted assets for them, but I can't see anything wrong with any of it. I had recently inserted a HOLDING location, but deleting it didn't help.

    There were some locations in a network system with two parents, but deleting one didn't help.

    I compared maxpropvalues with a week-old backup and found no differences.

    I'm looking now for a OOB version of LIBRARY.XML to compare.



    ------------------------------
    Robert Goff
    ------------------------------



  • 9.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 05:31 PM

    Out of desperation, I disabled the extended drilldown in system properties, and the old drilldown appeared fine. Still looking for a clean LIBRARY.xml.

    (I've only found one drilldown dialog in LIBRARY.xml -- are they both in that one definition, with the difference handled by the bean?)



    ------------------------------
    Robert Goff
    ------------------------------



  • 10.  RE: Asset/Location drilldown fails to open

    Posted Wed December 20, 2023 05:43 PM

    Sorry, I can't help you there -- we never made it to a version of Maximo with the new/extended Drilldown.  But it sounds like you made some progress -- at least you know the old-school drilldown works.  So that likely means it's not a data issue.  That's good!

    I'd still challenge you to test another browser besides Chrome and Edge if you haven't done so already.  Also, if your instance is publicly accessible, can you reach it from somewhere other than the corporate LAN, such as your home network or your smartphone?  It's starting to feel like it isn't Maximo that changed; so maybe it's the browser, or a Group Policy, or a Firewall setting, etc.



    ------------------------------
    Travis Herron
    ------------------------------



  • 11.  RE: Asset/Location drilldown fails to open

    Posted Thu December 21, 2023 04:05 AM

    They work absolutely differently - different beans, different logic. External DrillDown is based on lochierachy as top-level object. 

    And yes, OTB it is only in library.xml. 

    And do u have anything in SystemOut?



    ------------------------------
    Andrey Ilinskiy
    Handz.on
    https://www.on.de/
    München
    ------------------------------



  • 12.  RE: Asset/Location drilldown fails to open

    Posted Tue January 02, 2024 11:44 AM

    Nothing in SystemOut, and the vanilla LIBRARY.XML was a bust -- the one I had was fine.

    I've done all I can think of to check the health of the location hierarchy; does anyone have any scripts or tips for that?



    ------------------------------
    Robert Goff
    ------------------------------



  • 13.  RE: Asset/Location drilldown fails to open

    Posted Tue January 02, 2024 12:34 PM

    Since the old-school drilldown works correctly, I don't think that your hierarchies have health issues.  Since the logs aren't logging anything, it's probably not a Maximo issue either.  I still say you should try a different, non-Chromium browser; and you should try to access Maximo from outside your corporate network (e.g. via smartphone).  Also. . .a tried-and-true troubleshooting step: clear your browser cache.



    ------------------------------
    Travis Herron
    ------------------------------



  • 14.  RE: Asset/Location drilldown fails to open

    Posted Tue January 02, 2024 01:06 PM

    Deleting the browser cache was the first thing I did; also, all users are seeing this behavior. Second thing was to revert LIBRARY.XML. Brand-new installation of Firefox has the same behavior.

    I also looked at the HTTP request/response and don't see anything glaringly wrong. Does anyone know what it should look like?



    ------------------------------
    Robert Goff
    ------------------------------



  • 15.  RE: Asset/Location drilldown fails to open

    Posted Wed January 03, 2024 09:53 AM

    Hi Robert,

    Since you said it worked the day before with no difference in system change, I am thinking more into data health.

    • Since you use MXLOADER, I suggest to really looking into the last data you have changed right before the problem arises. Or at least the day before the problem arise
    • I agree with Travis, check also the hierarchical integrity. And are the parent a Network type, or Primary type?

    I suggest to track down from Data Health path first. 

    Easiest is to trail back your last data change that you've done via MXLOADER.  It may seem to be irrelevant but it really depends to rules within your Maximo. i.e. how WO location tied up with Asset's location, is there any automation script that rule any applications that use Locations. And so on.

    Hope this helps in one way or another.



    ------------------------------
    Agustina Rajino
    ------------------------------



  • 16.  RE: Asset/Location drilldown fails to open

    Posted Sun January 07, 2024 03:47 AM

    Hi Robert,

    This does sound like a data issue.  The extended drilldown uses the locancestor (I'm sure) whereas the old one uses the lochierarchy.  However, there are cases even with the old one depending on where you start it, it will use locancestor or lochierarchy.

    Loading via the MXLoader is normally perfect, but that doesn't mean that something hasn't gone wrong.

    You should validate the following:

    1. For each location it exists in the locoper, lochierarcy, and locancestor tables
    2. For each location it has has an ancestor of itself.  i.e. location=ancestor in the locancestor table
    3. Check that for each parent in the lochieracy table exists in the location table
    4. Check that for each ancestor in the locancestor table exists in the location table
    5. Check that the haschildren has been set for each location that has children.
    6. Have you run the integrity checker?

    I haven't heard which loggers you have enabled.  Have you enabled the SQL for the LOCATION, same with APPLICATION and even the SERVICE.

    Now about the behaviour.  Do you get any difference from:

    • Locations list tab - action Open Drilldown
    • Locations list main tab - from a location with a parent, what happens from the parent drilldown
    • Asset list tab - location field open drilldown
    • Same from location field on an asset
    • Repeat from the work order

    Could there be a chance that there is bad data associated with an asset?

    • Ensure that for each asset the location exists in the location table
    • Check the asset ancestoir as well

    Let us know if that has found an issue.



    ------------------------------
    Regards,
    Craig Kokay
    Principle Consultant
    Cosol
    https://cosol.global/

    Ph: +61-411-682-040
    email: craig.kokay@cosol.global
    ------------------------------



  • 17.  RE: Asset/Location drilldown fails to open

    Posted Mon January 08, 2024 06:00 PM

    Thanks a ton for your detailed response, Craig.

    • locoper -- all locations exist except storerooms and one salvage location.
    • lochierarchy, locancestor -- 1,700+ decommissioned locations were removed from the hierarchy.
    • locancestor -- 4 locations that didn't have self-ancestors. Fixed by reassigning their parents, but it didn't help the drilldown.
    • lochierarchy parents -- there were two not at the top of the hierarchy that didn't have parents; fixed by reassigning, but didn't help the drilldown.
    • locancestor ancestor -- all good.
    • lochierarchy children -- 15 records in a network system that should have been children=1. Fixed, but no help.
    • asset location -- all good
    • behavior -- whatever entry point I try, detail menu, asset action, location action, etc. it fails to open.
    • Integrity Checker -- Didn't know about it, will run tonight.



    ------------------------------
    Robert Goff
    ------------------------------



  • 18.  RE: Asset/Location drilldown fails to open

    Posted Mon January 15, 2024 03:07 PM

    The problem was resolved by installing the 7.6.1.3 update with the latest IFIX. Unfortunately, that means I don't know what caused it. I do have a log of the ingegrity checker from before the update and I intend to compare it to a current run, but I don't hold out much hope -- there were no errors in the log that seemed relevant. 

    I'm very grateful to everyone who responded, and I'm sorry I can't offer more information.



    ------------------------------
    Robert Goff
    ------------------------------