Maximo Open Forum

 View Only

 BMXAA4106E A major exception occured

  • Everything Maximo
  • Maximo Application Suite
Trisha S's profile image
Trisha S posted 03-17-2026 13:40

BMXAA4106E A major exception has occured check system logs to see it.

The workorder is in schd state and there is one of the task workorder that is also in schd state , user is trying to change the actual start date in both but he is getting this error. I tried replicating but couldn't replicate the issue as i am not getting this error, how do i troubleshoot? 

Which logs should i enable?

Steven Shull's profile image
Steven Shull

Major exceptions are typically things like null pointer exceptions that are not handled. Unfortunately, you really need the logs to begin to investigate what happened. It could be something with how the data restrictions are built out (site access, data restrictions on their security groups, conditions on the statuses, etc.), missing data on their record (such as not having a default insert site and something depending on that), different flows in automation scripts, etc. If it's data restriction related and the restriction is invalid in some capacity (references a column that doesn't exist for example), you likely would see the query in the logs. But if not, you should hopefully get a stacktrace of the error to help narrow down where the problematic code area of code is. 

Trisha S's profile image
Trisha S

Hi @Steven,

Thank you for responding. I checked the logs and found that something like, FormulaMBoEventlistner event maximo.workorder.add has been fired for object Workorder launch point x_calculate .

i found there is no autoscript as such  but there is an attribute formula for workorder object sum$woactivity$x_calculate

I am not able to figure out what might be causing this issue, because the same set up is in lower environment and i am mot getting error there

Steven Shull's profile image
Steven Shull

Do you have any conditions on the formula? It'd be displayed underneath the formula in the Conditional Formula section.

I've tested creating a new attribute called x_calculate on the WORKORDER object (which would add it to the underlying views like WOACTIVITY) and adding your exact formula to this attribute. Even when I mix and match null and non-null values on the child object, and whether I pick a work order with or without tasks, I can't trigger the null pointer exception. It's possible you're on a version with a defect or it's possible you have some additional configuration that is required to trigger the null pointer exception. I've seen this in formulas a lot, especially with formulas that manipulate dates where people don't validate that the attribute is not null before trying to perform a function against it.