|
Troubleshooting |
Troubleshooting |
Problems by Importing Functional Components |
|
This document contains information that will support you in recognizing the source of errors which cause the agent to function improperly or individual tasks to be executed incorrectly.
The first source to be checked is the activation log of the AE job for SAP. It provides information about the actions the agent has taken in connection with the SAP system and how the particular actions ended.
Sometimes the error cause is easily found in the attributes of an executable object (such as a wrong client or user). Check the attributes of the particular object.
An SAP user (client, name or passport) must be defined in a Login object to be able to establish a connection to the SAP System. This user must also be available with the same passwordA secret combination of characters for a Automation Engine user. in all an SAP system's clients in which tasks are executed. Check the Login object and the users in the SAP system.
Within the SAP system, the agent is represented by the CPIC user. This user requires the appropriate rights such as operator rights for background processing, for example. Check the rights of the SAP system's CPIC user.
Through job logs and spool lists, the transaction "SM37" provides information about job executions. The XMI log which can be called using "RZ15" also supplies helpful records.
Agent and Server log files provide exact information about the relevant point in time when the error occurred. These files' contents are also provided in the System Overview. The initial section shows the complete INI file including the parameters which have been specified for the agent and server. This section is followed by a chronological list of all executed actions.
Error situations occurring in the SAP system are logged in SAP's system log. Use the SAP transaction "SM21" to view the system log. In particular cases (such as when the agent fails to schedule a job step), the SAP system log is automatically copied to an own tab in the AE report.
Traces provide even more detailed information than log files. They contain all messages which were sent from and to agent and server or agent and SAP system (RFC trace). Traces can be activated in the agent's INI file or the System Overview. Trace contents are stored in files in the agent's working directory or an individually defined directory.
Traces are required for the support or development team's analysis process. Always include this information in your support message.
An activated RFC trace create files on agent side but also on SAP's application server computer. Automic recommends activating traces only for a short period of time in order to reduce the hard disk's memory consumption. Set gw/accept_remote_trace_level to 0 if no trace files should be created in the SAP system.
Further information about RFC trace is available in the SAP note number 532918.