Show TOC

Troubleshooting Locate this document in the navigation structure

The Troubleshooting tab provides access to monitoring and error data.

Context

Note If you cannot analyze or solve the error, contact Product Support. See SAP Mobile Platform Server Troubleshooting (guide) for details.
To get the back-end error information, register ERROR_LOG_SRV service in the Management Cockpit.
Note Error logged in the Troubleshooting tab of the Management Cockpit under OData Services is assigned with a transaction ID (available under the TransactionId column), use this ID in the log file to get more details about the error.

Procedure

  1. Under Search criteria,
    1. select From and To date to display errors generated in a particular time frame.
    2. check Show Only Errors option to display log level 'Error'. Uncheck Show Only Errors to display log level 'Error' and 'Debug'.
  2. Click Search. Errors occurred is displayed under Logs.
  3. Select a Timestamp URL in the Logs section to view details of an error.
    1. Select the Details tab for an overview of the error details.
    2. Select the Stack Trace tab for the Java error stack trace.
    3. Choose the Back-end Error Log tab for the error log information of the back-end system. If there is no error in the back-end but only in the Java stack, Back-end Error Log is not displayed.
  4. In the Overview screen:
    1. Select the Details tab for an overview of the error details.
    2. Select the Stack Trace tab for the Java error stack trace.
    3. (Applicable only for SAP Gateway service errors) select the Back-end Error Log tab for the error log information of the back-end system.
  5. To see the error content information for SAP Gateway service errors,
    1. Copy the Transaction ID of the error.
    2. Log in to your back-end system and use transaction /IWBEP/ERROR_LOG to open the back-end error log.
    3. Filter for the copied transaction ID.
    4. Double-click the transaction ID to display the Error Context section.
    5. Click Call Stack to display the Call Stack screen.
    6. From the Call Stack screen, you can navigate to the source code and set a breakpoint to see what went wrong.