Applicable versions and levels
Windows versions: V5.0L10 or later
Action
Points to check
Can the registered job be operated using the rights of the service startup account (the default value is the "systemwalker" local account) specified when Systemwalker was installed?
Cause
In the Windows versions Systemwalker Operation Manager, normally the job operates using the rights of the "Systemwalker MpMjes" service. The job may not operate normally because the service startup account has insufficient rights.
Action method
Use one of the following actions to assign sufficient rights to start the job:
Prepare the job operating environment so that the job can operate using the rights of the service startup account (the default value is the "systemwalker" local account)
Change the "Systemwalker MpMjes" service startup account to an account that can execute jobs. (*1)
Configure the settings so that the job is executed with job owner rights. (*2)
*1: When changing the service startup account, do not forget to configure the advanced user rights for the account. The setting can be configured in the following windows:
Windows NT(R): User Manager
Windows(R) 2000/Windows Server 2003 STD/Windows Server 2003 DTC/Windows Server 2003 EE/Windows Server 2008 or later: Local Security Policy, or Domain Security Policy
The required rights are as follows:
Log on as a service
Act as part of the operating system
Increase quotas or Adjust memory quotas for a process (depending on the operating system)
Replace a process level token
Additionally, the user must belong to the Administrators group on the local computer, and "Password never expires" must be set.
*2: Refer to the action method in "5.2.11 The Job Ends Abnormally with Code 0x40000913 [Windows versions]" for information on the procedure to execute a job with owner rights.
Information
Review whether the "Systemwalker MpMjes" service startup account that executes the job is a user that has rights to execute jobs. It may not be possible to start jobs (the operating environment is not prepared) if the user has not installed the application or has never logged in to the desktop.
