SAP Agent-specific exit codes
What is it?
When a SAP job fails, the SAP Agent reports an exit code that identifies the stage at which the failure occurred. Use this page to map an exit code in the 70000 range to the operation the agent was attempting (logon, job copy, status check, output retrieval, and so on).
Codes outside this list are Windows system error codes returned by the agent's host. Refer to Windows System Errors in the Concepts online help.
Definition errors
The agent could not assemble a valid request before contacting SAP.
| Exit Code | Description |
|---|---|
| 70001 | The job name (destination) required to identify the SAP target is missing or null. |
| 70002 | The job number required to track this job on the SAP system is null. |
| 70003 | The SAP R/3 and CRM job definition does not have an SAP job name defined. |
| 70004 | The external user configured in the User setting in SAPLSAM.ini is empty. The agent cannot attempt a logon without a user name. |
Connection and logon errors
The agent reached SAP but could not establish or configure the session.
| Exit Code | Description |
|---|---|
| 70005 | Error logging on to the SAP system via the XMI interface. Verify the User, Password, Gateway, SystemNumber, and ClientID settings in SAPLSAM.ini. |
| 70015 | Error setting the XMI audit level during logon setup. |
| 70016 | Error verifying whether extended XBP functions are available on the SAP system. |
Job start errors
Logged on successfully, but the agent could not start the job.
| Exit Code | Description |
|---|---|
| 70006 | Error checking whether the SAP job exists on the system before attempting to start it. |
| 70007 | Error copying the SAP job in preparation for execution. |
| 70008 | Error retrieving the job definition after the copy step. The copy succeeded but the agent could not read back the copied job's details. |
| 70009 | Error starting the copied job (ASAP scheduling). The copy and definition retrieval succeeded but the start call failed. |
| 70017 | Error starting the job immediately because no SAP background work processes were available. |
Runtime monitoring errors
The job started, but the agent could not monitor it through to completion or retrieve results.
| Exit Code | Description |
|---|---|
| 70010 | Error retrieving the job's current status during execution monitoring. |
| 70011 | Error reading the job log after the job completed or failed. |
| 70012 | Error retrieving the list of child jobs generated by this job. |
| 70013 | Error sending the abort command to SAP for this job. |
| 70014 | Error reading the job spool list using the XBP 2.0 interface. |
| 70018 | Error retrieving current status for a list of monitored jobs. |
| 70019 | Error reading job details from the SAP system. |
| 70020 | Error retrieving batch processing resource statistics from the SAP system. |
| 70021 | Error retrieving application information from the SAP system. |
| 70022 | Error reading the application log content for the job. |
FAQs
My job failed with an exit code that isn't in this list. What does it mean? Codes outside this list are Windows system error codes. Refer to Windows System Errors in the Concepts online help.
What should I check first if I see exit code 70004? 70004 means the User setting in SAPLSAM.ini is empty. Add the SAP login user name and encrypt it before saving the file. See Encrypt SAP credentials.
What should I check first if I see exit code 70005?
70005 is an XMI logon failure. Verify the User, Password, Gateway, SystemNumber, and ClientID settings in SAPLSAM.ini. Also confirm the SAP user holds the S_XMI_ALL authorization role. See Prerequisites.
What does exit code 70017 indicate? The agent could not start the job immediately because no SAP background work processes were available. This is typically a SAP-side capacity condition, not a misconfiguration.