2.3 Messages Starting with MpAosfP

This section explains messages starting with MpAosfP. These messages are generated by the power control, service/application startup function.

[Windows]MpAosfP: INFO: 100: Systemwalker MpAosfP is normal start.

[Description]

Service Systemwalker MpAosfP has started.

[Windows]MpAosfP: INFO: 101: Systemwalker MpAosfP is normal end.

[Description]

Service Systemwalker MpAosfP has closed.

[Windows]MpAosfP: ERROR: 102: Systemwalker MpAosfP is abnormal end.

[Description]

Service Systemwalker MpAosfP has ended abnormally.

[System Action]

Closes the service. Service/application startup and power control functions are not working.

[System Administrator Response]

Find out the cause of error. If you cannot find corrective measures, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 104: Internal error occurs end of Process function name=ffff error code=cccc contents=dddd

[Description]

Error has occurred in function.

[Parameter]

ffff : Function name

cccc : Error code

dddd : Error contents

[System Action]

Aborts the process.

[System Administrator Response]

Find out the cause of error from function name, error code, error contents. If you cannot find corrective measures, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: INFO: 106: System Reboot Request is normal end.

[UNIX]MpAosfP: INFO: 106: System Reboot Request is normal end

[Description]

Requested re-booting of the system has completed successfully.

[Windows]MpAosfP: INFO: 107: System Shutdown Request is normal end. < CCCC >

[UNIX]MpAosfP: INFO: 107: System Shutdown Request is normal end< CCCC >

[Description]

Requested shut down of the system has completed successfully.

[Parameter]

CCCC: Command name + Parameter

[Windows]MpAosfP: INFO: 108: System Power Off Request is normal end. < CCCC >

[UNIX]MpAosfP: INFO: 108: System Power Off Request is normal end< CCCC >

[Description]

Power off request of system is executed properly from Operation Management Client of Systemwalker Centric Manager.

[Parameter]

CCCC : Command name + Parameter

[Windows]MpAosfP: ERROR: 109: System Reboot Request is abnormal end.

[Description]

Failed to re-boot the system.

[System Action]

Aborts the process.

[System Administrator Response]

Shut down the system and re-start it. Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer if the message occurs frequently.

[Windows]MpAosfP: ERROR: 110: System Shutdown Request is abnormal end.

[Description]

Failed to shut down the system.

[System Action]

Aborts the process.

[System Administrator Response]

Shut down the system. Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer if the message occurs frequently.

[Windows]MpAosfP: ERROR: 111: System Power Off Request is abnormal end, only System Shutdown is executed.

[Description]

Failed to power off the system. Power off the system after the shut down process.

[System Action]

Shut down the system. Cannot power off. Auto power on will not be carried out at the time of next power on.

[System Administrator Response]

Power off the system. Power on the system manually at the time of next power on.

Check whether the environment is appropriate by referring to the manual of power control device or that of power control software.

[Windows]MpAosfP: WARNING: 115: Creating End Event(iiii) fails, so this End Event is not use for waiting.

[Description]

Failed to create an environment for queuing the completion event. Queuing is not possible for the completion event.

[Parameter]

iiii : Failed completion event

[System Action]

Cannot carry out queuing process for this completion event.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 116: End Event is more than MAX(50).

[Description]

Completion event has exceeded the maximum value (50).

[System Action]

Ignore the completion event exceeded the maximum value 50.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 117: Because failing open Service Database, can not execute service.

[Description]

Failed to open the service database.

[System Action]

Cannot carry out service startup process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 118: Fails executing Service(ssss).

[Description]

Failed to start the service by using service/application startup function.

[Parameter]

ssss : Service name

[System Action]

Cannot carry out service startup process. Continues with the next process.

[System Administrator Response]

Check the service environment i.e. service name, installation environment.

[Windows]MpAosfP: WARNING: 119: Previous Service(tttt) is not executing, so Service(ssss) is not executed.

[Description]

Could not start the service as the previous service is not started by using service / application startup function.

[Parameter]

ssss : Not started service

tttt : Not started earlier service

[System Action]

Cannot carry out service startup process. Continues with the next process.

[System Administrator Response]

Check the service schedule and the environment of the earlier service.

[Windows]MpAosfP: WARNING: 120: Previous Service(ssss) of Service(tttt) is not defined.

[Description]

It is necessary to define previous service name in service/application startup function.

[Parameter]

ssss : Service name

tttt : Previous service name defined by ssss service

[System Action]

Continue the process by following the specifications of previous service which is not yet started.

[System Administrator Response]

Define the previous service correctly. Delete the definition if not required.

[Windows]MpAosfP: WARNING: 121: Fails executing Application(aaaa).

[Description]

Failed to start the application defined by using service/application startup function.

[Parameter]

aaaa : Application name

[System Action]

Application has not started. Continues with the next process.

[System Administrator Response]

Check the application environment.

[Windows]MpAosfP: WARNING: 122: Previous Service(ssss) is none.

[Description]

Previous service defined by using service/application startup function does not exist.

[Parameter]

ssss : Service name

[System Action]

Continue the process by following the specifications of previous service which is not yet started.

[System Administrator Response]

Check the earlier service.

[Windows]MpAosfP: WARNING: 123: Service(ssss) is none.

[Description]

Service defined by using service/application startup function does not exist.

[Parameter]

ssss : Service name

[System Action]

Service has not started. Continues with the next process.

[System Administrator Response]

Check whether the service name is correct or not. Also check whether the service is installed correctly or not.

[Windows]MpAosfP: WARNING: 124: Fails executing command(cccc).

[Description]

Failed to execute the command on exit.

[Parameter]

cccc : Command name

[System Action]

Cannot execute the command. Continues with the next process.

[System Administrator Response]

Check the command environment.

MpAosfP: INFO: 127 : Waiting for End Event(iiii) is not canceled.

[Description]

There was no completion event notification in between the server shut down time and the waiting period even though the monitoring process for completion was carried out.

[Parameter]

iiii : Completion event

[System Action]

Releasing queuing, shut down and power off the server.

[Windows]MpAosfP: WARNING: 128: uuuu session is not canceled.

[Description]

Could not release the link from user, even though completion monitoring was carried out, as the actual waiting period lapsed from the shut down time of server.

[Parameter]

uuuu : User name

[System Action]

Releasing queuing, shut down and power off the server.

[Windows]MpAosfP: ERROR: 129: Fails dynamic allocation, so process does not continue.

[Description]

Cannot continue the process due to failure in acquiring the dynamic area.

[System Action]

Aborts the process.

[System Administrator Response]

Make necessary provisions in the system or in machine for acquiring the necessary dynamic area.

[Windows]MpAosfP: WARNING: 132: Internal error occurs function name=ffff error code=cccc contents=dddd

[UNIX]MpAosfP: INFO: 132: Internal error occurs function name=ffff error code=cccc contents=dddd

[Description]

Error in calling the function.

Function name = CreateProcess Error code = 2
Failed to start the application registered to the Application Execution sheet in the Service/Application Execution Pattern Definition dialog box.
Function name = GetServiceKeyName Error code = 1060
Failed to start the service registered to the Service Execution sheet in the Service/Application Execution Pattern Definition dialog box.

[Parameter]

ffff : Function name

cccc : Error code

dddd : Error contents

[System Action]

Continue the process.

[System Administrator Response]

Find out the cause of error from function name, error code and error contents.

Function name = CreateProcess Error code = 2
Check that the path of the application registered to the Application Execution sheet in the Service/Application Execution Pattern Definition dialog box is correct.
Function name = GetServiceKeyName Error code = 1060
Check that the name of the service registered to the Service Execution sheet in the Service/Application Execution Pattern Definition dialog box.

If the cause is still not clear, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

MpAosfP: WARNING: 133: Specified Power Control Hardware does not support that next system schedule is dddd after cccc days.

[Description]

Date and time for the next system startup is not entered in the scope which is not supported by the specified power control function. Due to this, next auto power on process cannot be carried out.

[Parameter]

cccc : Number of days from today

dddd : The scheduled date and time

[System Action]

Cannot perform the next auto power on process.

[System Administrator Response]

Perform scheduling on such days on which power control is possible. Or, carry out the manual process at the time of next startup.

Number days on which power control is possible are shown below.

PMAN/L : 45 Days

PowerChutePlus : 14 Days

[Windows]MpAosfP: WARNING: 134: Next system start is not scheduled.

[Description]

Date and time of next system startup exceeds the number of days on which power control is possible. Due to this, next auto power on process cannot be carried out.

[System Action]

Cannot perform the next auto power on process.

[System Administrator Response]

Perform scheduling on such days on which power control is possible. Or, carry out the manual process at the time of next startup.

Number days on which power control is possible are shown below.

PMAN/L : 45 Days

PowerChutePlus : 14 Days

[Windows]MpAosfP: ERROR: 136: upssleep is not found, so set power chute plus or system path(path=XXX).

[Description]

Could not find the power off command of Power Chute Plus (UPSSLEEP.EXE) or PowerChute Business Edition for disconnecting the power supply.

[Parameter]

XXX: Information of specified system path

[System Action]

Cancel the power off process and carry out the shut down process.

[System Administrator Response]

Install UPSSLEEP.EXE. Or, confirm the system path setup of UPSSLEEP.EXE.

An example of system path is shown below:

When the installation directory of UPSSLEEP.EXE is C:\Program Files\PowerChute\upssleep.exe
C:\Program Files\PowerChute

See the OS manual for how to register system path.

[Windows]MpAosfP: ERROR: 137: PMAN/L power control command is not found, so set PMAN or system path(path=XXX).

[Description]

Could not find the power off command of PMAN/L server power control for disconnecting the power supply.

[Parameter]

XXX: Information of specified system path

[System Action]

Cancel the power off process and carry out the shut down process.

[System Administrator Response]

Confirm the install of PMAN/L and system path setup.

See the OS manual for how to register system path.

[Windows]MpAosfP: ERROR: 138: Because of Dynamic allocation fails, Automatic Operations Support Facility is stop.

[Description]

Could not acquire the dynamic area. Closes Auto Operation Support.

[System Action]

Aborts the process.

[System Administrator Response]

Increase the usable dynamic area by increasing the usable virtual storage and closing the unnecessary applications. After that, start the service (Systemwalker MpAosfP).

[Windows]MpAosfP: ERROR: 139: Automatic Operations Support Facility is wrong, reinstall Automatic Operations Support Facility.

[Description]

Error in the environment of Auto Operation Support. Re-install the Auto Operation Support.

[System Action]

Aborts the process.

[System Administrator Response]

Install Systemwalker. If the message keeps appearing even after installation, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 156: MpStpSv is not found, so set Power Control Software or system path(path=XXX).

[Description]

Tried to conduct power off process but could not found power stop command (MpStpSV.EXE) of power control software corresponding to Systemwalker.

[Parameter]

XXX: Information of specified system path

[System Action]

Stop the power off process and shut down.

[System Administrator Response]

Install MpStpSV.EXE or confirm the settings of system path of MpStpSV.EXE. See the power control software manual and OS manual for installation of MpStpSv.EXE and confirmation and setup of system path respectively.

[Windows]MpAosfP: WARNING: 200: SMTP server name is not specified.

[Description]

SMTP server host name of E-mail send destination is not specified.

[System Action]

Cannot send mail. Continues with the next process.

[System Administrator Response]

Check the SMTP server host name of the E-mail send destination.

[Windows]MpAosfP: WARNING: 232: User name for Popup message occurs error.

[Description]

Error in user name process of pop-up messages.

[System Action]

Does not carry out pop-up message notification. Continues with the next process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

MpAosfP: WARNING: 234: Popup message process occurs error.

[Description]

Error has occurred while sending pop-up messages. There are chances that the specified user or the computer may not exist or the Messenger service is not started.

[System Action]

Continues the process.

[System Administrator Response]

Confirm whether the Messenger service has started or not. Also confirm the specified user or computer name.

[Windows]MpAosfP: WARNING: 235: Popup message sending process occurs error.

[Description]

Error in sending pop-up messages.

[System Action]

Continue the process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 236: Domain is none, or Server is none.

[Description]

Domain specified at the time of sending pop-up message does not exist. Unable to find the server in domain.

[System Action]

Does not carry out pop-up message notification. Continues with the next process.

[System Administrator Response]

Confirm whether the specified domain is correct or not.

[Windows]MpAosfP: WARNING: 271: Systemwalker Centric Manager is not installed, no notice to stop is sent.

[Description]

Systemwalker Centric Manager is not installed. Notification by e-mail or pop-up message will not be performed.

[System Action]

Cannot perform completion notification. Continues with the next process.

[System Administrator Response]

Install Systemwalker Centric Manager.

MpAosfP: WARNING: 272: Because the action control server is not operating, no notice is sent.

[Description]

[Windows version]

Systemwalker MpAosfB service is not started or failed in communication with Systemwalker MpAosfB service.

[UNIX version]

Systemwalker Centric Manager is not started or failed in communication with Systemwalker Centric Manager.

Due to this, notification by e-mail or pop-up message will not be performed.

[System Action]

Cannot perform completion notification. Continues with the next process.

[System Administrator Response]

[Windows version]

Start Systemwalker MpAosfB service. If the action execution destination is set to another server on Centric Manager, check that there is no problem in the communication environment with the server specified as the destination.

[UNIX version]

Start Systemwalker Centric Manager. Check that there is no problem in the communication environment with the server specified as the action execution destination on Centric Manager.

MpAosfP: WARNING: 273: Because memory is lack, E-Mail sending request is not executed.

[Description]

Could not request to send E-Mail due to insufficient memory.

[System Action]

Cannot send mail. Continues with the next process.

[System Administrator's Response]

Increase the memory. Close the unnecessary applications and increase the usable memory.

MpAosfP: WARNING: 301: Fails Power Off for the target agent(hhhh).

[Description]

Failed to power off the managed host from the managing host with the batch power control function. The cause of this failure would be as follows:

Wrong managed host name
The managed host is not running
Calendar service is not running on the managed host
Error occurred in communication environment

[Parameters]

hhhh: Name of the managed host of which power off has failed.

[System Action]

Ignores failure in power off of the managed host and Continues with the process.

[System Administrator Response]

Check whether the managed host is running and power control service is operating. After identifying and resolving the cause of the failure, power off the managed host.

[Windows]MpAosfP: WARNING: 1000: Host name is none

[Description]

Target host name for on/off is not specified in power on/off of remote server.

[System Action]

Aborts the process.

[System Administrator Response]

Specify the correct host name.

[Windows]MpAosfP: WARNING: 1001: Host name length is more than 256.

[Description]

The name of the target host for server power on/off specified on the remote server exceeds 256 bytes.

[System Action]

Aborts the process.

[System Administrator Response]

Specify the correct host name.

[Windows]MpAosfP: ERROR: 1002: PMAN/L Power Control API parameter error.

[Description]

Error has occurred in the parameter of PMAN/L power control API. The error is in power on/off of remote server.

[System Action]

Aborts the process.

[System Administrator Response]

Check the host name. If you cannot find the cause, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 1003: PMAN/L Power Control Environment error.

[Description]

There is improper execution environment of PMAN/L power control in power on/off of remote server.

[System Action]

Aborts the process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 1004: PMAN/L Power Control send/recv error

[Description]

Error has occurred in power on/off of remote server while transmitting the requested PMAN/L power control.

[System Action]

Aborts the process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 1005: PMAN/L Power Control schedule error.

[Description]

Error in the schedule setup of PMAN/L power control.

[System Action]

Aborts the process.

[System Administrator Response]

Check PMAN/L setup.

[Windows]MpAosfP: WARNING: 1006: PMAN/L Power Control is prohibited power off/on.

[Description]

Cannot power on/off as it is not allowed.

[System Action]

Aborts the process.

[System Administrator Response]

Confirm the status/environment of the server on which power on/off process is carried out. If you cannot find the cause, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 1007: For Key controlling, Power Control is not done.

[Description]

Power control box key is in "OPERATE" mode.

[System Action]

Aborts the process.

[System Administrator Response]

Make the mode of power control box key as "LOOK".

[Windows]MpAosfP: WARNING: 1008: The light goes out, Power Control is not done.

[Description]

Power control is not possible as the power on server is failed.

[System Action]

Aborts the process.

[User Response]

Reserve available space if there is not enough available space in the file system.

[System Administrator Response]

Reserve available space if there is not enough available space in the file system.

If the problem persists even after reserving the space, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 1009: Power off is already done.

[Description]

Server specified is already switched off or is in power off status.

[System Action]

Aborts the requested power off process. Continues power off process to the server which is in the middle of the process.

[Windows]MpAosfP: WARNING: 1100: Parameter is none.

[Description]

Parameter of the command is not specified.

[System Action]

Aborts the process.

[System Administrator Response]

Re-execute by specifying the parameter.

[Windows]MpAosfP: ERROR: 1101: Socket can not be opened.

[Description]

Failed to open socket.

[System Action]

Aborts the process.

[System Administrator Response]

Check TCP/IP environment of the system. If you cannot find the cause of error, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: WARNING: 1102: Fails getting self hostname.

[Description]

Error has occurred while getting the self host name.

[System Action]

Aborts the process.

[System Administrator Response]

MpAosfP: WARNING: 1103: Host name resolution error.

[Description]

Cannot decide the proper host name for remote power control.

[System Action]

Aborts the process.

[System Administrator Response]

Check the host name. If you cannot find the cause of error, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

MpAosfP: ERROR: 1104 Internal error occurs.

[Description]

Internal operation error has occurred in the power control process.

[System Action]

Aborts the process.

[System Administrator Response]

Collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 1105: Send error occurs.

[Description]

Transmission error has occurred in the power control process.

[System Action]

Aborts the process.

[System Administrator Response]

Check TCP/IP environment of the system. Confirm SNMP adapter environment of send destination. If you cannot find the cause of error, collect data of power control_calendar with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.

[Windows]MpAosfP: ERROR: 1107: PMAN/L control dll(F3DMIF32.DLL) is none.

[Description]

DLL (F3DMIF32.DLL) useful for PMAN/L control does not exist.

[System Action]

Power control function is not working. Carries out the shut down process.

[System Administrator Response]

Install the DLL useful for PMAN/L control.