14.3.2 Actions to be taken if normal operation is disabled
While you are using JP1/IT Desktop Management 2 - Manager, normal operation might be disabled or an error might occur. The following describes possible problems and actions to be taken:
- Organization of this subsection
(1) Job execution does not proceed
If the job execution does not proceed, the possible reasons are as follows:
(a) The local host name of the agent does not match the destination specified on the managing server
If the agent name is different from the name specified for the system configuration or destination of the managing server, remote installation does not terminate. Confirm that the agent name is correct.
(b) Destinations with the same name and different host IDs exist
If agents with the same name exist, the job might not terminate because a different destination is specified for the job.
In this case, execute the resetnid command on the agents that have the same name. For details about this command, see 6.1.6 Example of manual maintenance of system configuration information.
(c) The user has not logged on to the computer
Even if the computer is running, a job in GUI installation mode is not executed unless the user has logged on.
(d) An external program monitoring time is not set
If an external program monitoring time is not set, the job waits endlessly because control does not return from the external starting program. Set the external program monitoring time on the External Program page in the JP1/ITDM2 Packaging dialog box.
(e) Settings in the information file for higher connection destinations are not correct
If the settings in the information file for higher connection destinations are not correct, job results cannot be reported because JP1/IT Desktop Management 2 - Agent cannot connect to a higher server. Check and, if necessary, revise the information file for higher connection destinations.
(f) ITDM-compatible distribution is being performed on an agent
A job cannot be executed at the same time with ITDM-compatible distribution on an agent. Therefore, if ITDM-compatible distribution is being performed on the agent, the status of the job might remain as Waiting for transmission.
(g) Processing after remote installation or processing of an AIT file does not terminate normally
If processing after remote installation or AIT file processing does not terminate normally, installation on the agent is placed in the endless wait state.
If remote installation does not complete, RegisterWindowMessage might not have been issued when the AIT file processing ended.
(h) A user program started before or after installation has not terminated
If installation has completed on the agent but the job progress indicates 70% on the managing server, it is assumed that a user program, started before or after installation, has not terminated yet.
(2) A job fails
If a remote installation job causes an error, the cause of the error is displayed as a maintenance code. In the Job Status window, open the Detailed Information dialog box to check the maintenance code.
(3) The relay system contains a job but does not contain a package
Packages stored in the relay system are automatically deleted when a certain period of time has passed. If you do not specify the expiration date during packaging or job creation, a package is deleted the next day of the remote installation. Even if you specify the expiration date, the package is deleted if the next day of the remote installation is a holiday or if the agent has not been turned on for several days. This results in a situation where the relay system contains a job but does not contain a package.
To prevent such a problem, specify the expiration date of a package with due consideration during packaging or job creation. However, specifying an expiration date that is too long causes memory compression.
The following maintenance code is displayed.
Maintenance code: 300097030000