Category Installation Errors
Runtime Errors START_CALL_SICK
Date and Time
Database inconsistency: Start Transaction SICK.
The current program had to be terminated because of an
error when installing the R/3 System.
The error occurred when initializing the R/3 System.
What can you do?
Please call the Transaction SICK. The list generated here
contains an installation error.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
The error probably occurred when installing the
Error text of the first reported error:
“Can’t execute sap_check_if_sick”.
How to correct the error
Report the error to the group responsible for installing your
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
“START_CALL_SICK” ” ”
“SAPMSYST” or “SAPMSYST”
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose “System->List->Save->Local File
2. Corresponding system log
Information on where terminated
Termination occurred in the ABAP program “SAPMSYST” – in
The main program was “SAPMSYST “.
In the source code you have the termination point in line 1781
of the (Include) program “SAPMSYST”.
I received this error after I did DB restore on my current sandbox server from Production.
To resolve this issue I executed report MSSPROCS from SE38.