KNAN29082-E
The IM Configuration Management service cannot start because it cannot confirm whether the IM database service has started. Cause: cause
IM Configuration Management Service could not be started because completion of IM database service startup could not be confirmed.
- S:
-
Stops IM Configuration Management Service.
- O:
-
Take corrective action based on the reason:
-
Reason: The IM database service is now performing start or stop processing.
-
Reason: The IM database service is stopping.
Execute the jimdbstatus command to determine whether the IM database service is running, and then perform the following operation.
- In Windows:
-
Start the IM database service, and then restart JP1/IM - Manager.
- In UNIX:
-
Stop JP1/IM - Manager, and then re-execute the jco_start command.
-
Reason: The IM database service was interrupted during a restart.
Execute the jimdbstop -f command to forcibly stop the IM database service, and the perform the following operation.
- In Windows:
-
Start the IM database service, and then restart JP1/IM - Manager.
- In UNIX:
-
Execute the jco_start command.
-
Reason: The IM database service is not set up.
Set up the IM database service, and then start JP1/IM - Manager.
-
Reason: Status confirmation error
-
Reason: System error
Collect JP1/IM data, and then contact a system administrator.
-