This section describes the messages starting with mpnjsosv.
The messages starting with mpnjsosv are generated by the Task Link service.
[Description]
The Server Task Link engine (Systemwalker MpNjsosv service) has started the initial processing.
[Description]
The Server Task Link engine (Systemwalker MpNjsosv service) has started the process of scheduling.
[Description]
The Server Task Link engine (Systemwalker MpNjsosv service) has started the process of stopping.
[Description]
The Server Task Link engine (Systemwalker MpNjsosv service) has stopped the process of scheduling.
[Description]
The Server Task Link engine (Systemwalker MpNjsosv service) could not start the process of scheduling because a problem occurred in the initial processing.
[System Action]
Terminates the process.
[System Administrator Response]
Restart the system.
If the problem cannot be resolved, collect the data of the following functions by using Maintenance Information Collection tool, and contact your Fujitsu systems engineer.
Server Task Link
Client Task Link
Depending on the options you selected during installation, one of the above functions may not exist. In that case, collect only the data of function that you can select.
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
[Description]
Failed to bind the control path establishment reception socket of Server Task Link engine (Systemwalker MpNjsosv service) when performing initial processing of communication control section.
[Parameter]
YYY : System error code notified by the Server Task Link engine
[System Action]
Terminates the process.
[System Administrator Response]
Due to the reason such as that a port necessary for the Task Link service to start is already in use by other application, the Task Link could be unable to use the port number. Ensure that the port number required for the Task Link service to start is available for use. For more details about the port number used by the Task Link, see the Systemwalker Operation Manager Installation Guide.
[Description]
Failed to bind the Task Link connection socket of Server Task Link engine (Systemwalker MpNjsosv service) when performing initial processing of communication control section.
[Parameter]
YYY: System error code notified by the Server Task Link engine
[System Action]
Terminates the process.
[System Administrator Response]
Due to the reason such as that a port necessary for the Task Link service to start is already in use by other application, the Task Link could be unable to use the port number. Ensure that the port number required for the Task Link service to start is available for use. For more details about the port number used by the Task Link, see the Systemwalker Operation Manager Installation Guide.
[Description]
Failed to receive the data in Server Task Link engine (Systemwalker MpNjsosv service).
[Parameter]
YYY: System error code notified by the Server Task Link engine (Systemwalker MpNjsosv service).
[System Action]
The Server Task Link engine (Systemwalker MpNjsosv service) ignores the received data and requested process.
[System Administrator Response]
This message is output when the send/receive data is corrupted due to network problem. Check if there is a network problem.
If you still receive this message, collect the data of the following functions by using Maintenance Information Collection tool, and contact your Fujitsu systems engineer.
Server Task Link
Client Task Link
Depending on the options you selected during installation, one of the above functions may not exist. In that case, collect only the data of function that you can select.
[Description]
Failed to receive the data in Server Task Link engine (Systemwalker MpNjsosv service).
[Parameter]
YYY: System error code notified by the Server Task Link engine (Systemwalker MpNjsosv service).
[System Action]
The Server Task Link engine (Systemwalker MpNjsosv service) ignores the received data and requested process.
[System Administrator Response]
This message is output when the receive data is corrupted due to network problem. Check if there is a network problem.
If you still receive this message, collect the data of the following functions by using Maintenance Information Collection tool, and contact your Fujitsu systems engineer.
Server Task Link
Client Task Link
Depending on the options you selected during installation, one of the above functions may not exist. In that case, collect only the data of function that you can select.
