Applicable versions and levels
Windows versions: V5.0L10 or later
Check all applicable actions below to resolve the issue.
Action 1
Points to check
Has an application that involves window output been started as a job?
Cause
If a job does not end, it may have been started as an application that involves window output.
Action method
Applications that involve window output cannot be executed as jobs (except when the Task Link client application startup commands are used).
If the application outputs a pop-up to the window, take action so that this is not output. Additionally, use the Task Link client application startup commands to execute an application that involves window output.
If the problem is reproduced, check the application status according to the confirmation procedure in "5.4.5 The Job Does Not End (1)".
Action 2
Points to check
Has a print application been started as a job?
Cause
If a print application does not have a printer set as a print destination, and the default printer of the Windows operating system is set as the print destination, the job may end with nothing printed, or the job may not end.
Action method
By taking the following actions, it may be possible to print normally.
Use the print application to use a printer other than the printer set as the default printer.
Before starting the print application from Systemwalker Operation Manager, log on to Windows locally using the "Systemwalker MpMjes" service logon account. (If Execute jobs under the respective job owner's authority is selected in the Options tab of the Define Operating Information window, log on to Windows locally using the job owner account.)
