Users are reporting that Command (CMD) jobs are failing. The agent's joblog shows the job terminating with exit code 180002 and a status of "Unknown error."
Log Example:
03/03/2026 10:36:48.564+0000 CAWA_I_20013 Command to be executed: "C:\Windows\SYSTEM32\cmd.exe" /c "E:\<full_path_to_script>"
03/03/2026 10:36:48.569+0000 CAWA_I_20022 Process created with pid: 8048
03/03/2026 10:42:02.651+0000 CAWA_I_20018 Job failed. Exit code 180002, Status: "Unknown error"
Workload Automation Agent 12.x, 24.x
Windows Server
SAP Business Objects Data Services (BODS)
The joblog indicates that the agent successfully created the process (PID 8048) and initiated the command. The job ran for approximately 5 minutes and 14 seconds before failing. This duration suggests the script successfully started and performed initial processing before encountering a terminal error.
Upon review of the Standard Output (STDOUT) and Standard Error (STDERR) files, it was determined that the script is executing an SAP Business Objects Data Services ETL job via the AL_RWJobLauncher.exe utility.
The exit code 180002 is an application-specific return code from the SAP Business Objects Data Services engine. In this context, 180002 indicates a network failure preventing the Job Launcher from communicating with the Job Server or the repository.
Consult the SAP application team for further assistance.
The "Unknown error" status is displayed because 180002 is not a standard Windows system error code; the WA Agent is simply reporting the return code provided by the AL_RWJobLauncher.exe process.
Per SAP Community, the error numbers in the 180xxx range, such as 180002 ("Network failure"), are primarily categorized under Job Launcher (SCH) errors, indicating issues with job execution, scheduling, or connectivity to the Job Server.
Key Aspects of BODS Error Handling:
180xxx Series: These are generally related to job launcher/execution errors (e.g., 180002 Network failure, 180003 Service not started, 180004 LINK_DIR not defined).