The following section shows the event log messages that should be monitored, their causes, and the action to be taken.
1001 <Error> <R, S, C>
An error occurred while the execution request was received from Server.
- Cause
- It is possible that the system is unstable due to a memory shortage.
- Action
- Relay manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- After resolving the memory shortage problem, use the client manager to restart the client.
1002 <Error> <R, S, C>
TCP/IP (Windows Sockets Interface) error occurred. xx/yy
- Cause
- Either the network environment is invalid or it is possible that a communication failure occurred.
- xx: Name of the function in which the error occurred
- yy: Socket error code
- Action
- Relay manager
- After resolving the network environment or communication setting problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- After resolving the network environment or communication settings problem, use the client manager to restart the client.
1003 <Error> <R, S, C>
An error occurred on WinSockAPI. Cause of error: xx Additional information: yy
- Cause
- Either the network environment is invalid or it is possible that a communication failure occurred.
- xx: Socket error code
- yy: Name of the function in which the error occurred
- Action
- Relay manager
- After resolving the network environment or communication setting problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- After resolving the network environment or communication settings problem, use the client manager to restart the client.
5012 <Error> <R, S, C>
An error occurred in the following process. Cause of error: xx Additional information: yy
- Cause
- An error occurred during installation of a package.
- xx: C language runtime error or Win32 API error code
- yy: Name of the function in which the error occurred
- Action
- Based on the error code and the name of the function in which the error occurred, resolve the error, and then rerun the job.
6001 <Error> <R, S, C>
An error occurred in the following process. Cause of error: xx Additional information: yy
- Cause
- An error occurred during packaging.
- xx: C language runtime error or Win32 API error code
- yy: Name of the function in which the error occurred
- Action
- Based on the error code and the name of the function in which the error occurred, resolve the error, and then rerun the job.
7004 <Error> <R, S, C>
An error occurred while instructions information was referred from Server.
(File system of Windows NT may be invalid.)
- Cause
- Either the file is corrupt or a disk failure has occurred.
- Action
- Relay manager
- Run Scan Disk. After resolving the file or disk problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- Run Scan Disk. After resolving the file or disk problem, use the client manager to restart the client.
7009 <Error> <R, S, C>
Though the processing request was received from Server, Remote Installer could not start.
- Cause
- It is possible that the system is unstable due to a memory shortage.
- Action
- Relay manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- After resolving the memory shortage problem, use the client manager to restart the client.
7014 <Error> <R, S, C>
An error occurred in program. Cause of error: xx, Additional information: yy
- Cause
- An error occurred during the registration of packaging.
- xx: C language runtime error or Win32 API error code
- yy: Name of the function in which the error occurred
- Action
- Based on the error code and the name of the function in which the error occurred, resolve the error, and then rerun the packaging.
7018 <Error> <R, S, C>
Own host name cannot be acquired. The range of own host name is outside the valid range
- Cause
- The local host name is coded in 65 or more characters.
- Action
- Code the local host name in 64 or fewer characters.
8001 <Error> <R, S>
Memory shortage occurred in the relay system.
- Cause
- It is possible that the system is unstable due to a memory shortage.
- Action
- Relay manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
8023 <Error> <R, S>
The higher system cannot be connected because that is old version. (hostname:xx)
- Cause
- The version of the higher system is potentially too old.
- xx: Host name or IP address of the source or connection destination, specified in setup, of the job execution request.
- Action
- Check the version of the higher system. If the version is too old, upgrade the higher system.
8024 <Error> <R, S>
No Free Space to download the package.
- Cause
- Insufficient free space on the hard disk.
- Action
- Allocate enough free space on the hard disk, and then rerun the job. For details about hard disk space requirements, see 5.3.3 Disk space requirements in the manual Description and Planning Guide.
8025 <Error> <R, S>
No Free Space to download the script file.
- Cause
- Insufficient free space on the hard disk.
- Action
- Allocate enough free space on the hard disk, and then rerun the job. For details about hard disk space requirements, see 5.3.3 Disk space requirements in the manual Description and Planning Guide.
8026 <Error> <R, S>
No free space in package directory to store the package.
- Cause
- Insufficient free space on the hard disk
- Action
- Allocate enough free space on the hard disk, and then rerun the job. For details about hard disk space requirements, see 5.3.3 Disk space requirements in the manual Description and Planning Guide.
8050 <Error> <S>
ID-Job received from xx but yy is valid server.
- Cause
- The connection destination is specified incorrectly.
- xx: Host name or IP address of the connection destination specified in the setup
- yy: Host name or IP address of the higher system that executed the editing of the ID.
- Action
- On the Connection Destination page of the Relay System Setup dialog box, check the settings for the higher system. For details about the Connection Destination page, see 5.2.1 Connection Destination page in the manual Setup Guide.
10000 <Error> <M, R>
RDBMS is connected up to the maximum connection.
- Cause
- There are not enough user connections that can simultaneously connect to the relational database.
- Action
- Check user connections settings if Microsoft SQL Server is used as a relational database server, or process settings for Oracle, and increase the number of user connections that can connect simultaneously to the relational database.
10008 <Error> <M, R>
Database format unmatched.
- Cause
- The version of the relational database does not match that of JP1/Software Distribution.
- Action
- Use Database Manager to upgrade the relational database.
10009 <Error> <M, R>
Login to RDBMS failed.
- Cause
- The settings for using the relational database are incorrect.
- xx: Type of relational database being used
- NETM_MSSQL: Microsoft SQL Server
- NETM_ORACLE: Oracle
- Action
- Check the settings in the Database Environment page settings of the Server Setup dialog box. For details about the Database Environment page, see 4.2.1(2) Database Environment page (for Microsoft SQL Server or Oracle) in the manual Setup Guide.
10010 <Error> <M, R>
DataSourceName is invalid.
- Cause
- The name of the relational database is invalid.
- xx: Type of relational database being used
- NETM_MSSQL: Microsoft SQL Server
- NETM_ORACLE: Oracle
- Action
- Check the settings in the Database Environment page settings of the Server Setup dialog box. For details about the Database Environment page, see 4.2.1(2) Database Environment page (for Microsoft SQL Server or Oracle) in the manual Setup Guide.
10011 <Error> <M, R>
An access error to RDBMS, because transaction log full.
- Cause
- Not enough free space in the transaction log for the relational database.
- Action
- Allocate enough free transaction log area for the relational database.
10012 <Error> <M, R>
An access error to RDBMS, because capacity of database over.
- Cause
- Not enough free area for the relational database.
- Action
- Allocate enough free area for the relational database.
11006 <Error> <M, R, S>
While starting the Software Distribution server, a memory shortage had occurred.
- Cause
- It is possible that the system is unstable due to a memory shortage.
- Action
- Manager or relay manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
11020 <Error> <M, R, S>
Setting of an operation environment is improper.
- Cause
- It is possible that JP1/Software Distribution settings are incorrect.
- Action
- Manager or relay manager
- Check the settings in the Server Customization page settings of the Server Setup dialog box. For details about the Server Customization page, see 4.2.4 Server Customization page in the manual Setup Guide.
- Relay system
- Check the settings for the Relay system customization page in the Relay System Setup dialog box. For details about the Relay system customization page, see 5.2.4 Relay System Customization page in the manual Setup Guide.
11022 <Error> <M, R, S>
Resource hangar is destroyed.
- Cause
- It is possible that the package storage directory for JP1/Software Distribution is corrupt.
- Action
- In the Maintenance Wizard, select Revise to re-install JP1/Software Distribution Service, which will repair and initialize the package storage directory. For details about the Maintenance Wizard, see 1.3 Changing installation settings in the manual Setup Guide.
12013 <Error> <M, S>
Environment for the resource management file access server is destroyed.
- Cause
- It is possible that the cabinet information storage directory for JP1/Software Distribution is corrupt.
- Action
- In the Maintenance Wizard, select Revise to re-install JP1/Software Distribution Service, which will repair and initialize the cabinet information storage directory. For details about the Maintenance Wizard, see 1.3 Changing installation settings in the manual Setup Guide.
12014 <Error> <M, S>
Environment for the resource attribute file access server is destroyed.
- Cause
- It is possible that the package information storage directory for JP1/Software Distribution Manager is corrupt.
- Action
- In the Maintenance Wizard, select Revise to re-install JP1/Software Distribution Service, which will repair and initialize the package information storage directory. For details about the Maintenance Wizard, see 1.3 Changing installation settings in the manual Setup Guide.
12015 <Error> <M, S>
Environment for the execution management file access server is destroyed.
- Cause
- It is possible that the job detail information storage directory for JP1/Software Distribution is corrupt.
- Action
- In the Maintenance Wizard, select Revise to re-install JP1/Software Distribution Service, which will repair and initialize the job detail information storage directory. For details about the Maintenance Wizard, see 1.3 Changing installation settings in the manual Setup Guide.
12016 <Error> <M, S>
Environment for the resource state file access server is destroyed.
- Cause
- It is possible that the installation package information storage directory for JP1/Software Distribution is corrupt.
- Action
- In the Maintenance Wizard, select Revise to re-install JP1/Software Distribution Service, which will repair and initialize the installation package information storage directory. For details about the Maintenance Wizard, see 1.3 Changing installation settings in the manual Setup Guide.
12017 <Error> <M, S>
It failed in generation of an environment that a resource management file access server operates.
- Cause
- It is possible that the system is unstable due to memory shortage.
- Action
- Manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
12018 <Error> <M, S>
Generation of an environment for the resource attribute file access server failed.
- Cause
- It is possible that the system is unstable due to memory shortage.
- Action
- Manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
12019 <Error> <M, S>
Generation of an environment for the execution management file access server failed.
- Cause
- It is possible that the system is unstable due to memory shortage.
- Action
- Manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
12020 <Error> <M, S>
Generation of an environment for the resource state file access server failed.
- Cause
- It is possible that the system is unstable due to memory shortage.
- Action
- Manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
14004 <Error> <M, R, S>
System error occurred during start.
- Cause
- It is possible that the system is unstable due to memory shortage.
- Action
- Manager or relay manager
- After resolving the memory shortage problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system
- After resolving the memory shortage problem, use the client manager to restart the client.
14037 <Error> <M, R>
Process of Software Distribution Manager was down.
- Cause
- JP1/Software Distribution detected an error. It is possible that a service (Remote Installer Server) for JP1/Software Distribution Manager is stopped.
- Action
- From Control Panel, choose Administrative Tools, and then Services to check the status of Remote Install Server. If it is Start or Pause, restart Remote Install Server. If no status is shown (not running), start Remote Install Server.
14038 <Error> <S>
Process of Software Distribution SubManager was down.
- Cause
- JP1/Software Distribution detected an error. It is possible that a service (Client Install Service) for JP1/Software Distribution Client (relay system) is down.
- Action
- Use the client manager to check the client's status. If the status is Running, restart the client. If it is Terminated, or Starting or terminating, or Non-resident, start the client. For details about how to start a non-resident client, see 11.1.2(2) Making a client non-resident in the manual Administrator's Guide Volume 1.
16016 <Error> <M, R>
The operation history storage directory cannot be accessed.
- Cause
- It is possible that the file is corrupt or there is a disk failure.
- Action
- Run Scan Disk. After resolving the file or disk problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
16017 <Error> <M, R>
The operation history backup directory cannot be accessed.
- Cause
- It is possible that the file is corrupt or there is a disk failure.
- Action
- Run Scan Disk. After resolving the file or disk problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
16018 <Error> <M, R>
The operation history cannot be saved because the space is insufficient in the history storage directory.
- Cause
- Insufficient free space on the hard disk.
- Action
- Allocate enough free space on the hard disk, and then rerun the job. For details about hard disk space requirements, see 5.3.3 Disk space requirements in the manual Description and Planning Guide.
16019 <Error> <M, R>
The operation history cannot be backed up because the space is insufficient in the operation history backup directory.
- Cause
- Insufficient free space on the hard disk.
- Action
- Allocate enough free space on the hard disk. For details about hard disk space requirements, see 5.3.3 Disk space requirements in the manual Description and Planning Guide.
16020 <Error> <M, R>
The space in the operation history backup directory has reached the threshold value.
- Cause
- The available space in the operation history backup directory has reached the threshold value that was specified in the setup.
- Action
- From Control Panel, choose Administrative Tools, and then Services to terminate the JP1/Software Distribution Manager service (Remote Install Server), and back up everything under the operation history backup directory specified in the setup. After making a backup, delete everything under the backup directory to allocate enough space, and then start the service (Remote Install Server) for JP1/Software Distribution Manager.
16023 <Error> <M, R>
Processing for storing operation monitoring history in the database resulted in a system error.
- Cause
- JP1/Software Distribution detected an error when operation monitoring history was to be stored in the database.
- Action
- See 6.7 Collecting maintenance data, collect the data required for determining the cause of the error, then contact the support service or distributor.
16024 <Error> <M, R>
Processing for storing operation monitoring history in the database resulted in an RDB access error.
- Cause
- JP1/Software Distribution detected an error when operation monitoring history was to be stored in the database.
- Action
- See 6.7 Collecting maintenance data, collect the data required for determining the cause of the error, then contact the support service or distributor.
16030 <Error> <M, R>
An attempt to connect to the network drive has failed during the access to the operation log.:xx
- Cause
- There may be an error in the authentication information settings or in the connection path to the network drive.
- Action
- Specify a valid login ID, password, and domain name in the Network Connection panel of Manager Setup.
- Also check the connection path to the network drive. If the connection path to the operation history storage directory is incorrect, perform an overwrite installation, and specify the correct path in the Software Operation History Storage Directory Settings dialog box. If the operation history backup directory is incorrect, specify the correct path on the Operation Monitoring page.
16031 <Warning> <M, R>
Store the operation monitoring history that has not yet been stored to the database by executing the dcmmonrst command with the option "/x".
- Cause
- The operation history storage directory contains an operation history file, whose file is 20 MB or greater that has not yet been stored in the database.
- Action
- Execute the dcmmonrst command with /x specified in the argument to store the operation history in the database.
20000 <Error> <R, S, C>
An error occurred in the following process. Cause of error: xx Additional information: yy
- Cause
- Either the network environment is invalid or it is possible that a communication failure occurred.
- xx: Socket error code
- yy: Name of the function in which the error occurred
- Action
- Relay manager
- After resolving the network environment or communication setting problem, use Services to restart the server (Remote Install Server) for JP1/Software Distribution Manager (from Control Panel, choose Administrative Tools, and then Services).
- Relay system or client
- After resolving the network environment or communication settings problem, use the client manager to restart the client.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)