ABAP Runtime Errors

START_CALL_SICK SAP ABAP Runtime Error start call sick







START_CALL_SICK is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: F - Installation Errors

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.


START_CALL_SICK ABAP Runtime Error

Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

Database inconsistency: Start transaction SICK. Start transaction SICK. The list generated here shows the installation errors that have occurred. Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

Error text of the first reported error:
<runtime parameter>. Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

The error occurred during initialization of the SAP system.