IBM Support

Class Not Found Exception: com.ibm.tivoli.mobile.oslc.MoutMobile

Troubleshooting


Problem

If you see these "class not found" exceptions on your Maximo logs, and you don't use or have Maximo Anywhere installed, you can use this document to resolve the problem.
Those classes are Maximo Anywhere exclusive and won't be used by Mobile or Maximo, these errors will only appear in the logs, they won't cause any issue on your system.

Symptom

All these errors in the logs:

24 Jul 2023 23:02:45:920 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileInvreserve

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileInvreserve

24 Jul 2023 23:02:46:023 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileMatrectrans

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileMatrectrans

24 Jul 2023 23:02:46:045 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileAssettrans

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileAssettrans

24 Jul 2023 23:02:46:298 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileSetLaborName

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileSetLaborName

24 Jul 2023 23:02:46:303 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileMatusetrans

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileMatusetrans

24 Jul 2023 23:02:46:312 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutMobileInventory

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutMobileInventory

24 Jul 2023 23:02:46:330 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.MoutGetLangCodeInfo

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.MoutGetLangCodeInfo

24 Jul 2023 23:02:46:372 [ERROR] [integration] com.ibm.tivoli.mobile.oslc.OslcOsUserNotification

java.lang.ClassNotFoundException: com.ibm.tivoli.mobile.oslc.OslcOsUserNotification

Cause

Old Anywhere classes still being reference and trying to be executed.

Environment

Maximo and Manage.

Diagnosing The Problem

Check Maximo SystemErr and SystemOut.

Resolving The Problem

1 - Open the Object Structures application

2 - Search for this Object:

OSLCWODETAIL

3 - Open the Object and clear the Outbound and Inbound classes from the Object.

4 - Save it

5 - Repeat the same process for these other Object Structures as well:

OSLCLABTRANS

OSLCMATUSETRANS

OSLCINVENTORY

OSLCLABORCRAFTRATE

OSLCMAXUSER

OSLCINVRESERVE

OSLCMATRECTRANS

OSLCASSETTRANS

OSLCOSUSERNOTIFICATI

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Product Synonym

maximo; anywhere

Document Information

Modified date:
30 January 2024

UID

ibm17112497