I'm totally new to AutoSys and have been muddling my way around. I've managed to figure out that the job I sent to the AutoSys Server is failing and the Exit Code is -655. Can anyone please tell me what that means?
5 Answers
If you are bound to active directory for security then a 655 can mean
There are more security violations that can trigger this error. These are the most common. 655 is always some security related issue.
Please make sure that the below are working fine
autoping -m (machine name) - Autoping is successful
autorep -m (machine name) This should return as machine is Online
Per Appendix A of the Unicenter AutoSys Job Management for UNIX and Windows Reference Guide:
-655 (SYSTEM_ERROR) => STARTJOB failures because auto_remote will not start.
Somewhat helpful.
I got this error when the profile in the job does not match an existing profile. In my case, it was due to a typo.
Reference:
EXITCODE: -655 on Windows System Agent
Document ID : KB000006112 Last Modified Date : 14/02/2018 Show Technical Document Details
Issue:
We have installed a 11.3 System Agent successful on a Windows system. Autoping works fine. User and password are defined within autosys_secure.
Test job is submitted and ends with exitcode -655.
[03/08/2017 10:06:53] CAUAJM_I_40245 EVENT: FORCE_STARTJOB JOB: testjob [03/08/2017 10:06:53] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: STARTING JOB: testjob MACHINE: win_agent [03/08/2017 10:06:54] CAUAJM_I_40245 EVENT: ALARM ALARM: STARTJOBFAIL JOB: testjob MACHINE: win_agent [03/08/2017 10:06:54] <Owner attribute error. User does not exist in the system> [03/08/2017 10:07:04] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: FAILURE JOB: testjob MACHINE: win_agent EXITCODE: -655 Environment:
11.3 SP7 System Agent on Windows
Cause:
Machine definition contains wrong node_name.
Resolution:
Adapt machine definition with correct node_name.
ncG1vNJzZmirpJawrLvVnqmfpJ%2Bse6S7zGiorp2jqbawutJoaGxsaWuDcn%2BOmqytp6OuwG7EyK1knKeUmnp3gZQ%3D
