Symptom
The client export (transaction SCC8) or the client import stops. In the Main export or the Main import log (in transaction SCC3) the below error can be seen:
Transport program tp could not be started (RC= 9)
Scenario A:
The SLOG in DIR_TRANS/log shows the following errors:
ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
The gateway trace (dev_rd) logs a similar error as below:
GwICheckFrag: no write to client sapcac//usr/sap/<SID>/DVEBMGS00/exe/tp (idx 167, hdl 80) within 120 seconds, disconnect now
***LOG S23=> GwIDisconnectClient, client disconnected (167) [gwxxrd.c 10701]
***LOG S74=> GwIDisconnectClient, client disconnected ( sapcac) [gwxxrd.c 10712]
***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c 10729]
***LOG S0I=> GwIDisconnectClient, client disconnected ( tp) [gwxxrd.c 10742]
Scenario B:
The SLOG in DIR_TRANS/log shows the following error or similar:
WARNING: System <SID>. Warning. <timestamp> :
ERROR: The following call returned with exit code 7:
ERROR: sapevt SAP_TRIGGER_RDDIMPDP name=<SID> tpsid=<SID> pf=<path/to/profile> -t
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
Read more...
Environment
Release based on SAP NetWeaver
Product
Keywords
RC = 9, TRINT_PROGRESS_INDICATOR, GwIDisconnectClient, GwICheckFrag, client copy, SCC8, TRSTATUS!='R', Could not start transport control program tp , KBA , BC-CTS-CCO , Client Copy (For ByD issues select BC-TLM-CP) , BC-CST-GW , Gateway/CPIC , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.