Applicable versions and levels
Windows versions: V13.2.0 or later
Action 1
Points to check
Is a file on the network being used for the job?
Cause
A local system account has been set as the startup account of the "Systemwalker MpMjes" service.
Local system accounts do not have network connection rights.
Action method
For the effective user of the job, specify an account that can access the network.(In this case, select Execute jobs under the respective job owner's authority in the Options tab of the Define Operating Information window, which will be displayed when Operation information is clicked in the Systemwalker Operation Manager Environment Setup window.)
Alternatively, change the startup account of the "Systemwalker MpMjes" service to an account that can access the network. Refer to "Changing the Startup Account" in the Systemwalker Operation Manager Installation Guide for information on these changes.
Applicable versions and levels
Windows versions: V5.0L10 to V13.3.1
Action 2
Points to check
Can the resource (for example, file) used by the job be accessed?
For example, when the access to the directory or file fails, does the job end abnormally with a code set by the job or is an error message output?
Cause
If a resource that is required to execute the job cannot be accessed, the job does not operate normally. If the default definition information is used immediately after the installation, the job is executed with the logon account rights of the "Systemwalker MpMjes" service. For this reason, if the job does not operate normally, the cause of the problem may be that a resource required to execute the job cannot be accessed using the logon account of the "Systemwalker MpMjes" service.
Action method
To make the job operate normally, take one of the following actions:
Set appropriate rights for the account or resource, so that the resource required to execute the job can be accessed using the logon account of the "Systemwalker MpMjes" service.
Use any user account that can access the resource required to execute the job as the job startup account.
The procedure that is required to perform the action in b. is as follows:
Select Execute jobs under the respective job owner's authority in the Options tab of the Define Operating Information window, which will be displayed when Operation information is clicked in the Systemwalker Operation Manager Environment Setup window.
When the Define Operating Information window is closed, the Set Startup Mode of Job Execution Control dialog box will be displayed. Select Enable the saved operating information definitions from the next startup. (in versions of V10.0L21 or earlier), and then click OK.
From the Control subject box in the Systemwalker Operation Manager Environment Setup window, select Job Execution Control, and then click Start to restart the same service (the Jobscheduler service is also restarted).
Register the job owner set for the project (Jobscheduler definition item) or job folder (Job Execution Control definition item) in the Define Job Owner's Information Window, which will be displayed when Job owner is clicked in the Systemwalker Operation Manager Environment Setup window.
Using Control Panel >> Administrative Tools >> Local Security Policy, grant the "Log on as a batch job" right to the account used as the job startup account.
