U2000009 Job '<job_name>' with RUN# '<RUN#>' ended with return code '128'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

U2000009 Job '' with RUN# '' ended with return code '128'

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

Detailed Description and Symptoms

A Windows job ends with a return code of 128.

 Potentially significant messages: 

From the job report/Messages window:   

ended on return code '128'.

Investigation

The return codes that are reported from Automic can come from the job itself, from Automic or from the Operating System.  In this case a job fails with the following the Messages window or in the job report:

20091027/094013.200 - U2000003 Job 'JW.RP.SOLVE' was started with RUN# '5149655'.
20091027/094013.200 - U2001041 The job was started with Process ID = '568 (0x238)'
20091027/094013.216 - U2000034 Monitor thread with thread ID '3280' started successfully.
20091027/094013.231 - U2000009 Job 'JW.RP.SOLVE' with RUN# '5149655' ended on return code '128'.

In this case the 128 return code is coming from within Windows, and not from Automic—Automic is simply reporting the error.

Return code 128 indicates either a Windows heap problem on the machine that has the Windows Agent installed, or permissions problems.  If the Windows Agent has been installed with all of the correct permissions per the documentation (found under Administration Guide? Installation? New Installation? Installation Procedure? Installing the Agents? Installing the Agent for Windows? Section 3. Setting the system environment) then this is most likely a heap problem.  

Reference to this can be found at http://support.microsoft.com/default.aspx?scid=kb;en-us;184802.  You can also check the following Microsoft Knowledge Base articles for how to best resolve this problem:  Q142676, Q175687 & Q184802.

Solution

Confirm that the user that starts the Agent has the following permissions set:
o Act as part of the operating system
o Replace a process level token
o Logon as service
o Logon as batch job *)
o Restore files and directories
o Adjust memory quotas for a process

Then, check the knowledge base article from Microsoft regarding the Windows heap error here:  http://support.microsoft.com/default.aspx?scid=kb;en-us;184802