Transport control program tp could not be started

[Former Member]

We are Using SAP Enterprise 4.7x100 on Windows 2003 Server and MS SQL Server 2000 as database.

my kernel 6.40 with patch 196, tp version 340.16.38, r3trans version 6.13 (release 640 - 07.01.08 - 14:25:00) and disp+work patch number 219.

I am getting below error message in stms -> Monitor -> TMS Alerts -> TMS Alert Viewer.

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.

Result of RSTPREST as below.

Check Transport Tool 04.03.2008 12:48:25

5 PIP System PIP (generated by transaction SE06)

5 tp Interface

Host Name pintas

Version 1.80

Transport Directory
pintas\sapmnt\trans

Logging On (TPLOG contains 111647 entries)

5 Transport Profile

Path
pintas\sapmnt\trans\bin\TP_DOMAIN_PI..

Profile TP_DOMAIN_PIP.PFL is readable

Version Version 0001 (domain DOMAIN_PIP)

5 RFC Destination

Destination CALLTP_WindowsNT

tp Path E:\usr\sap\PIP\SYS\exe\run\tp.EXE

tp Executable Size: 6,045,696 bytes

RFC Ping Link setup: 50 msec

5 tp Call

RFC Link tp was started successfully

tp Version 340.16.38 (n .ow.unkn)

DB Connect Link to database successful

Offline Call

Here my offline call is not working it comes with down side yellow arrow.

I checked OS level my tp and r3trans are successfully connecting to Database.

Please help me how to resolve this problem.

Thanks & Regards,

Nikunj.

[Former Member]

Hi,

i think there is no error with tp program.

navigate to stms -> Monitor -> TMS Alerts -> TMS Alert Viewer

against Transport environment - Transport tool , you found -> Could not start transport control program tp,

put select Transport environment - Transport tool

click on open alerts

the alerts are display,

now click on display alerts then select all alerts and click on complete alerts

now you find the status of Transport environment - Transport tool green

now again when navigate to stms -> Monitor -> TMS Alerts -> TMS Alert Viewer

you found status red ( this is because there is no tp program is currently running.)

just click on open alerts and check status. it green if there are no alerts.

regards,

kaushal

[Former Member]

Dear Kaushal,

I am not clear with the steps you mention below please kindly give me more clear steps.

>now click on display alerts then select all alerts and click on complete alerts >now you find the status of Transport environment - Transport tool green >now again when navigate to stms -> Monitor -> TMS Alerts -> TMS Alert Viewer >you found status red ( this is because there is no tp program is currently running.) >just click on open alerts and check status. it green if there are no alerts.

Thanks,

Nikunj

Edited by: Nikunj Thaker on Mar 4, 2008 1:19 PM

[Former Member]

Hi,

sorry my mistake.

first check the data and time against alerts. ( stms -> monitor -> tms alerts -> tms alert viewer)

might be it is old not current.

you can check all alert using CCMS

perform the above steps at following path

stms -> monitor -> tms alerts -> CCMS alert monitor.

regards,

kaushal

[Former Member]

I checked date and time it current only not past.

Regards,

Nikunj

[clas_hortien]

Hi,

can you send me the environment of the sap service:

SAP MMC -> Rightclick on the service -> all task -> view environment

And please send me the value of the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\<YourSIDHere>\AdmUser

and all of the keys in the subkey environment.

Regards

Clas

[Former Member]

Hi,

Please find as below.

SAP Environment (System Environment + SAP Registry Environment)

-

---

CLASSPATH=C:\jdk1.3.1_15

ClusterLog=C:\WINNT\Cluster\cluster.log

ComSpec=C:\WINNT\system32\cmd.exe

dbms_type=mss

DIR_PUT=
pintas\sapmnt\put

JAVA_HOME=C:\jdk1.3.1_15

MSSQL_DBNAME=PIP

MSSQL_SCHEMA=dbo

MSSQL_SERVER=pintas

NUMBER_OF_PROCESSORS=6

OS=Windows_NT

Path=C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\WBEM;C:\DMI\win32\bin;e:\mssql7\BINN;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\IBM\Director\bin;;E:\usr\sap\PIP\sys\exe\run;C:\jdk1.3.1_15;C:\jdk1.3.1_15\bin;C:\jdk1.3.1_15\jre\bin\classic

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

PROCESSOR_ARCHITECTURE=x86

PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 6, GenuineIntel

PROCESSOR_LEVEL=15

PROCESSOR_REVISION=0206

SAPLOCALHOST=pintas

SystemDrive=C:

SystemRoot=C:\WINNT

TEMP=C:\TEMP

TMP=C:\TEMP

windir=C:\WINNT

System Environment

-

---

ClusterLog=C:\WINNT\Cluster\cluster.log

ComSpec=C:\WINNT\system32\cmd.exe

NUMBER_OF_PROCESSORS=6

OS=Windows_NT

Path=C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\WBEM;C:\DMI\win32\bin;e:\mssql7\BINN;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\IBM\Director\bin

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

PROCESSOR_ARCHITECTURE=x86

PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 6, GenuineIntel

PROCESSOR_LEVEL=15

PROCESSOR_REVISION=0206

SystemDrive=C:

SystemRoot=C:\WINNT

TEMP=C:\TEMP

TMP=C:\TEMP

windir=C:\WINNT

SAP Registry Environment

-

---

CLASSPATH=C:\jdk1.3.1_15

dbms_type=mss

DIR_PUT=
pintas\sapmnt\put

JAVA_HOME=C:\jdk1.3.1_15

MSSQL_DBNAME=PIP

MSSQL_SCHEMA=dbo

MSSQL_SERVER=pintas

PATH=;E:\usr\sap\PIP\sys\exe\run;C:\jdk1.3.1_15;C:\jdk1.3.1_15\bin;C:\jdk1.3.1_15\jre\bin\classic

SAPLOCALHOST=pintas

TEMP=%SystemDrive%\TEMP

TMP=%SystemDrive%\TEMP

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\PIP\Environment

CLASSPATH=C:\jdk1.3.1_15

DBMS_TYPE=mss

DIR_PUT=
pintas\sapmnt\put

JAVA_HOME=C:\jdk1.3.1_15

MSSQL_DBNAME=PIP

MSSQL_SCHEMA=dbo

MSSQL_SERVER=pintas

PATH=;E:\usr\sap\PIP\sys\exe\run;C:\jdk1.3.1_15;C:\jdk1.3.1_15\bin;C:\jdk1.3.1_15\jre\bin\classic

SAPLOCALHOST=pintas

TEMP=C:\WINDOWS\TEMP

TMP=C:\WINDOWS\TEMP

Thanks,

Nikunj

[Former Member]

Hi,

ok but i think there is no problem with tp program,

it is a alerts form CCMS monitor,

some time when you try to import request you get following

TP_CALL_FAILED

RFC error: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

but when you try to import request again you are able to import request again.

we are also facing this problem after upgrading TP and kernel patch. in QAS system ( domain controller)

try to increase swap (virtual memory)

one more question are you used common transport directory?

regards,

kaushal

[Former Member]

Dear Kaushal,

No we are not using comm. transport directory.

and i am getting message INTERFACE_NOT_OK in stms->monitor->tms alert->tms alert viewer.

Thanks,

Nikunj

[Former Member]

Hi,

Nikunj, please check the transport tool and connection tests for all the systems in your TMS. Check which system is giving you the error.

Now suppose it is in the QAS system please check whether you are able to connect to the database of the system.

also check if you have mentioned the hostname and the respective ip-addresses in the hosts file.

Regards,

Suhas

[Former Member]

Hi Suhas,

At present my tms configured as single system and its domain controller.

No system is attached into it.

yes my hosts file already having entry.

Thanks,

Nikunj.

[Former Member]

Hi,

if your system is defined as single system and local domain controller ,

how you import request in that system,

manually by copying data and cofile?

are you able to import the request in your system?

regards,

kaushal

[Former Member]

Dear Kaushal,

yes you are correct by manually copying co and datafile.

and we are able to import request successfully.

Regards,

Nikunj

[Former Member]

Hi,

so no problem with you STMS configuration and tp/r3trans program,

it's happen some time when you try to import request in sap system the tp program is not started and and gives error. but when you try again you are able to import the request successfully.

this error resulted in alert viewer and you found entry like TP program not started.

regards,

kaushal

.

[Former Member]

Hi,

Nikunj, Kaushal is exactly correct. I have also come across similar response during a single system host. So your configuiration is not having any issue.

Regards,

Suhas

[Former Member]

Hi Suhas

I have also come across similar response during a single system host

it is not occurred only in single system but in two or three system landscape may have same problem,

use of latest kernel and tp/r3trans patch can avoid such problem.

regards,

kaushal

[Former Member]

Dear Kaushal/Suhas,

Yes i don't have any issue STMS and importing request.

I already have latest tp, r3trans and kernel.

But when ever i run program RSTPTEST i get my offline call with downside arrow.

and system through error message in dev_rd log file and also i get error message in TMS alert viewer.

So i can't understand why receiving this error and due to this my spam patch upgrade is stuck.

Regards,

Nikunj

[Former Member]

Hi,

Nikunj what is the error that you are getting in SPAM ?

Regards,

Suhas

[Former Member]

Dear Suhas,

I am not getting any error in SPAM its stuck there and i send message to SAP and SAP says that you first need to clear this and then you start continue with your spam patch upgrade.

Regards,

Nikunj

[Former Member]

Hi,

run SM59 -> TCP/IP connections

perform connection test on CALLTP_* ( for windows * indicate WIN )

check the result.

if connection is failed perform following

login on to domain controller 000 client

call STMS -> overview -> systems -> extras -> generate RFC destinations.

regards,

kaushal

[Former Member]

Dear Kaushal,

Thanks for reply but my CALLTP_WindowsNT RFC Connection working fine.

Thanks & Regards,

Nikunj.

[Former Member]

Hi,

can you provide the trace from SMGW.

run SMGW -> goto -> trace

regards,

kaushal

[Former Member]

Dear Kaushal,

REsult as below.

Tue Mar 04 15:39:19 2008

***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 793]

***LOG S23=> GwIDisconnectClient, client disconnected (021) [gwxxrd.c 11200]

***LOG S74=> GwIDisconnectClient, client disconnected ( pintas) [gwxxrd.c 11211]

***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c 11227]

***LOG S0I=> GwIDisconnectClient, client disconnected ( tp) [gwxxrd.c 11248]

• LOCATION SAP-Gateway on host pintas / sapgw00

• ERROR connection to partner broken

• TIME Tue Mar 04 15:39:19 2008

• RELEASE 640

• COMPONENT NI (network interface)

• VERSION 37

• RC -6

• MODULE ninti.c

• LINE 793

• DETAIL NiPRead (10.32.0.4/4285, hdl 7)

• SYSTEM CALL recv

• ERRNO 10054

• ERRNO TEXT WSAECONNRESET: Connection reset by peer

• COUNTER 45

Thanks,

Nikunj

[Former Member]

Hi,

check the services file contain following entry on sap application host.

\windows\system32\drivers\etc

open services file and check for following entry.

sapgw00 -tab- 3300/tcp

further

try to telnet the server with the port 3200

E.g.: > telnet xx.xx.xx.xx 3200 (check for the response and connection...)

Most of the time if above commands works then the problem is in netwrok only...

Creating and evaluating the network trace from the server and frontend. To test the network, you should run a fatigue test using the tool "niping":

Plz. check the following SAP Notes

Note 26086 - TCP/IP Connection to partner broken

Note 107407 - Win95: Connection Reset by Peer

Note 500235 - Network Diagnosis with NIPING

regards,

kaushal

[Former Member]

Dear Kaushal,

Entry there in services file.

If its network issue i can face problem with other services also.

But i am getting this error message in dev_rd and dev_disp only in case of when i am doing transport profile check through stms.

Thanks,

Nikunj