ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Executing a Windows job results in U02001040 Error in function 'LogonUser', error code '1909'

book

Article ID: 88216

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The below errors are produced when executing a Windows Job: 
 
20170629/083019.561 - U02000005 Job 'JOBS.XXX' with RunID '123456789' started. 
20170629/083019.592 - U02001040 Error in function 'LogonUser', error code '1909', error description: 'The referenced account is currently locked out and may not be logged on to.'. 
20170629/083019.592 - U02001000 Job 'JOBS.XXX' could not be started. Error code '1909', error description: 'The referenced account is currently locked out and may not be logged on to.'. 

This error indicates the user account contained within the LOGIN object for this job on this windows machine is locked.

Environment

OS: Windows

Resolution

A Windows Administrator should review the account located within the LOGIN object of the Job giving the above error and unlock the account.

An account lock can result from too many attempts to log in with bad credentials, an administrator manually locking in the account, or even a set expiration date for the account being triggered.

If the account is not locked and you are still receiving this error message a Windows Administrator should review the Windows event log of the machine which the agent is installed. They may find an error of NULL SID event 4625 within the Windows event log in which case the Windows Administrator may be experiencing the below Windows related issue:

NULL SID Security Log Event ID 4625 when attempting
logon to 2008 R2 Remote Desktop Session Host