Error message
0xB007: The Task Link Engine process startup request was not accepted. |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Points to check
Was the client Task Link engine started?
If so, the client Task Link icon will be displayed in the task tray.
Does the user logged in to the client have power off privileges?
The method used to check the user rights varies depending on the operating system. The following example is for Windows(R) 2000:
Windows(R) 2000
Select Control Panel >> Administrative Tools >> Local Security Policy to display the Local Security Policy window. Select Local Policies >> User Rights Assignment, and check the content set in Shut down the system.
Is the client specified in the parameter of the poffcli command correct?
Does the client specified in the parameter of the poffcli command exist?
Is the host name of the client specified in the parameter of the poffcli command correct?
Is the client specified in the parameter of the poffcli command connected to the network?
You can execute the ping command in the command prompt window on the server to check it. If there is a response, the client is connected to the network.
Cause
The client Task Link engine was not started.
If the client Task Link engine was not started, the client Task Link function cannot be used.
The user logged in to the client does not have power off privileges.
The host name of the client specified in the parameter of the poffcli command cannot be resolved.
Action method
If the client Task Link engine was not started
The following methods can be used to start the client Task Link engine:
Registration of the client Task Link in the startup program.
Register the client Task Link in the startup program on the client. Refer to the following manual for details:
"Definition for Task Link with Clients" in the Installation Guide
Manual startup by the user logged in to the client.
Select Start (or Apps) >> Systemwalker Operation Manager >> Client Task Link.
If the user that logged in to the client does not have power off privileges
Select Control Panel >> Administrative Tools >> Local Security Policy to display the Local Security Policy window. Select Local Policies >> User Rights Assignment, and add the user logged in to Shut down the system.
If the client specified in the parameter of the poffcli command is incorrect
If the client specified in the parameter of the poffcli command does not exist, specify an existing client.
If the host name of the client specified in the parameter of the poffcli command is incorrect, specify a correct host name.
If the connection on the network of the client specified in the parameter of the poffcli command cannot be confirmed (the ping command does not run normally):
Check the network cable connection.
Define the host name and IP address in the hosts file.
Information
Adding the host name and IP address to the hosts file
The method varies depending on the operating system, so use the appropriate one. The following example is for Windows(R) 2000.
[Windows(R) 2000]
Edit the hosts file in systemDirectory\system32\drivers\etc.
Add the host name and IP address to the hosts file from the line following the one on which "127.0.0.1 localhost" is written, in the following format:
ipAddress hostName (domainName)
