This is a list of messages displayed by the event monitoring and action control function. Source name is MpAosfB.
[Description]
The Event Monitor service has been started.
[System Action]
Starts monitoring events.
[Description]
The Event Monitor service has been stopped.
[System Action]
Stops monitoring events.
[Description]
Failed to activate the Event Monitor service since the user do not have administrator privileges.
[System Action]
Aborts the process.
[System Administrator Response]
Check that administrator privileges have been granted to the service logon account. If not, change the account to the one with logon account privileges.
[Description]
A past event has been retrieved from an event log.
[Parameter]
ppp : Date and time of message occurrence
eee : Event log type
vvv : Record number of event log
[System Action]
Continues the process.
[System Administrator Response]
The system might have been shut down before Systemwalker Operation Manager terminated. Terminate Systemwalker Operation Manager first then shut down the system.
[Description]
The old messages are sequentially discarded, as the messages that can be managed by automization exceeded the maximum number.
[Parameter]
nnnn : Maximum number of messages
[System Action]
Continues the process. When a new message is generated, old message is discarded.
[System Administrator Response]
Restart Systemwalker.
[Description]
An invalid regular expression is specified on the nnnnth line of the event monitoring definitions. The process will be continued, ignoring this line.
[Parameter]
nnnn : Line number
[System Action]
Ignore the line with the invalid regular expression and continues the process.
[System Administrator Response]
Open the Monitored Event Table window and correct the regular expression in the event definitions on the line indicated. See "Registering Monitoring Events" described in the Systemwalker Operation Manager User's Guide for regular expression notation.
[Description]
Failed to connect the socket.
[Parameter]
ssss: Cause code of error
[System Action]
Stops the Event Monitor service.
[System Administrator Response]
Remove the error by referring to the contents described in Cause. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The calendar name specified in action execution condition is not defined.
[Parameter]
cccc : Calendar name
[System Action]
Action execution condition is assumed for Everyday.
[System Administrator Response]
Check that the calendar has been registered to the Calendar of Systemwalker Operation Manager. If not registered, change the name of the calendar defined in action conditions to the one registered on the Monitored Event Table window.
[Description]
Error occurred in calendar service.
[Parameter]
cccc: Calendar name
eeee: Error code
[System Action]
Ignores the definition item of the concerned event action. Continues the process.
[System Administrator Response]
Investigate the cause of error in calendar service and take the corrective measures for that cause.
[Description]
Calendar service is not started.
[System Action]
Action execution condition operates for Everyday.
[System Administrator Response]
Start calendar service.
[Description]
The Action Management Server is not started or is busy.
[Parameter]
aaaa : Action that was to be executed
[System Action]
The concerned action is not executed.
[System Administrator Response]
Check whether Systemwalker is started correctly. Review the event monitoring conditions and change them so that too many actions will not be executed simultaneously.
[Description]
The environment (sound reproduction environment, modem etc.) that executes action is not set.
[Parameter]
aaaa : Action that failed
[System Action]
The concerned action is not executed.
[System Administrator Response]
An environment for executing audio notification or short mail notification has not been set up. Set up an environment using the Action Environment Setup dialog box.
[Description]
Error occurred in communicating with Action Management Server.
[Parameter]
aaaa : Action that failed.
[System Action]
The concerned action is not executed.
[System Administrator Response]
Check whether Systemwalker is started correctly. Ignore this message if it is output at system shutdown.
[Description]
Error occurred in Action Management Server.
[Parameter]
cccc : Detail code
[System Action]
The concerned action is not executed.
[System Administrator Response]
Take the corrective measures for the messages of 3000 machine numbers output immediately before and immediately after this error message.
[Description]
There is an error in definition of Monitored Event Table.
[Parameter]
ffff : File name
[System Action]
Disables the entire definition information.
[System Administrator Response]
If there is no backup data, reinstall Systemwalker or collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The number of action requests in queue reached the maximum (100) allowed by the Event Monitor function, because of the slow process on Action Management Server. Obsolete action requests will be deleted from the queue.
[System Action]
Continues the process. An obsolete request will be deleted from the queue, when it receives a new request.
[System Administrator Response]
Check the event monitoring conditions so that it will not invoke too many actions at once.
[Description]
The number of action requests in queue reached the maximum (100) allowed by the Event Monitor function, because events occur before the action is completed. Obsolete action requests will be deleted from the queue.
[Parameter]
rrrr: Action deleted from the queue
[System Action]
Continues the process. An obsolete request will be deleted from the queue, when it receives a new request.
[System Administrator Response]
Check the event monitoring conditions so that it will not invoke too many actions at once.
[Description]
The actions impossible to invoke have been deleted, because events occur before the action is completed. As a result, more than cccc actions (rrrr) have been deleted from the queue.
[Parameter]
cccc: Number of actions deleted from the queue
rrrr: Action deleted from the queue
[System Action]
Continues the process. An obsolete request will be deleted from the queue, when it receives a new request.
[System Administrator Response]
Check the event monitoring conditions so that it will not invoke too many actions at once.
[Description]
The definition of the action is invalid. The action will not be carried out.
[Parameter]
rrrr: Action
[System Action]
Continues the process, aborting the actions with invalid definition.
[[System Administrator Response]]
Check the settings of the action in the event monitoring conditions file.
[Description]
Cannot invoke the action, 'rrrr', because the library required to communicate with Action Management Server is missing. The action will not be carried out.
[Parameter]
rrrr: Action
[System Action]
Continues the process, aborting the action in which the error occurred.
[System Administrator Response]
Check if Systemwalker is installed properly. Also check if the Systemwalker installation directory is set to the environment variable 'Path'.
[Description]
The user name, the computer name or the address specified for the action, 'rrrr', has not been defined.
[Parameter]
rrrr: Action
[System Action]
Continues the process, aborting the action in which the error occurred.
[System Administrator Response]
Define the user name, the computer name or the address specified for the action in the event monitoring conditions file.
[Description]
The executable file, 'cccc', specified for the action for starting the application is missing.
[Parameter]
cccc: Name of the executable file
[System Action]
Continues the process without launching the application.
[System Administrator Response]
Check if the executable file exists. If it does not exist, install the application or specify an existing file in the event monitoring conditions file.
[Description]
The startup directory, 'dddd', specified for the action for starting the application is missing.
[Parameter]
dddd: Directory name
[System Action]
Continues the process without launching the application.
[System Administrator Response]
Check if the startup directory exists. If it does not exist, create a directory or specify an existing directory in the event monitoring conditions file.
[Description]
Failed to start the application.
[Parameter]
cccc: Name of the application that failed to start
[System Action]
Continues the process without launching the application.
[System Administrator Response]
Refer to the message logged prior to this message and resolve the problem.
[Description]
Failed to open the socket to send the SNMP trap.
[Parameter]
cccc: Detail code
[System Action]
Continues the process without sending the SNMP trap.
[System Administrator Response]
Check if the environment is defined for issuing an SNMP trap. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to obtain the own host name for the SNMP trap.
[System Action]
Continues the process without sending the SNMP trap.
[System Administrator Response]
Register the local host name and the IP address to the hosts file of the system.
[Description]
Failed to obtain the target host name, 'hhhh', to send the SNMP trap.
[Parameter]
hhhh: Name of the host that receives the SNMP the trap
cccc: Detail code
[System Action]
Continues the process without sending the SNMP trap.
[System Administrator Response]
Check that the name of the SNMP trap transmission target machine and its IP address specified in the event monitoring conditions file are correct. If correct, define the target host name and IP address to the hosts file of the system.
[Description]
Failed to send the SNMP trap.
[Parameter]
cccc: Detail code
[System Action]
Continues the process without sending the SNMP trap.
[System Administrator Response]
Check if the environment is defined for issuing a SNMP trap. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Access to the specified computer has been denied for the action that require logging in the event log.
[Parameter]
hhhh: Name of the computer that denied the access
[System Action]
Continues the process without logging in the event log.
[System Administrator Response]
For the account specified for the Event Monitor service, set the access rights to the computer on which the event log is stored.
[Description]
The specified computer is unavailable to output to event log.
[Parameter]
hhhh: Name of the unavailable computer
[System Action]
Continues the process without logging in the event log.
[System Administrator Response]
Check if the specified computer is available to use.
[Description]
Failed to open the event log file.
[Parameter]
kkkk: Type of the event log
Application: Application log
System: System log
Security: Security log
[System Action]
Terminates the process.
[System Administrator Response]
Refer to the message logged prior to this message, find the cause and resolve the problem.
[Description]
The Event Monitor function will not monitor event log messages output while the service is stopped.
[System Action]
Continues the process.
[System Administrator Response]
Use Event Viewer and check the messages output while the Event Monitor service is stopped. Handle errors, if necessary.
[Description]
Failed to write to the file that stores information on the read point of the event log file.
[System Action]
Continues the process.
[System Administrator Response]
If this error persists, stop the Event Monitor service, delete all files in the Systemwalker installation directory\mpaosfsv\base\temp whose name begins with "evtstart", and restart the service. Also check disk errors and the access rights to the file and the directory. Set updatable access rights for the files and directories.
[Description]
The format of the event log file is invalid. It will read the file again.
[Parameter]
kkkk: Type of the event log
Application: Application log
System: System log
Security: Security log
nnnn: Record number
[System Action]
Continues the process.
[System Administrator Response]
If this error persists, check the event log status (such as available disk space).
[Description]
Failed to read the event log file.
[Parameter]
kkkk: Type of the event log
Application: Application log
System: System log
Security: Security log
[System Action]
Terminates the process.
[System Administrator Response]
Refer to the message logged prior to this message, find the cause and resolve the problem.
[Description]
The setting of the log file to monitor is invalid.
[Parameter]
dddd: File name
[System Action]
Invalidate all definitions and terminates the process.
[System Administrator Response]
Open the Monitored Application Logfile Setup dialog box and check that the definition is correct (an existing file has been specified, a label has been set, etc.).
[Description]
Failed to open the Monitored File Information file.
[Parameter]
ffff: Name of the Monitored File Information file
[System Action]
Terminates the process.
[System Administrator Response]
Refer to the message logged prior to this message, find the cause and resolve the problem.
[Description]
An error occurred in the system function 'ffff' while monitoring the file 'dddd', due to the cause indicated by 'rrrr'.
[Parameter]
dddd: Name of the monitored file
ffff: System function
rrrr: Message indicating the cause of the error
[System Action]
Continues monitoring the file.
[System Administrator Response]
Refer to the message and resolve the problem accordingly. Check the status (missing or not, access rights, etc.) of the monitored file. If this problem persists, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The specified log file does not exist to monitor. This message is displayed when the service is started and the definitions are modified in the Monitored Log File Settings window.
[Parameter]
dddd: Name of the monitored file
[System Action]
Continues the process. Monitoring will start when the specified log file is created.
[System Administrator Response]
Check that the target log file specified in the Monitored Application Logfile Setup dialog box exists and specify the full path name to the existing file.
[Description]
Cannot monitor the specified log file because it is stored on a CD-ROM drive, a removable disk or a network drive.
[Parameter]
dddd: Name of the monitored file
[System Action]
Continues the process without monitoring the specified log file.
[System Administrator Response]
Do not specify the file stored on a CD-ROM drive, a removable disk or a network drive.
[Description]
The message output to the event log was discarded since there were 200 or more parameters.
[Parameter]
ppp: Date and time of message occurrence
rrr: Source name of message
mmm: Event ID of message
[System Administrator Response]
Check the specification for the application which outputs event logs and take action so as not to output messages that have 200 or more parameters.
[Description]
Failed to initialize, as error occurred in Action Management Server.
[Parameter]
ffff : System function in which error occurred
ssss : Message indicating the reason of error
[System Action]
Ends action execution process.
[System Administrator Response]
Take the corrective measures for the reasons of error. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The Action Management Server is shutdown, as abnormality occurred.
[System Action]
Ends action execution process.
[System Administrator Response]
Investigate the cause of error from the message displayed just before and take the corrective measures according to its contents. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Environment definition file necessary for action execution does not exist.
[System Action]
Ends action abnormally and continues the process.
[System Administrator Response]
Register an action execution environment using the Action Environment Setup dialog box.
[Description]
Memory is insufficient, as send data is large or send destinations are many. So action cannot be executed.
[Parameter]
iiii : Management number of the action that could not be executed.
[System Action]
Ends action abnormally and continues the process.
[System Administrator Response]
Split the send data or divide the send destinations and re-execute the action. Otherwise, add more memory.
[Description]
Memory is insufficient, as send data is large or send destinations are many. So action request cannot be received.
[System Action]
Disables action request.
[System Administrator Response]
Split the send data or divide the send destinations and re-execute the action. Otherwise, add more memory.
[Description]
During action execution the system function ffff failed due to the reason given in ssss.
[Parameter]
ffff : System function name
ssss : Message indicating the reason of failure
[System Action]
Ends action abnormally and continues the process.
[System Administrator Response]
Take the corrective measures according to the reasons of error. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to initialize socket.
[Parameter]
ffff : Socket file name
ssss : Message indicating the reason of failure
[System Action]
Ends the process.
[System Administrator Response]
Check if Systemwalker is installed properly. Remove the error by referring to the contents described in Cause. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to initialize socket.
[Parameter]
pppp : Port number
ssss : Message indicating the reason of failure
[System Action]
Ends the process.
[System Administrator Response]
Remove the error by referring to the contents described in Cause. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to communicate with API.
[System Action]
Disables action execution request or operation request.
[System Administrator Response]
Take the necessary corrective measures according to the message displayed just before.
[Description]
Failed to open code conversion table.
[System Action]
Uses the specified character string as it is.
[System Administrator Response]
Check if Systemwalker is installed properly. Remove the error by referring to the contents described in Cause. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Action list cannot be sent to the Action Control window as memory is insufficient.
[System Action]
Continues the process.
[System Administrator Response]
Restarts Action Control window after ending some of the applications.
[Description]
Character code conversion is not possible as unsupported character code is included.
[System Action]
Continues the process.
[System Administrator Response]
Recheck the character code specified in action execution.
[Description]
Failed to connect with the Action Control window.
[System Action]
Continues the process.
[System Administrator Response]
Take the necessary corrective measures according to the message displayed just before.
[Description]
The communication with the Action Control window has been cut off, because the Action Control window has not been exited normally or the network is down.
[System Action]
Continues the process.
[System Administrator Response]
Check the network status and the status of the computer on which the Action Control window has been opened. To suppress this message, close the Action Control window and shutdown the computer.
[Description]
Valid send destination does not exist in the address specified in action execution API.
[System Action]
Disables the requested action.
[System Administrator Response]
Confirm that the send destination is correct and re-execute action execution API.
[Description]
Host that executes action aaaa is not specified.
[Parameter]
aaaa: Action in which execution host is specified
[System Action]
Continues the process. But action in which execution host is specified is not executed.
[System Administrator Response]
Specify an execution host in the Action Execution Host sheet of the Action Environment Setup dialog box and re-execute action.
[Description]
The host to invoke the action
The Action Execution service (Systemwalker MpAosfX) is not running.
The port required for action execution is not available.
[Parameter]
hhhh : Host name
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Start the host to invoke the action and the Action Execution service (Systemwalker MpAosfX). If there is an application that uses port No. 6961, eliminate overlapping by changing the port, etc.
[Description]
Action execution host specified in the Action Environment Setup dialog box does not exist.
[Parameter]
hhhh : Host name
[System Action]
Continues the process. But, the action that was to be executed by the specified host is not executed.
[System Administrator Response]
Check that communications with the host specified in the Action Execution Host sheet of the Action Environment Setup dialog box and TCP/IP are available by executing the ping command and specify a host with which communications are available. Then, execute the action abnormally terminated in the Action Control window.
[Description]
An error occurred while connecting to the host to invoke the action. The action will be terminated abnormally.
[Parameter]
hhhh : Host name that was to be connected
ssss: Message indicating the contents of error
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Check whether heavy loads are placed to the network or a network trouble occurs. Refer to the message, find the cause of the socket communication error and resolve the problem.
[Description]
An error occurred while communicating with the host to invoke the action. The action will be terminated abnormally. This message is logged when the host executing the action lost the power supply or a network error occurred.
[Parameter]
iiii : Action control number
hhhh : Execution host
ssss : Message indicating the contents of error
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Check whether heavy loads are placed to the network or a network trouble occurs. Refer to the message, find the cause of the socket communication error and resolve the problem.
[Description]
Action was about to be executed but specified action execution server is being executed according to action execution request of other server. So the action cannot be executed.
[Parameter]
hhhh : Execution host
jjjj : The Server with demand
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Re-execute the action after confirming that action execution of the other server is over.
[Description]
System error occurred in Action Execution Server.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Investigate the cause of error according to the message displayed in the host that executes action, and implement the corrective measures accordingly. Re-execute the action after the corrective measures are implemented.
[Description]
The environment (sound reproduction environment, modem etc.) that executes action is not set.
[Parameter]
iiii: Action control number
hhhh: Name of host on which action is executed
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Set the environment to execute action in the Action Environment Setup dialog box on the host where action is executed.
[Description]
Environment information necessary for action execution is not registered.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Register an environment for action execution using the Action Environment Setup dialog box.
[Description]
Failed to load Dynamic Link Library (llll).
[Parameter]
llll : Dynamic Link Library name that could not be loaded
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Check whether the file of dynamic link library exists. When the file exists, check if the access right is referable. If not, change it to referable one. When the file of dynamic link library does not exist, Systemwalker might have not been installed properly. In this case, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
E-Mail action cannot be executed, as mail address of send source is not specified in E-Mail send process.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Specify send source address and carry out action execution request again. Alternatively, register the source address using the Action Environment Setup dialog box.
[Description]
E-Mail action cannot be executed, as SMTP server name is not specified.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Specify an SMTP server name in the Mail sheet of the Action Environment Setup dialog box and carry out action execution request again.
[Description]
Failed to invoke the E-Mail action because it failed to connect to the SMTP server due to the cause indicated in the message. The action will be terminated abnormally.
[Parameter]
hhhh : Server name
ssss : Cause of the socket communication error
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Refer to the message, find the cause of the socket communication error and resolve the problem. Check the status of the SMTP server (such as if it is running). Depending on the settings of the SMTP server, it may deny the connection if attempted to send too many e-mails. Contact the administrator of your SMTP server for details on the settings.
[Description]
An error occurred while communicating with the SMTP server due to the cause indicated in the message. The action will be terminated abnormally.
[Parameter]
hhhh : SMTP server name
ssss: Cause of the socket communication error
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Check the following.
Whether:
connection to the network can be made with the ping command.
If not, review and modify the network environment to be able to build connections.
the IP address displayed with the ping command is the intended one.
If not, check the network settings such as the hosts file.
the SMTP server stopped or some network trouble occurred when the message was output.
If the SMTP server is not running, activate the server. In case a network trouble occurred, remove the trouble.
[Description]
The SMTP server denied the connection due to the cause indicated in the message. The action will be terminated abnormally.
[Parameter]
hhhh : SMTP server
ssss: Error returned from the SMTP server
[System Action]
Terminates the action abnormally and continues the process.
[System Administrator Response]
Report the indicated error code and the message to the administrator of your SMTP server and resolve the problem. The format of the recipient or the sender address may be invalid, or the recipient or the sender may be unauthorized.
[Description]
Failed to open file during action execution.
[Parameter]
hhhh : File name
ssss : Message indicating the contents of error
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Check whether the file exists. If yes, check that access rights that can be updated have been granted. If not, change them to updatable ones.
[Description]
Error occurred in input output process of file during action execution.
[Parameter]
ssss : Message indicating the contents of error
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Take the corrective measures according to the contents of the message.
[Description]
Failed to create work file during action execution.
[Parameter]
ffff : File name that failed to be created
ssss : Message indicating the contents of error
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Check whether access rights that can be updated have been granted on the file storage directory. If not, change them to updatable ones.
[Description]
Cannot send an e-mail because the SMTP server returned an error. The action will be terminated abnormally.
[Parameter]
hhhh: Name of the SMTP server
ssss: Cause of the error returned from the SMTP server
[System Action]
Continues the process, but the action will be terminated abnormally.
[System Administrator Response]
The cause can be attributed to the following factors:
When the address specified as From address is indicated in the cause of the error message
The specified From address may have not been registered to the SMTP server. Change the specified From address to a mail address registered to the SMTP server.
When the address specified as the send destination is indicated in the cause of the error message
The SMTP server may not permit mail transmission to the address displayed. Check if the address on the send destination is correct.
For cases other than the above, contact SMTP server administrator with error code and message and take corrective measures.
[Description]
Profile name for signing in to MS-Mail is not specified in send process of MS-Mail. So MS-Mail action could not be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Specify profile name and carry out action execution request again or register profile name in the Action Environment Setup dialog box.
[Description]
MS-Mail action cannot be executed due to failure in logging in to MS-Mail.
[Parameter]
iiii : Action control number
hhhh : Execution host
cccc : Code indicating the reason of failure
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Confirm MS-Mail environment, profile name and password in the Action Environment Setup dialog box. If any of them is incorrect, set the correct one.
[Description]
Specified MS-Mail session cannot be found.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Register the specified profile name specified in action execution and re-execute.
[Description]
Failure in send process of MS-Mail.
[Parameter]
iiii : Action control number
hhhh : Execution host
cccc : Code indicating the reason of failure
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Confirm MS-Mail environment. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Send destination address specified in MS-Mail action is not correct. So MS-Mail action cannot be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Set correct address in send destination address.
[Description]
Send file specified in MS-Mail action does not exist. So MS-Mail action cannot be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Set the correct file name in the send file name field in the Mail sheet of the Action Definition window invoked from the Monitored Event Table window. You need to create a file if no file exists.
[Description]
Failed to open the send file specified in MS-Mail action. So, MS-Mail action cannot be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Set the correct file name in the send file name field in the Mail sheet of the Action Definition window invoked from the Monitored Event Table window. When the file exists, check if the access right is referable. If not, change it to referable one.
[Description]
A short mail action could not be executed because a short mail company has not been registered.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Register a short mail company in the Short Mail sheet of the Action Environment Setup dialog box.
[Description]
Short mail action cannot be executed, as an error occurred in the exit DLL used for message conversion of short mail.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Review the exit process for message conversion of short mail.
[Description]
COM port that has been added to short mail notification does not exist in the action execution host. Action is abnormally ended.
[Parameter]
nnnn : Action control number
hhhh : Action execution host name
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Re-execute action after changing the set up of the COM port in the Action Environment Setup dialog box.
[Description]
Short mail action cannot be executed, as the COM port is being used by another process or there are no access rights.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
When COM port is in use, wait for a while and re-execute action. If no access right is granted to COM port, grant it and re-execute action. You can re-execute action in the Action Control window.
[Description]
Cannot invoke the short mail action because it failed to open the COM port. The action will be terminated abnormally.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
The following messages are logged in the event log on the host that executed the action:
Source: MpAosfB
Event ID: 4104
Refer to the cause indicated in this message and resolve the problem.
[Description]
Short mail action could not be executed due to failure in reading from the COM port or writing to the COM port.
[Parameter]
iiii : Action control number
hhhh : Execution host
cccc : Code indicating the reason of failure
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Remove the error by referring to the contents described in Cause. Take appropriate action on the host indicated in the message. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
An attempt to connect the telephone line failed as the line was engaged, so short mail action could not be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Does not execute the action.
[System Administrator Response]
Wait for a while and carry out re-execution process in the Action Control window.
[Description]
Short mail action cannot be executed, as carrier signals are not received from the telephone line.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
"NO CARRIER" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
Sort mail action could not be executed, as error signals were received from telephone line.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
"ERROR" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
Short mail action could not be executed, as dial tone could not be detected from the telephone line. The action will be terminated abnormally.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
"NO DIALTONE" was returned from the modem. See the manual of the modem in use for the reason.
If the modem is connected to the extension line, it may fail to detect the tone signal due to the configuration of extension line. If this is the case, set a command to dial the short mail number without waiting for the tone signal as the modem's initialization AT command (in the COM Port sheet of the Action Environment Setup dialog box). Refer to the manual of the modem for details on the command.
Example: AT&fX3"
[Description]
Short mail action could not be executed, as there was no response from the telephone line
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
"NO ANSWER" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
Short mail action could not be executed, as telephone line was disconnected during action execution.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Confirm the connection status of modem and the telephone number of the short mail destination.
[Description]
The modem denied dialing the specified number because the number is listed in the blacklist. The action will be terminated abnormally.
[Parameter]
iiii: Action management number
hhhh: Name of the host on which the action is invoked
[System Action]
Continues the process, but the action will be terminated abnormally.
[System Administrator Response]
Check the definitions of the event monitoring conditions and prevent that too many short mail notification actions from being invoked at the same time. Refer to the manual of the modem for details on the modem's blacklist feature.
[Description]
Pop up message action could not be executed, as error occurred in sending the pop up message.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Investigate the cause of error from the message displayed in the host that executed action. Implement corrective measures for that cause.
[Description]
Send destination address of pop up message could not be acquired. So pop up message action could not be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Investigate the cause of error from the message displayed in the host that executed action. Implement corrective measures for that cause.
[Description]
Pop up action cannot be executed on the action execution server operating in Windows98/Me. Action is abnormally ended.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Specify the Windows server containing the action execution server as the popup action execution destination host, and re-execute action.
[Description]
Audio notification action could not be executed, as sound card is not installed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Install sound driver or confirm that the installation is done correctly. If the sound drive is not installed successfully, reinstall it.
[Description]
Either the sound driver is not installed or it is being used in some other process. So Audio notification action could not be executed.
[Parameter]
iiii : Action control number
hhhh : Execution host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Confirm that the sound driver is installed. If it is installed correctly then confirm that it is not being used in other process. If the sound driver is being used by another process, conduct an investigation on the relevant process side.
[Description]
Audio notification action could not be executed, as sound driver is being used in some other process.
[Parameter]
iiii : action control number of Audio notification
hhhh : Action execution destination host
[System Action]
Continues the process.
[System Administrator Response]
Wait for a while and execute the action again in the Action Control window. If the error persists despite taking this measure, confirm that it is not being used in some other process. When the sound driver is being used by another process, conduct an investigation on the relevant process side.
[Description]
Failed to open the dictionary used for voice reproduction. So Audio notification action could not be executed.
[Parameter]
iiii : Action control number of Audio notification
hhhh : Action execution destination host
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Confirm the status of the following files (existence, access rights)
(instdir)\mpwalker\mpaosfsv\base\etc\F3CKLING.DIC
(instdir)\mpwalker\mpaosfsv\base\etc\HIGH.DIC
Set access rights that allow you to refer on the files and directories.
[Description]
Failure in speech synthesis process. Due to this Audio notification action could not be executed.
[Parameter]
iiii : action control number of Audio notification
hhhh : Action execution destination host
cccc : Action completion code
dddd : Action completion detailed code.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
Investigate the cause of failure in speech synthesis process. Implement the process responding to that cause. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Audio notification action could not be executed, as sound driver does not support the waveform format used for voice reproduction.
[Parameter]
iiii : Action control number of Audio notification
hhhh : Action execution destination host
[System Action]
Continues the process. But Audio notification process cannot be carried out.
[System Administrator Response]
Install correct sound driver.
[Description]
System error occurred during sound reproduction.
[Parameter]
iiii : action control number of Audio notification
hhhh : Action execution destination host
cccc : Action completion code
dddd : Action completion detailed code.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
By clicking the audio notification action abnormally terminated in the Action Control window, display the Property dialog box. Remove the error by referring to the contents described in the dialog box.
[Description]
Failed to execute action of control number iiii.
[Parameter]
aaaa : Action contents
iiii : Action control number
hhhh : Action execution destination host
cccc : Action completion code
dddd : Action completion detailed code.
[System Action]
Ends the action abnormally and continues the process.
[System Administrator Response]
By clicking the action abnormally terminated in the Action Control window, display the Property dialog box. Remove the error by referring to the contents described in the dialog box.
[Description]
The Event Monitor service (Action Execution Server) has started.
[System Action]
Starts Action Execution Server.
[Description]
The Event Monitor service (Action Execution Server) has stopped.
[System Action]
Terminates Action Execution Server.
[Description]
Failed to initialize Action Execution Server.
[System Action]
Shuts down Action Execution Server.
[System Administrator Response]
Restart Action Execution Server (Systemwalker MpAosfX). Contact the technician if this message occurs even after restarting the server.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to acquire installation information.
[System Action]
Shuts down Action Execution Server.
[System Administrator Response]
Check if Systemwalker is installed properly. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to initialize socket.
[Parameter]
ssss : Reason for error
[System Action]
Shuts down the Action Execution Server.
[System Administrator Response]
Remove the error by referring to the contents described in Reason.
[Description]
Action could not be executed, as memory was insufficient.
[System Action]
Action is not executed.
[System Administrator Response]
Increase the memory or close the unnecessary applications. After that re-execute action.
[Description]
Error occurred in socket function.
[Parameter]
ffff : Function name in which error occurred
ssss : Reason for error
[System Action]
Action is not executed.
[System Administrator Response]
Remove the error by referring to the contents described in Reason.
[Description]
Thread ended abnormally. Due to that Action Execution Server is shutdown.
[System Action]
Action Execution Server is stopped.
[System Administrator Response]
Investigate the cause of error from the message displayed just before. Confirm that it is not an environment problem like memory, disk etc. and if necessary, add more memory or replace the disk to remove the environmental problem. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Error occurred in system function.
[Parameter]
ffff : Function name in which error occurred
ssss : Reason for error
[System Action]
Action is not executed.
[System Administrator Response]
Remove the error by referring to the contents described in Reason.
[Description]
Could not load the Dynamic Link Library.
[Parameter]
dddd : Link library name
ssss : Reason of error occurrence
[System Action]
Action is not executed.
[System Administrator Response]
Check whether DLL exists. If yes, then check whether the access rights of the file enable referencing. In other cases, take the corrective measures according to the reasons of error. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The action was about to be executed but the specified file does not exist.
[Parameter]
ffff : File name
[System Action]
Action is not executed.
[System Administrator Response]
Re-executes the action after specifying the correct file or creating the required files.
[Description]
Action cannot be executed, as the action execution environment is not defined.
[System Action]
Action is not executed.
[System Administrator Response]
Define the action execution environment in the Action Environment Setup dialog box.
[Description]
Ms-Mail action cannot be executed, as profile name is not specified.
[System Action]
Action is not executed.
[System Administrator Response]
Specify a name in the Profile Name field of MS-Mail in the Mail sheet of the Action Environment Setup dialog box.
[Description]
MS-Mail action cannot be executed, as the MS-Mail log on failed.
[Parameter]
ssss : Reason of error occurrence
[System Action]
Action is not executed.
[System Administrator Response]
Remove the cause of the logon error by referring to the contents described in Reason.
[Description]
MS-Mail action cannot be executed, as the specified MS-Mail session does not exist.
[System Action]
Action is not executed.
[System Administrator Response]
Re-executes the action after specifying correct MS-Mail session.
[Description]
Failed in the transmission process of MS-Mail.
[Parameter]
ssss : Reason of error occurrence
[System Action]
Action is not executed.
[System Administrator Response]
Remove the cause of the transmission error by referring to the contents described in Reason.
[Description]
The MS-Mail action cannot be executed, as the address specified in MS-Mail is not correct.
[System Action]
Action is not executed.
[System Administrator Response]
Re-executes the action after specifying the correct address.
[Description]
File specified in MS-Mail does not exist.
[System Action]
Action is not executed.
[System Administrator Response]
Re-execute the action after specifying correct file or creating file.
[Description]
Failed to open the file specified in MS-Mail.
[System Action]
Action is not executed.
[System Administrator Response]
Specify the correct file name at the action definition in the Monitored Event Table window.
[Description]
The specified short mail company is not registered.
[Parameter]
cccc : Company name
[System Action]
Action is not executed.
[System Administrator Response]
Specify the short mail company registered in the Short Mail sheet in the Action Environment Setup dialog box as part of the action definition of the Monitored Event Table window.
[Description]
The short mail action was about to be executed, but an error occurred in the message conversion process.
[System Action]
Action is not executed.
[System Administrator Response]
Check the content of the message sent via short mail in the action definitions of the Monitored Event Table window to see if it contains invalid characters. If necessary, change the message so that it contains only the characters that can be sent via short mail.
[Description]
The short mail action was about to be executed, but there was failure in opening the COM port.
[Parameter]
ssss : Reason of error occurrence
[System Action]
Action is not executed.
[System Administrator Response]
Refer to the cause indicated in the message and resolve the problem.
If "Access denied" is indicated as the cause, the modem may be currently in use by another process. Check if the modem is not in use (such as by RAS connection).
[Description]
The short mail action was about to be executed, but the input output error of COM port occurred.
[Parameter]
ssss : Reason of error occurrence
[System Action]
Action is not executed.
[System Administrator Response]
Remove the cause of the input output error by referring to the contents described in Reason.
[Description]
The short mail action was about to be executed, but the line was busy.
[System Action]
Action is not executed.
[System Administrator Response]
Re-execute the action after waiting for a while. Check the modem status in case this message occurs frequently.
[Description]
The short mail action was about to be executed, but carrier signals cannot be received from the telephone line.
[System Action]
Action is not executed.
[System Administrator Response]
"NO CARRIER" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
The short mail action was about to be executed, but received error signals from the telephone line.
[System Action]
Action is not executed.
[System Administrator Response]
"ERROR" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
The short mail action was about to be executed, but could not detect dial tone from the telephone line.
[System Action]
Action is not executed.
[System Administrator Response]
"NO DIALTONE" was returned from the modem. See the manual of the modem in use for the reason.
If the modem is connected to the extension line, it may fail to detect the tone signal due to the configuration of extension line. If this is the case, set a command to dial the short mail number without waiting for the tone signal as the modem's initialization AT command (in the COM Port sheet of the Action Environment Setup dialog box). Refer to the manual of the modem for details on the command.
Example: AT&fX3"
[Description]
The short mail action was about to be executed, but there was no response from telephone line.
[System Action]
Action is not executed.
[System Administrator Response]
"NO ANSWER" was returned from the modem. See the manual of the modem in use for the reason.
[Description]
The short mail action was about to be executed, but the telephone line was disconnected.
[System Action]
Action is not executed.
[System Administrator Response]
Re-executes after waiting for a while.
[Description]
The modem denied dialing the specified number because the number is listed in the blacklist. The action will be terminated abnormally.
[System Action]
Continues the process, but the action will be terminated abnormally.
[System Administrator Response]
Check the definitions of the event monitoring conditions and prevent that too many short mail notification actions from being invoked at the same time. Refer to the manual of the modem for details on the modem's blacklist feature.
[Description]
The audio notification action could not be executed, as the sound driver is not installed.
[System Action]
Action is not executed.
[System Administrator Response]
Installs the sound driver.
[Description]
The audio notification action could not be executed, as the sound driver could not be called.
[System Action]
Action is not executed.
[System Administrator Response]
Check whether the sound driver is installed or whether it is being used by another process. If not installed, install the sound driver and if it is being used, wait for a while and execute the action again.
[Description]
The audio notification action could not be executed, as the sound driver is being used in some other process.
[System Action]
Action is not executed.
[System Administrator Response]
Re-executes after waiting for a while.
[Description]
Error occurred in audio reproduction.
[Parameter]
cccc : Error code
[System Action]
Stops audio reproduction.
[System Administrator Response]
Remove the error by referring to the contents described in Error code.
[Description]
Failed to initialize voice synthesizer engine.
[System Action]
Aborts the process.
[System Administrator Response]
Check if voice synthesizer is installed properly and voice can be reproduced under the environment.
[Description]
Cannot play the sound because the voice synthesizer engine (SAPI) is not installed. The action will be terminated abnormally.
[System Action]
Continues the process, but the action will be terminated abnormally.
[System Administrator Response]
Install the product that has the voice synthesizer engine (SAPI) included.
[Description]
There is an abnormality in data received from definition window.
[Parameter]
cccc : Item code of the received data
dddd : Value of the received data
[System Action]
Ends the process.
[System Administrator Response]
Check if Systemwalker is installed properly. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
The form of the event monitoring condition definition is incorrect.
[Parameter]
ffff: Name of event monitoring condition definition file
[System Action]
Aborts the process
[System Administrator Response]
Check the method to define event monitoring conditions. Define event monitoring conditions from the Monitored Event Table window.
[Description]
Failed to get the list of short mail companies.
[System Action]
Continues the process. But short mail action cannot be carried out.
[System Administrator Response]
Check if Systemwalker is installed properly. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to acquire the calendar service library.
[System Action]
Continues the process. But condition as per date specified in action condition, is ignored. Further, settings as per date cannot be done in condition of Monitored Event Table.
[System Administrator Response]
Check whether the calendar service is installed. If yes, check that the service is running and if not, activate the service.
If the error is not solved even after the service has been activated, collect data and contact a Fujitsu system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to acquire the library that fetches the system name list information.
[System Action]
Continues the process. But operation cannot be carried out according to the selection of system name, in Monitored Event Table.
[System Administrator Response]
Check if Systemwalker is installed properly. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Error occurred in file operation.
[System Action]
Continues the process.
[System Administrator Response]
Take corrective measures according to the message displayed just before.
[Description]
The linkage function for synchronizing with the Monitored Event Table window due to an error.
[System Action]
Continues the process of the Event Monitor and the Action Management functions, but the Monitored Event Table window and the Action Environment Setup dialog box are disabled.
[System Administrator Response]
Collect data and contact a Fujitsu's system engineer. After collecting data, restart Systemwalker.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
This message appears when uninstalling Systemwalker Centric Manager after defining 1025 lines or more event monitoring condition definitions in the environment where Systemwalker Centric Manager (V5.0L10 and later) and Systemwalker Operation Manager coexist. On Systemwalker Operation Manager, up to 1024 event monitoring condition definition lines are valid.
[System Action]
Continues the process within the maximum number of definitions.
[System Administrator Response]
Review event monitoring condition definitions according to the system operation.
[Description]
Memory is insufficient.
[Parameter]
ssss : Calling source process name or function name
[System Action]
Ends the process.
[System Administrator Response]
Extends the size of page file or increase the memory.
[Description]
Auto Operation Support process ended.
[Parameter]
pppp : Name of the process that ended
cccc : Completion code of the process that ended
[System Action]
Ends the process.
[System Administrator Response]
Collect data and contact a Fujitsu's system engineer.
1) Check Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
2) Collect the Dr. Watson log.
[Description]
Internal operation abnormality occurred in Auto Operation Support daemon
[Parameter]
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Collect data and contact a Fujitsu's system engineer.
1) Check Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
2) Collect the Dr. Watson log.
[Description]
Failed to receive the data during the process.
[Parameter]
pppp : Occurrence source process name in which error is occurred
[System Action]
Ends the process.
[System Administrator Response]
Eliminate the cause of failure by referring to the message that is displayed before and restart Systemwalker.
[Description]
Failed to send the data during the process.
[Parameter]
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Eliminate the cause of failure by referring to the message that is displayed before and restart Systemwalker.
[Description]
Failed to open the definition file
[Parameter]
ssss : Message showing the error contents
ffff : File name of definition file
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Check if the file displayed exists and if access rights that allow you to update the file are granted.
[Description]
Failed to read definition file.
[Parameter]
ffff : File name of definition file
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Check if the file displayed exists and if access rights that allow you to refer to the file are granted.
[Description]
Failed to write definition file
[Parameter]
ffff : File name of definition file
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Check if the file displayed exists and if access rights that allow you to update the file are granted.
[Description]
Failed to receive data during the process.
[Parameter]
ssss : Reason code that failed
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
If the message is output during portscan etc., no action is required. In cases other than the above, restart the Systemwalker MpAosfB service.
[Description]
Failed to send data during the process.
[Parameter]
ssss : Reason code that failed
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Restart the Systemwalker MpAosfB service.
[Description]
Failed to open definition file.
[Parameter]
ssss : Message showing the error contents
ffff : File name
pppp : Occurrence source process name in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Check if the file displayed exists and access rights that allow you to refer to the file are granted.
[Description]
System function name ffff called from cccc failed due to the reasons shown in ssss.
[Parameter]
cccc : Calling source process name or function name
ffff : System function name
ssss : Message showing the reason of failure
[System Action]
Ends the process.
[System Administrator Response]
Remove the error by referring to the contents described in Reason. If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
An error is found in the received data.
[Parameter]
pppp: Name of the process that caused the error
qqqq: Name of the sender process
[System Action]
Terminates the process.
[System Administrator Response]
Collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
[Description]
Failed to get shared memory. Process ended.
[Parameter]
mmmm : Name of shared memory in which error occurred
pppp : Name of process in which error occurred
[System Action]
Ends the process.
[System Administrator Response]
Expands the size of page file or increases the memory.
[Description]
Failed to obtain the sharing control table used by the Event Monitor service.
[Parameter]
pppp: Name of the process in which the error occurred
nnnn: Shared memory
[System Action]
Terminates the process.
[System Administrator Response]
Investigate the cause of error from the message displayed just before.
If you cannot find corrective measures, collect data and contact a Fujitsu's system engineer.
Collect data by checking Event Monitor and Action Execution/System Monitor with the Maintenance Information Collection Tool.
