User may see following error(s) when using Global variables or JavaScript
Application Name | VAR_ECHO_WINDOWS_TESTING |
Generation Number | 5 |
Job Name | ECHO |
State | SUBERROR |
Job Type | NT |
Status | Invalid AFM |
Start Time | Thu 3 Feb 2022 14:16:51 EST |
End Time | Thu 3 Feb 2022 22:15:58 EST |
Agent Name | AGENT |
Submission Count | 1 |
Command to run | c:\tmp\echo_test.bat |
Arguments to pass | 100 200 300 400 500 600 700 800 900 10 |
The WA Agent logs will show error similar to this:
20220202 16011312+0500 DESERVER_7500 AGENT ECHO/ VAR_ECHO_WINDOWS_TESTING.2/MAIN STATE SUBERROR Failed SetEnd Status(Invalid AFM) Plugin(runner) User(AGENT) Host(DESERVER)
Release : 12.2/12.3
Component : ESP dSeries
The job is likely using Global var or Javascript to substitute some fields.
E.g. The "Arguments to pass" in the following job is using Variables.
If Variable values are incorrect or have any special characters, then job will get those values.
In Desktop Client, navigate to Services -> Global Variable or JavaScript. Open the variable or script used by the job and check them for any special/hidden or incorrect characters.
E.g The following variable called PARM4 has a return after 400. This cannot be used by the WA Agent as ARGS in command (Unix/Windows).
Note: There may be other errors or values that can result in job failing with "Failed SetEnd Status(Invalid AFM)".