9.5.1 Notes when using JP1/AJS3 for x86 in a WOW64 environment

This subsection gives cautions when using JP1/AJS3 for x86 in the Windows-on-Windows 64 (hereafter, WOW64) environments^#1 of Windows Server 2012, 64-bit versions of Windows Server 2008, or Windows Server 2003 x64 Editions.

When a 32-bit application is executed in a WOW64 environment, calls to the file system are redirected from %systemroot%\system32^#2 to %systemroot%\syswow64, and access requests to the registries HKEY_LOCAL_MACHINE\Software and HKEY_CLASS_ROOT are redirected to HKEY_LOCAL_MACHINE\Software\SysWow64 or elsewhere. That is, the operating system isolates 32-bit applications from 64-bit applications, and prevents file and registry collisions.

Because JP1/AJS3 for x86 environments is a 32-bit application, calls are redirected as described above. This could result in any of the problems listed in the table below. To avoid such problems, do not specify any files under %systemroot%\system32 as files to be referenced or updated by JP1/AJS3.

#1: Also includes Windows 8.1, Windows 8, Windows 7 and Windows Vista on a JP1/AJS3 - View host.
#2: %systemroot% is an environment variable that points to the directory in which the Windows system is installed. The default setting is C:\WINDOWS.

Table 9‒2: Potential JP1/AJS3 problems in a WOW64 environment
Affected functionality	Problem
PC job^#1 or QUEUE job that runs under Windows	When a file under `%systemroot%\system32` is specified as the executable file for a PC job or for a QUEUE job that runs under Windows, the file access is actually redirected to a path under `%systemroot%\syswow64`. As a result, the job fails to start, or ends abnormally. For a PC job, the following problems might occur: Problem 1 The following message is output to the integrated trace log, and the job fails to start: KAVU4550-W The execution file (`file-name`) is missing at the agent `(agent-host-name)`. This message might appear, for example, when the backup utility in the system tools (`ntbackup`) is executed. Problem 2 The following message is output to the Windows event log, and the job ends abnormally with return code 128: This application has failed to start because netman.dll was not found. This message might appear, for example, when the `ipconfig` command in the system tools is executed.
`jp1exec` command	When an executable file under `%systemroot%\system32` is specified in the `jp1exec` command, the command fails to start and the job that executed the command ends abnormally.
Mail system linkage function	When the mail system linkage function is enabled for Outlook 2007 or an earlier version, the communication process for monitoring for email messages ends abnormally when the JP1/AJS3 service starts. A Receive Mail job executed at this time will also end abnormally.^#2
JP1/AJS3 - View tool execution	When an executable file under `%systemroot%\system32` is registered with the command for starting a JP1/AJS3 - View tool, the command fails to start the tool.^#3
Monitoring Files job	When a file under `%systemroot%\system32` is specified as the file to be monitored^#3, the file access is actually redirected to a path under `%systemroot%\syswow64`. Updates to the file under `%systemroot%\system32` remain undetected and the job remains in running state.
Monitoring Log Files job	When a log file under `%systemroot%\system32` is specified as the log file to be monitored^#3, the log file access is actually redirected to a path under `%systemroot%\syswow64`. Updates to the log file under `%systemroot%\system32` remain undetected and the job remains in running state.
Judgment job	When a file under `%systemroot%\system32` is specified as the judgment condition, the file access is actually redirected to a path under `%systemroot%\syswow64` and cannot determine whether the file is present in `%systemroot%\system32`. Consequently, dependent units are not executed.
Standard input file for a PC job	When a file under `%systemroot%\system32` is specified as the standard input file for a PC job, the file access is redirected to a path under `%systemroot%\syswow64`. Because it cannot find the standard input file, the job fails to start.
Standard output file for a PC job	When a file under `%systemroot%\system32` is specified as the standard output file for a PC job, the file access is redirected to a path under `%systemroot%\syswow64`. The PC job started from JP1/AJS3 can reference and update the standard output file if it is a 32-bit application, but not if it is a 64-bit application.
Standard error output file for a PC job	When a file under `%systemroot%\system32` is specified as the standard error output file for a PC job, the file access is redirected to a path under `%systemroot%\syswow64`. The PC job started from JP1/AJS3 can reference and update the standard error output file if it is a 32-bit application, but not if it is a 64-bit application.
Transfer file for a PC job	When a file under `%systemroot%\system32` is specified as the transfer source file for a PC job, the file access is redirected to a path under `%systemroot%\syswow64`. Because it cannot find the transfer source file, the job fails to start. When a file under `%systemroot%\system32` is specified as the transfer destination file for a PC job, the file access is redirected to a path under `%systemroot%\syswow64`. The PC job started from JP1/AJS3 can reference and update the transfer destination file if it is a 32-bit application, but not if it is a 64-bit application.
Command	When a file under `%systemroot%\system32` is specified as the file to be used for the command input or output, the I/O file access is redirected to a path under `%systemroot%\syswow64` and cannot reference or update the specified file.
Environment settings	When a file under `%systemroot%\system32` is specified in the environment settings, the file access is redirected to a path under `%systemroot%\syswow64` and cannot reference or update the specified file.

#1

Includes PC jobs for which Queueless Agent is specified as the execution service.

#2

In a WOW64 environment, you can run the 32-bit version of Outlook 2010 to use the mail system linkage function.

For details about the prerequisite programs for the mail system linkage function and the OS, see 2.3.1 Prerequisite programs for linking mail systems in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

#3

In the Files dialog box, you cannot specify a file under %systemroot%\system32.

An alternative means of avoiding problems in a PC job, QUEUE job that runs under Windows, or jp1exec command is to temporarily disable file system redirection when JP1/AJS3 starts a job. This allows 64-bit applications under %systemroot%\system32 to start successfully. For details about the setting to disable redirection, 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.

To Page Top