Maximo Open Forum

Hi all,

Seeking your assistance to provide ideas or solutions on how to resolve this issue. Whenever I generate a work order from Preventive Maintenance or try to close a work order, I keep receiving the error message: "Has been updated by another user." Our Maximo version is 7.6.1.3

Appreciate your help on this.

I have seen the updated by another user error in various PM related bugs but can't think of a scenario off the top of my head when it occurs on the LOCATIONS object.

Is this a PM record tied to the location (rather than an asset or route)? And is it schedule based or meter based? And is it all PMs for all locations or just this one specific location/PM?

What I like to do to triage this scenario when you can reliably recreate it is to turn on sql logging to INFO for just the locations object. IE create a new child logger of LOCATION.LOCATIONS with its log level set to INFO.



Save and apply settings. Then recreate the issue and disable the logging.

What this does is help you understand how locations are being fetched along with what is being modified on the locations object. This can help you identify where the problem might be. It is possible, for example, that a custom automation script is updating the locations record on work order save and is using a different relationship to get the record. 

I would recommend since you're on 7.6.1.3 (newer MAS versions have a system property to disable automation scripts) to turn on admin mode in a lower environment and try to recreate the issue. That can potentially eliminate or help confirm an automation script as the issue. It's not perfect because it does disable other things (such as publish channels) which could potentially lead to the issue. But is still helpful in trying to pinpoint. 

Hi Steven,

Appreciate your suggestion on this. After applying it, we observed that the system log still does not show the actual user who updated the location/asset/PM, instead, it continues to display my name.

For context, this PM is linked to either location or asset, and it is schedule-based. The issue occurs across multiple locations and assets, not just a single case. At this point, we are still facing the same problem.

Have you encountered a similar issue before? If so, could you please advise on the possible cause or recommend how we should proceed?

I can think of a couple of items to check and try.
1. Do you have or use Automation scripts as this may be triggering and cause the error you are seeing. If you can recreate this issue in a non-production environment then I would put the system in Admin Mode which will prevent Autoscript from launching. Then try you scenario again and if the error does not occur you then need to look at your Autoscripts. You could also turn on logging for Automation scripts and see what scripts are triggering when you are performing the action that is generating the error. 
2. Sometimes this can be triggered by an escalation that is set to run frequently. If you are putting the system in Admin Mode escalations will also not run so this could be another area. Based on your description you will want to look at escalations that are on the WORKORDER object.
3. You could tune on SQL logging to INFO, but beware this does write a lot of information to the logs and may slow down your Maximo system.  You should see either updates or inserts. Note if you have not looked at these types of logs before it does spit out a lot of information and will take time to sift through if you have not done this before. 

Mike

Are the PMs getting the errors tied to "Dynamic" Job Plans?  What IFix level are you at in 7.6.1.3? 

We had a similar problem and reported it to IBM but they were not able to reproduce the issue even though we did so in our MaxDemo environment.  IBM Support believes that the issue was fixed in IFix 031.  (IFix 036 was released at the end of September 2025 and was the last IFix for 7.6.1.3.)

We were on IFix 018 and are currently in the process of applying IFix 036 but have not had a chance to test this.

In our case, we found that the error was due to a bug in the WO Completion process that was unchecking the "Use Job Plan Sequences?" checkbox when the Job Plan on the WO is a "Dynamic Job Plan".  If that sounds like it could be your problem, I can provide more details and describe teh Escalation we put in place as a workaround.