5.2.2 Troubleshooting command execution problems

When the NetExec command is executed, the message The server does not respond to the connect request. is displayed.

JP1/Script is not installed on the connection target computer.

Install JP1/Script on the computer you wish to connect to, and then restart Windows.

The script was executed in the logon space, but the Script launcher or the Script Launcher service was not active on the connection target computer.

Start the Script launcher or the Script Launcher service.

The script was executed in the service space, but the JP1/Script service was not active on the connection target computer.

Start the JP1/Script service.

A logical host name (logical IP address) was specified as the connection target computer, but failover occurred at the logical host.

Specify a physical host name (physical IP address), not a logical host name (logical IP address), as the connection target computer.

When you specify a logical host name as the connection target computer, register JP1/Script into the cluster.

When the NetExec command is executed, the message unknown user name or bad password. is displayed.

A script with Logon set as the start type was executed by using the automatic startup function or from JP1/Script Manager. If the script was executed directly, the user account used to log on to Windows does not exist on the connection target computer, or the Guest account is invalid.

Check the connection target computer to make sure that the Guest account is valid.

Make sure that the user account used to log onto Windows exists on the connection target computer.

A script whose start type is Service was executed using the automatic start function, but the user account set in the JP1/Script service does not exist on the connection target computer, or the Guest account is invalid.

Check the connection target computer to make sure that the Guest account is valid.

Make sure that the user account set in the JP1/Script service exists on the connection target computer.

The script was started from a JP1/AJS service program, but the OS user account mapped to the JP1 user executing the script does not exist on the connection target computer, or the Guest account is invalid.

Check the connection target computer to make sure that the Guest account is valid.

Make sure that the OS user account mapped to the JP1 user executing the script exists on the connection target computer.

The script was started from a service program other than JP1/AJS, but the user account set in each service account does not exist on the connection target computer, or the Guest account is invalid.

Check the connection target computer to make sure that the Guest account is valid.

Make sure that the user account set in each service program exists on the connection target computer.

When the NetExec command is executed, the message The server is not logged on through the logon user specified in the startup parameter for the Script Launcher service. is displayed.

The script was executed in the logon space of the Script Launcher service, but the user specified in the start parameter has not logged on.

Log on as the logon user specified in the start parameter.

When the NetExec command is executed, the message The user who executed the NetExec command is not permitted to perform the operation in the call-destination computer. is displayed.

The NetExec command was executed by a user who is not permitted to do so.

Log on as a user who is permitted to execute the NetExec command on the connection target computer.

When the NetExec command is executed, the message Access is denied. Check the file attributes or the security. is displayed.

The script was executed by using the automatic startup function or from a service program such as an upper-level service program, but a local system account was set as the system account.

If the script was executed by using the automatic startup function or from a service program such as an upper-level service, set a user account that exists on the connection target computer as the service account.

When the SetGV, GetGV, DeleteGV, or NetExec command was executed, the message This command cannot be executed. was displayed.

Settings at the connection target computer prohibit execution of this command on a client.

Check the JP1/Script Manager settings at the connection target computer to make sure that execution of this command is permitted on a client.

After the Exec, NetExec, or CallSpt command was executed, an unexpected code was set in the _EXEC_RTN_ reserved variable.

An error occurred in the execution file that was started.

Execute the executable file by itself to make sure that there is no error and that the executable file does not return the code that was set in _EXEC_RTN_.

If an application error occurs in the executable file, a value such as -1073741819 (hexadecimal C0000005) is set.

When the Beep command was executed, an error code such as 0002 (the system cannot find a specified file) was output.

This is caused by a restriction of the OS or hardware.

Take corrective action, for example by using the IMEventMessage command. For details, see the notes in 8.13.3 Beep (sound a beep from the speakers).

A beep did not sound when the Beep command was executed.