ESP dSeries Workload Automation

 View Only
  • 1.  Windows Agent Causing Jobs to Fail

    Posted Mar 03, 2020 09:58 PM
    Hi everyone. Just wondering if anyone has come across a similiar issue. We had one of our Windows agents (11.3.4 version) causing jobs to fail all of a sudden. It was not marked inactive, the manager server was able to communicate fine to the agent. However, in looking at the application logs from the agent server, we found the below error. This seemed to be causing jobs to simply fail for no reason. I even ran the SetExitC.exe that comes with the agent install. I passed a return code of 0 for a simple test of the agent. The job ended up failing with a 255 instead.

    To fix the issue I simply stopped and restarted the agent service. This allowed the jobs to be run fine after being resubmitted. We are wondering if there is any way to be proactive here and identify the issue before it causes jobs to fail, maybe even have the agent service recycled automatically. I'm not sure what the error is and if it is feasible to monitor for a specific error.

    We are on Dseries 12.1

    Log Name:      Application
    Source:        Application Error
    Date:          3/2/2020 11:05:44 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Faulting application name: su.exe, version: 0.0.0.0, time stamp: 0x5411dff5
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.19629, time stamp: 0x5e2fdc0d
    Exception code: 0xc0000142
    Fault offset: 0x00000000000ecf30
    Faulting process id: 0x1958
    Faulting application start time: 0x01d5f0ac6d9669ce
    Faulting application path: C:\Program Files\CA\WA Agent R11.3.4\su.exe
    Faulting module path: KERNELBASE.dll
    Report Id: ab4ee1a1-5c9f-11ea-8112-005056bcc0e6


  • 2.  RE: Windows Agent Causing Jobs to Fail
    Best Answer

    Broadcom Employee
    Posted Mar 04, 2020 10:28 AM
    Hi Travis,
    The error "Exception code: 0xc0000142" usually indicates some kind of permission issue.  If this is reproducible then you can user Procmon from Sysinternals.  It can tell you if there was problem loading any libraries.  You can also grant additional permission in the User Access Control (UAC).

    Act as part of the operating system
    Adjust memory quotas for a process
    Allow log on locally
    Back up files and directories
    Logon as batch job
    Logon as service
    Replace a process level token
    Restore files and directories

    HTH,

    Nitin Pande

    ------------------------------
    Support
    Broadcom
    Toronto
    ------------------------------



  • 3.  RE: Windows Agent Causing Jobs to Fail

    Posted Mar 06, 2020 03:03 PM
    Thanks Nitin. I will need to take this up with our Windows admins, this is beyond my scope of expertise :)


  • 4.  RE: Windows Agent Causing Jobs to Fail

    Posted Aug 19, 2020 03:49 AM
    Hi Travis,

    have you been able to resolve this issue?