Troubleshooting
Problem
The Mic Service does not start when starting the Maximo Application Server. Maximo runs fine, but the MEA does not run and results in various errors in the UI and interface transactions.
Cause
The mea user is not setup properly. This did not cause a problem in 6.2.1, but causes the MEA to fail in 6.2.2 and higher.
Diagnosing The Problem
You will see the following stack trace in the Maximo log:
09 Jan 2009 10:52:52:446 [ERROR] Error Initializing MicService:null
java.lang.NullPointerException
at psdi.security.SecurityService.authenticateUser(SecurityService.java:858)
at psdi.iface.mic.MicService.getNewUserInfo(MicService.java:581)
at psdi.iface.mic.MicService.init(MicService.java:196)
at psdi.server.ServiceCoordinator.init(ServiceCoordinator.java:173)
at psdi.server.MXServer.init(MXServer.java:1599)
at psdi.server.MXServer.start(MXServer.java:2182)
at psdi.servlet.MAXIMOStartupServlet.init(MAXIMOStartupServlet.java:59)
at ...
09 Jan 2009 10:52:52:533 [ERROR] server#CriteriaError
Resolving The Problem
This error indicates that the MIC service (MEA) is not starting. You will see the stack trace in the startup log, after shutting down and restarting Maximo.
It may not start because the MEA user is not an active user.
In External Systems -> Integration Administration Setup -> "Maximo user name for inbound processing" - check that this user (default is mxintadm) is a valid user.
In Security -> Users - query mxintadm and make sure it is associated with a Person whose status is ACTIVE.
Also verify that the profile for mxintadm shows a default insert site. Many MEA transactions require that the Default Insert Site be populated. It can be set to any active site.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21363970