Job fails with error "598 Error getting osuser"

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

A Job may Abort or go into Launch Error due to the error "598 Error getting osuser". This is seen in the Job's output file. 

Below is and example of the error:

===== OUTPUT INFORMATION ===========================================
user           amuser
printer        TEST
copies         1
function       STORE
output req     N
log run        Y

===== LOGIN INFORMATION ============================================
dbtype         
login          
netconnect     
dbtype2        
db_login2      
net_connect2   
sid            

parameter file
5
End of parameter file
job pid 15357
598 Error getting osuser
Error on command: awexe UPD_JQ so_jobid=17413969.00 so_status=31 so_job_pid=15357 so_seq_no=3073195.
Checking to see if awapi is working
Awapi not working.
Retry failed.
awexe UPD_JQ so_jobid=17413969.00 so_status=31 so_job_pid=15357 so_seq_no=3073195
Error 1 setting job to RUNNING status

Environment

Release : 9.x

Component : CA Automic Applications Manager (AM)

Cause

Applications Manager is unable to verify/find the OS user in /etc/passwd.

During the Job run process, the Job runs a function getpwuid, which will relies on /etc/passwd. Applications Manager expects to find the OS user listed for the Job in the /etc/passwd file.

Resolution

1. Confirm if the OS user listed for the Job, exist locally on Agent machine. The OS user should exist in the /etc/passwd file.

2. If the OS user does not exist in /etc/passwd because the OS User is an LDAP User, refer to the LDAP admin to review the OS user authentication process.
There may be an issue in the authentication process or a setting change is required to allow Applications Manager to validate against the LDAP OS User.