Runtime Errors - START_CALL_SICK

Category Installation error Runtime Errors START_CALL_SICK Date and Time 01.06.2017 11:13:43

|Short Text |

|What happened? | | The current program had to be terminated because of an | | error when installing the R/3 System. | | The current program had to be terminated because of an error when | | installing the SAP system. |

|What can I do? | | Start transaction SICK. The list generated here shows the installation | | errors that have occurred. | | Note which actions and entries caused the error to occur. | | | | Consult your SAP administrator. | | | | Using transaction ST22 for ABAP dump analysis, you can view, manage, |

|Error analysis | | The error probably occurred when installing the | | R/3 system. | | Error text of the first reported error: |

|How to correct the error | | Report the error to the group responsible for installing your | | R/3 System. | | If the error occurs in a non-modfied SAP program, you might be able to | | find a solution in the SAP Notes system. If you have access to the SAP | | Notes system, check there first using the following keywords: | | | | “START_CALL_SICK” | | “SAPMSYST” bzw. SAPMSYST | | “D020_SNC_CHECK_EXTID” | | If you cannot solve the problem yourself, please send the following | | information to SAP: | | | | 1. This description of the problem (short dump) | | To do this, choose System -> List -> Save -> Local File (unconverted) | | on the screen you are in now. | | | | 2. A suitable system log | | To do this, call the system log in transaction SM21. Restrict the time | | interval to ten minutes before the short dump and five minutes after | | it. In the display, choose System -> List -> Save -> Local File | | (unconverted). | | | | 3. If these are programs of your own, or modified SAP programs: Source | | code of these programs | | To do this, choose More Utilities -> Upload/Download -> Download in | | the Editor. | | | | 4. Details regarding the conditions under which the error occurred or |