Transport control program tp could not be started

[former_member199650]

Hi everyone,

I am getting the following error log while transporting the Transport Requests:

*Transport control program tp could not be started*

*Message no. TP608 Diagnosis*

*There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.*

*Error code: 4*

*RFC error text:*

*Meaning of the error codes:*

*03 RFC system failure*

*04 RFC communication failure*

*System Response*

*The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).*

*Procedure*

*Contact your system administrator or use report RSTPTEST to localize the error. You can then execute the command again.*

Please guide.

Thanks and Regards

MP Vashishth

[anindya_bose · Accepted solution]

Hi

It seems you have a problem in RFC.

Please go to SE38 or SA38 and run the program RSTPTEST in dialog mode.

You will get the details of the error.

Depending on your Operating System , you can check CALLTP_Linux or CALLTP_WINDOWS RFC connection from SM59.

Check if both authorization and connection test are fine for this RFC.

[former_member199650 · Accepted solution]

Hi,

Thanks for your reply please.

I have checked SM59, here i got CALLTP_HP-UX.

Here Activation Type is 'Start on Application Server' and SNC is 'Inactive'.

Please guide.

Thanks and Regards

[anindya_bose · Accepted solution]

Please check the link below

http://help.sap.com/saphelp_nwmobile71/helpdata/en/57/898009a859493a8bce56caaf0f8e13/content.htm

[former_member199650 · Accepted solution]

Hi,

I am getting following error while testing connection on SM59:

ERROR timeout during allocate

LOCATION SAP-Gateway on host npcldev / sapgw00

DETAIL no connect of TP /usr/sap/DEV/SYS/exe/run/tp fr

COMPONENT SAP-Gateway

COUNTER 38

MODULE gwr3cpic.c

LINE 5805

RETURN CODE 242

SUBRC 0

RELEASE 640

TIME Tue Feb 9 15:25:28 2010

VERSION 2

Please guide.

Thanks and Regards

Edited by: MP Vashishth on Feb 9, 2010 11:26 AM

[anindya_bose · Accepted solution]

did you upgrade your Kernel patch recently? It could be a reason for this error.

when did you last transport successfully?

Regards

Anindya

[former_member199650 · Accepted solution]

Hi,

Yes, there was an kernal petch upgrade just a few days back , after that some transportations were happend.

Please guide.

Thanks and Regards

Edited by: MP Vashishth on Feb 9, 2010 11:33 AM

Edited by: MP Vashishth on Feb 9, 2010 11:35 AM

[anindya_bose · Accepted solution]

Please then raise a mesasge with SAP mentioning your Kernel patch.. They would be able to tell you which Kernel patch has a solution to the problem.

In the meantime, you can try with other Kernel Patch or else revert back your old Kernel if that is possible.

Please let me know the status..

Thanks and Regards

Anindya

[former_member204746 · Accepted solution]

when you upgraded your kernel, hos did you extract SAR files? di you extract them directly in the kernel directory? If so, you might have extracted all files from AAA to SAPCAR and did not extract SAPCAS to ZZZZ because SAPCAR was in usage.