Applicable versions and levels
Windows versions: V5.0L10 or later
Check all applicable actions below to resolve the issue.
Action1
Points to check
Is the job waiting for input?
Does the application output a message box when an error occurs?
Cause
When an error occurs, a message box may be output, and there may be a wait state for OK button input. Alternatively, an interactive command (such as edlin) or a command that makes an input request (such as format, backup, pause) may have been defined in the batch file.
Action method
Consider taking the following actions:
If a command or function that makes an input request is contained in the application, investigate if the application can be modified so that these commands or functions do not run.
If there is a possibility that the application stopped because it was in an input wait state when the error occurred, the job will not end, so consider configuring a setting to make the job end after a fixed period has elapsed.
For example, in Specify the time limit of job execution. of the Edit Queue window, consider setting a limit value to execute the job in a particular queue, so that jobs that run for a long time are treated as having ended abnormally.
To start an interactive job, also consider using the Task Link client application startup commands.
Information
Systemwalker Operation Manager jobs operate in environments in which the window cannot be seen (background), therefore the request to click OK remains unnoticed. For this reason, jobs that have fallen into an input wait state do not end.
Action 2
Points to check
Has a resident application been started?
Cause
The operating status of a job started from Systemwalker Operation Manager is monitored until the descendent processes of that job. Even if the structure of the job is that a resident process is started from the batch file, and the batch file ends, it does not mean that job has ended just because the batch file ends.
Action method
In Systemwalker Operation Manager, the job does not end until all processes started from the job, for example child processes, grandchild processes, and descendent processes, have ended.
If a batch that makes a request to start resident processes, for example, is started from Systemwalker Operation Manager, the job does not end. Consider performing operations with a prerequisite to have jobs that do not end or operations starting this type of application from other than Systemwalker Operation Manager.
Action 3
Points to check
Is the application in an infinite loop?
Cause
The job may have caused an unintended error, and as a result, it may be in an infinite loop caused by an abnormal route that is should not normally follow.
Action method
Check if the CPU time of the job has been increased by Task Manager, for example.
If the application that was started as the job is in an infinite loop, the cause cannot be investigated from the perspective of the Systemwalker Operation Manager behavior.
First, check if there is a problem in the operating environment. If there are no problems, debug from the perspective of the application behavior.
Action4
Points to check
Has conime.exe been started as a child process of the job?
Cause
If conime.exe (console IME) is not resident because of the operating system specification, and an application that requires conime.exe is executed, conime.exe is started as a child process. conime.exe is a resident process, therefore there is a possibility that the process remains, so the job does not end.
Action method
Refer to Microsoft Knowledge Base Article 814379, and then take appropriate action.
Perform the following types of actions:
Configure the registry settings so that conime.exe does not start.
Make conime.exe resident before starting the job.
Configure the settings so that the following type of batch file is executed when the system starts or when the logon occurs. (Register the batch file in Task Scheduler or Startup.)
Example batch file
REM Simulate sleep using ping.exe |
