Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 2


KAVU3550-W

The execution file (file-name) was not found.

The executable file does not exist.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

  1. The relative path to the executable file has been specified, but the folder or directory necessary for execution has not been set in the PATH environment variable.

  2. The specified executable file is on a network drive.

  3. In a WOW64 environment, an executable file in %systemroot%\system32 has been specified.

  4. If this message is output after execution of an action job, the platform set in the detailed definition of the action job is incorrect.

  5. When a job is executing, the specified executable file is not found.

Take one of the following actions according to the cause of the error, and then reissue the request.

  1. Make sure that the folder or directory necessary for the PATH environment variable has been correctly set.

  2. Do not specify the path beginning with a network drive name. Instead, specify the path beginning with a computer name (for example, \\computer-name\shared-folder\executable-file-name).

  3. In a WOW64 environment, if a file in %systemroot%\system32 is specified, file access is redirected to %systemroot%\syswow64. Take either of the following corrective actions:

    - In Windows Server 2012 or the 64-bit version of Windows Server 2008, specify %systemroot%\sysnative instead of %systemroot%\system32, and then re-execute the job.

    - In Windows Server 2003 (x64), when you execute a job in a WOW64 environment, disable file system redirection, and then re-execute the job.

    For details about how to execute a job in a WOW64 environment, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

  4. Recheck the detailed definition of the action job, and then re-execute the action job.

  5. Make sure that the executable file exists, and then re-execute the job. Also, make sure that the executable file will not be moved or deleted.