The table below shows the cause of principal maintenance codes that are returned from ordinary installation jobs, and procedures for resolving the problems.

If the destination is a UNIX client, a value other than 00 is displayed as the user status even when the external program processing is successful and the remote installation job ends normally. However, this does not indicate a problem and can be ignored.

Table 6-1 Remote installation maintenance codes

Maintenance code	Cause	Action
300092020000	Large software was remotely installed; the client is unable to allocate the disk space necessary for installation and work space.	See 5.3.3 Disk space requirements in the manual Description and Planning Guide. Calculate the hard-disk space required on the client during the remote installation. If the remote installation is on a PC that does not have adequate hard-disk space, delete any unneeded files before proceeding. Install the JP1/Software Distribution Client only on a drive that has adequate free space.
300093010000	The package to be installed remotely is not supported by the client.	Upgrade the client to a version that supports the package to be installed remotely.
300097010000	Files to be remotely installed cannot be created for the following reasons: A file to be remotely installed is being used. A duplicate name directory exists. The user does not have access permission for the files. The software was distributed to a client that does not support high-compression packages.	Resolve the cause indicated in reasons 1 through 3. If the client executes an Install when system starts remote installation on a program that is registered in the Startup group, the installation fails due to reason 1. In this case, move any programs that have started since the startup time to Software Distribution Client Startup; the system starts the program after executing the installation processing. For details about how to move the NETM_DM_P Startup folder, see 11.2.2(2) Moving startup programs in the manual Administrator's Guide Volume 1. For reason 4, distribute any high-compression packages after packaging them in a compatible compression mode.
3000980Exx00#	The pre-processing program failed to start.	None.
3000980F0000	The external program monitoring timed out without a response from the pre-processing program.	Check the pre-processing program. Make sure that external program monitoring time is set to an appropriate value.
30009A01xx00#	The post-processing program failed to start.	When xx is 00, check the path of the external program. When xx is other than 00, check the user status.
30009A060000	The external program monitoring timed out without a response from the post-processing program.	Check the post-processing program. Make sure that external program monitoring time is set to an appropriate value.
30009F090000	The power for the client PC was turned off during the downloading or installation of the package; the installation of the package failed.	None.
900090009000	Even if the installation has not been executed, the managing server is notified that the installation process ended. The same software as the remotely installed software is already installed on the client system. The file was not created after the installation was completed. The data remote-installed on the client system was deleted.	When creating a job, specify Replace existing package to install an identical package to that which may exist in the remote installation destination. The existing package is overwritten.

#: xx denotes a return code from the pre- or post-processing program.

Tables 6-2 and 6-3 show maintenance codes, their meanings, and actions to be taken when JP1/Software Distribution Client, or other Hitachi program products are installed remotely.

The xx part of the maintenance code that is returned in the 3000AF00xx00 format is a job result return code. A return code also is displayed on the client screen upon termination of the remote installation of JP1/Software Distribution Client (client).

Table 6-2 Maintenance codes from remote installation of JP1/Software Distribution Client

Maintenance code	Cause	Action
300077030000	A JP1/Software Distribution Client (client) that was not compatible with the destination OS was distributed; the installation failed.	Check the OS at the destination and the applicable OS for JP1/Software Distribution Client (client); remotely install the JP1/Software Distribution Client (client) that is compatible with the destination OS.
3000AF000000	Normal termination.	None.
3000AF008000	Analysis of installation setup file (setup.inf) failed.	Notify the system administrator.
3000AF008100	Installation file not found on the medium (no PP files).	Possibly invalid media. Notify the system administrator.
3000AF008200	Registration of icon failed (post-installation error).	The operating environment for JP1/Software Distribution may be invalid. Manually perform overwrite installation.
	Program folder for remote control agent missing.	The operating environment for JP1/Software Distribution may be invalid. Manually perform overwrite installation.
3000AF008300	Registration of registry for remote control agent failed.	The operating environment for JP1/Software Distribution may be invalid. Manually perform overwrite installation.
	Registration of permitted controller for remote control agent failed.	The operating environment for JP1/Software Distribution may be invalid. Manually perform overwrite installation.
	Installation directory in the registry missing.	The operating environment for JP1/Software Distribution may be invalid. Manually perform overwrite installation.
	Registration of a module required for searching for information about Microsoft Office and anti-virus products failed.	COM Object Save Command Failed is output to Windows-directory\Temp\DMPINST.LOG. Take one of the following actions: Re-install JP1/Software Distribution Client. Start the command prompt and execute the following command: REGSVR32.EXE "JP1/Software-Distribution-installation-directory\BIN\dmpComSW.dll".
3000AF008500	Error during file copy (disk-access error).	Make sure that the hard disk is operating normally. If the hard disk is operating normally, it is possible that the installation directory is being used. Either close all applications that are using the installation directory or reboot the PC.
3000AF008500	Creation of file copy directory failed during automated distribution of JP1/Software Distribution Client (client).	Make sure that the hard disk is operating normally. If the hard disk is operating normally, it is possible that the installation directory is being used. Either close all applications that are using the installation directory or reboot the PC.
3000AF008600	Insufficient free hard-disk space for installation directory.	Either rerun the remote installation after increasing the amount of free hard-disk space or rerun the remote installation by specifying another installation drive.
3000AF008600	Backup of execution file failed.	Rerun the remote installation after increasing the amount of free hard-disk space.
3000AF008700	Reading of installer DLL failed.	Notify the system administrator.
	Disk replacement requested during automated distribution of JP1/Software Distribution Client (client).	Notify the system administrator.
	Invalid disk number during automated distribution of JP1/Software Distribution Client (client).	Check the disk number and try packaging again.
	Error during decompression of installation file.	Notify the system administrator.
	Remote control agent failed to read installation DLL (file open error).	Notify the system administrator.
3000AF008B00	Error in integrated installer flag settings	Notify the system administrator.
3000AF008C00	JP1/Software Distribution Client (client) was installed on a computer on which one of the following relay system products was already installed: JP1/Software Distribution Client (relay system) JP1/Software Distribution SubManager Software Distribution SubManager Software Distribution Relay System Software Distribution/P-AF Groupmax Remote Installation Client Relay System	Take one of the following actions: Uninstall the relay system product Install JP1/Software Distribution Client (client) on a different PC
	JP1/Software Distribution Client (client) was installed on a computer on which Software Distribution Light was already installed.	Uninstall Software Distribution Light, or install JP1/Software Distribution Client (client) on a different computer.
	Integrated installer operation error	Notify the system administrator.
	Invalid OS version on installation destination (installation rejected).	Remote installation of JP1/Software Distribution Client may have been attempted on a system on which it cannot be installed. Check the OS version of the installation destination.
	Invalid installation destination OS in remote control agent.	Remote installation of JP1/Software Distribution Client may have been attempted on a system on which it cannot be installed. Check the OS version of the installation destination.
	JP1/Software Distribution Client (client) Remote Control Agent was installed on a PC on which JP1/Remote Control Agent or JP1/Software Distribution Manager Remote Control Agent was already installed.	Notify the system administrator.
3000AF009000	The installation component is invalid (it was installed remotely on a PC on which Client installation by Web was already installed).	If the JP1 Version 7i component Client Installation by Web is installed on the PC, install the installation component manually.
3000AF009200	JP1/Software Distribution Client (client) busy.	Re-try remote installation of JP1/Software Distribution Client (client).
3000AF009300	Hard disk-space shortage occurred during installation of JP1/Software Distribution Client from Web browser (installation from ActiveX-compatible page).	Delete any unneeded files; re-try the installation.
3000AF009400	Installation pre-processing error.	Notify the system administrator.
	Driver setting by remote control agent failed.	Notify the system administrator.
	Remote control agent failed to read the dialog box.	Notify the system administrator.
	Remote control agent service control error.	Notify the system administrator.
3000AF009500	Attempt was made to install JP1/Software Distribution Client (client) from Web browser. However, components other than a client or remote control agent are already installed.	Uninstall the non-client, non-remote control agent components.
	JP1/Software Distribution Client (client) was remotely installed on a PC on which JP1/Software Distribution Manager (relay manager) was already installed.	Uninstall JP1/Software Distribution Manager, or install JP1/Software Distribution Client (client) on a different PC.
	JP1/Software Distribution Client (relay system) was remotely installed on a PC on which JP1/Software Distribution Manager was already installed.	Uninstall JP1/Software Distribution Manager, or install JP1/Software Distribution Client (relay system) on a different PC.
3000AF009600	The transfer of management files from the relay system failed.	Re-execute remote installation.
3000AF009800	JP1/Software Distribution Client was remotely installed on a PC on which Startup Kit Support Tool was already installed.	If Startup Kit Support Tool is already installed on the PC, the installation should be performed manually.
	JP1/Software Distribution Client (relay system) was remotely installed on a PC on Differing Components Extractor was already installed.	If Differing Components Extractor is installed on the PC, install JP1/Software Distribution Client (relay system) manually.

Table 6-3 Maintenance codes from remote installation of other Hitachi program products

Code	Meaning	Action
300077030000	A Hitachi program product not compatible with the destination OS was distributed; the installation failed.	Check the destination OS and the applicable OS for the Hitachi program product. Remotely install a Hitachi program product compatible with the destination OS.
3000AF008000, 3000AF008100	The installation terminated abnormally.	Notify the system administrator.
3000AF008200	An external program error occurred after installation. Addition of an icon failed Addition of a group failed	Check to see that the path for the program to be executed after the packaging process is correctly specified. If the path is correct, it is possible that the program that was executed terminated abnormally.
3000AF008300	The installation terminated abnormally.	Notify the system administrator.
3000AF008400	Memory shortage during installation.	Close other programs to free memory, and retry.
3000AF008500	Hard disk access error occurred.	Confirm that the hard disk is operating normally. If the hard disk is OK, it is possible that the installation destination folder is busy, in which case close the application using the folder or reboot your PC.
3000AF008600	Not enough free space on the hard disk.	Make sure that the hard disk has enough free space, and then retry.
3000AF008700	The installation terminated abnormally.	Notify the system administrator.
3000AF008800	The startup parameter is invalid Example: Although an update installation was specified, the applicable program is not installed.	If the error situation is as explained in the example at the left, try installation again. In other cases, notify the system administrator.
3000AF008A00	The new PP cannot be reinstalled.	Since the old version is already installed on the distribution destination, try remote update installation again.
3000AF008B00	The installation terminated abnormally.	Notify the system administrator.
3000AF008C00	The installation was rejected Example: No prerequisite program found. No prerequisite programs are installed.	If the error situation is as explained in the example at the left, install the prerequisite program and then try installation again. In other cases, notify the system administrator.
3000AF008D00, 3000AF008E00, 3000AF008F00	The installation job terminated abnormally.	Notify the system administrator.
3000AF009000 to 3000AF009900, 3000AF009A00 to 3000AF009F00	The installation job terminated abnormally due to a Hitachi PP-specific reason.	Check the release notes or the README file for the program product whose installation failed. Alternatively, notify the system administrator for the affected program product.

The table below shows the maintenance codes that are returned from the remote installation of other companies' software, their causes, and actions to be taken.

Table 6-4 Maintenance codes from remote installation of other companies' software

Maintenance code	Cause	Action
300091070000	An error occurred during installation on the destination system. The following causes can be suspected: In the packaging, a recorder file is not specified in the recorder file specification field. Alternatively, the extension for the specified file is not recognizable. No recorder or AIT files are found. An attempt was made to remote-install a package using an AIT file on a client that does not support AIT files.	In the Software Distribution Packaging dialog box, open the Recorder File page, confirm that a recorder file is specified in the recorder file directory specification field, and execute the job. Note that file extensions vary depending upon the destination environment and the method of installation employed. Make sure that the destination system supports AIT files. Also, make sure that the package is not damaged.
300094060000	An error occurred during the copying of the installation definition file.	Check the amount of available disk space in the destination system. If the problem persists when the job is rerun, notify the system administrator.
300097020000	Destination system: a PC An error occurred during installation on the destination system. The following causes can be suspected: The path for the installer specified in the installation definition file in the recorder file is invalid. The path for the installer specified in package information in the AIT file is invalid. System error. Destination system: UNIX The installation password file is damaged.	Destination system: a PC Check the path for the installer specified in the installation definition file. Check the path for the installer specified in the package information in the AIT file. If the problem persists even after the preceding checks are made, notify the system administrator. Destination system: UNIX Register the installation password file, and then rerun the job.
30009F070000	An error occurred during installation on the destination system. The following causes can be suspected: Invalid installation destination directory Insufficient installation destination disk space An error during execution of the recorder file An error during execution of the AIT file Invalid version of the Visual Test or Automatic Installation Tool A distribution facility based on Visual Test is not installed on the destination system. The destination system does not support a distribution facility based on Visual Test. Windows Installer is not installed on the destination system.	Check the specification of the installation destination directory, the capacity of the distribution destination desk, and the directory. Check the execution results of the recorder or AIT file. The user status value in the maintenance code (the 9th and 10th digits from the left) contains a return code from the execution of the recorder or AIT file. Check the version of Visual Test by which the recorder file was created. Check the version of the Automatic Installation Tool by which the AIT file was created. Make sure that a distribution facility based on Visual Test is installed on the destination system. Make sure that Windows Installer is installed on the destination system.
30009F0B0000	During installation on the distribution system, the processing of the recorder or AIT file timed out. The following causes can be suspected: Invalid coding for the processing of the recorder or AIT file. During the distribution of software, the user on the client side manipulated the installer screen.	Check to see if the recorder file or AIT file monitoring time specified using Packager or the remote installer is adequate. After revising the recorder or AIT file, re-do the packaging. If the installation screen is active on the client side, close the screen, and then rerun the job.
300099020000	Distribution system: a PC An error occurred during execution of the installation script on the distribution system. The following causes can be suspected: Processing of the Setup() function failed. System error. Distribution system: UNIX An error during the include processing.	Distribution system: a PC Make sure that the system is operating in the GUI installation mode and that the contents of the recorder or AIT file do not have an error. If the problem persists even after the preceding checks are made, notify the system administrator. Distribution system: UNIX Investigate the cause of the problem by checking the log file for the distribution system.

The table below shows maintenance codes that are returned, their causes, and actions to be taken, when Search for Microsoft Office products and Search for anti-virus products in a Get software information from client job are executed.

Table 6-5 Maintenance codes from the execution of a get software information from client job

Maintenance code	Cause	Action
3000EF200000	An error occurred during the acquisition of software information on the distribution system. The following causes can be suspected: Memory shortage Disk I/O error	Delete any unneeded files on the distribution system and increase the available hard disk space. In addition, stop any applications that are not needed.
3000EF210000	A script execution error occurred for the acquisition of software information on the distribution system. The following causes can be suspected: Invalid script Invalid client installation status	If the same error occurs when other scripts are executed, re-install the client. If only this script produces an error, notify the system administrator.
3000EF220000	A disk space shortage occurred during the acquisition of software information on the distribution system.	Delete any unneeded files on the distribution system to increase the available hard disk space, and rerun the job.
3000EF230000	A memory shortage occurred during the acquisition of software information on the distribution system.	Stop any unneeded applications on the distribution system, and rerun the job.
3000EF240000	The processing of a script for the acquisition of software information timed out on the distribution system.	The script that was executed contains an error. Notify the system administrator.
3000EF250000	The execution of a script for the acquisition of software information failed on the distribution system. The Windows scripting host may not have been installed or may have been installed incorrectly.	Re-install the Windows scripting host on the distribution destination system. If this re-installation does not resolve the problem, re-install the client.
3000EF300000	Detection of patch information by Windows Update Agent or MBSA failed in the distribution-destination system. The following causes can be suspected: A required program is not installed. The job was executed by a user who did not have proper permissions. Workstation and Server services are down.	Confirm whether the required programs are installed. Re-run the job by enabling the following settings in the Client setup: If the client is resident, Run the client with non-Administrator user permissions If the client is non-resident Make sure that the Workstation and Server services are not down.

The table below shows maintenance codes that are returned, their causes, and actions to be taken, from a Transfer user inventory schema to client job.

Table 6-6 Maintenance codes from a transfer user inventory schema to client job

Maintenance code	Cause	Action
300073002290, 300093012290, 3000e5012290, 3000e7012290	The relay system or the client that is the target of the job does not support the execution of Transfer user inventory schema to client jobs.	Transfer user inventory schema to client jobs can be used in the versions indicated below. Make sure that the relay system or the client you are using is one of the following versions: Software Distribution SubManager Version 3.0 03-10 or later Software Distribution/Workstation Version 3.0 03-10 or later Software Distribution Client Version 3.0 03-10 or later

The table below shows maintenance codes that are returned, their causes, and actions to be taken, from a Set the software monitoring job.

Table 6-7 Maintenance codes from a Set the software monitoring job

Maintenance code	Cause	Action
300093010000	The relay system or the client that is the target of the job does not support the execution of Set the software monitoring jobs.	Set the software monitoring jobs can be used in the versions indicated below. Make sure that the relay system or the client you are using is one of the following versions: Software Distribution SubManager 07-50 or later Software Distribution Client 07-50 or later