Hitachi

JP1 Version 12 JP1/Client Process Automation Messages


KNAO0525-E

Failed to start the job because logon failed. (os-user-name, job-name, job-execution-ID, maintenance-information-1, maintenance-information-2)

The job failed to start as the OS user.

(S)

Discontinues the requested processing.

(O)

The maintenance information 2 contains values collected by using the GetLastError function of Win32API.

Understand what the error code means and take appropriate action.

The following shows the frequent causes for, and how to respond to, reason numbers in maintenance-information-2.

Reason number: 1311

If a domain user is specified as the job execution user, the status of the domain controller might have caused the error. The domain user must be able to log on to the system because it refers to the user account. CPA is not aware of the number and statuses of the domain controllers during its operation. Use care if you restart the domain controller while a job is running.

Reason number: 1326

An access token for the OS user who executes the job might not be obtained. Ensure the following:

  • The OS user name and the password are correct.

  • If a domain user is specified as the job execution user, the status of the domain controller might have caused the error. The domain user must be able to log on to the system because it refers to the user account. CPA is not aware of the number and statuses of the domain controllers during its operation. Use care if you restart the domain controller while a job is running.

  • An access token might not be obtained due to a temporary error of a Win32API function.

Reason number: 1330

Check that the password of the user has not expired.

Reason number: 1792

Check that the Net Logon service has been up and running.

Reason number: 1909

The account of the OS user who executes the job might be locked out. Check whether invalid passwords were entered for the OS user who executed the job.

If the account is locked out, unlock the account.

For details on how to unlock the account, see Microsoft websites.

If the problem persists, collect appropriate data and then contact the system administrator.