STMS Could not start transport control program tp

[Former Member]

Hi

I created the transport system and the fault came up "Could not start transport control program tp" i went to the report RSTPTEST and got this error

timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time

out during connection setup (check that partner exists)

I will just tell you that i use nt and oracle.

I have removed all restrictions to the TP file.

in the gateway trace file i get this:

trc file: "dev_rd", trc level: 1, release: "720"

Wed May 23 10:32:08 2012

***LOG S00=> GwInitReader, gateway started ( 4776) [gwxxrd.c     1732]

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    45

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

pid        4776

gateway runs with dp version 125000(ext=118000) (@(#) DPLIB-INT-VERSION-125000-UC)

gateway (version=720.2010.01.26)

Wed May 23 10:32:09 2012

gw/local_addr : 0.0.0.0

CCMS: initialize CCMS Monitoring for ABAP instance with J2EE addin.

CCMS uses Shared Memory Key 73 for monitoring.

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Bind service sapgw00 (socket) to port 3300

Wed May 23 10:32:10 2012

GwPrintMyHostAddr: my host addresses are :

  1 : [172.25.4.188] Q2SAND2.q2con.local (HOSTNAME)

  2 : [127.0.0.1] Q2SAND2.q2con.local (LOCALHOST)

Full qualified hostname = Q2SAND2.q2con.local

DpSysAdmExtCreate: ABAP is active

DpSysAdmExtCreate: VMC (JAVA VM in WP) is active

Wed May 23 10:32:12 2012

DpIPCInit2: read dp-profile-values from sys_adm_ext

DpShMCreate: sizeof(wp_adm)##43024#(2264)

DpShMCreate: sizeof(tm_adm)##5517056#(27448)

DpShMCreate: sizeof(wp_ca_adm)##64000#(64)

DpShMCreate: sizeof(appc_ca_adm)#64000#(64)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080

DpShMCreate: sizeof(comm_adm)##584080#(1144)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=512/48/65600/90416/156064

DpShMCreate: sizeof(slock_adm)##156064#(104)

DpFileTableSize: max/headSize/ftSize/tableSize=3800/16/364864/364880

DpShMCreate: sizeof(file_adm)##364880#(80)

DpShMCreate: sizeof(vmc_adm)##40896#(2152)

DpShMCreate: sizeof(wall_adm)##(41664/36752/64/192)

DpShMCreate: sizeof(gw_adm)#48

DpShMCreate: sizeof(j2ee_adm)#3936

DpShMCreate: SHM_DP_ADM_KEY##(addr: 000000000DD50050, size: 6930432)

DpShMCreate: allocated sys_adm at 000000000DD50060

DpShMCreate: allocated wp_adm_list at 000000000DD53030

DpShMCreate: allocated wp_adm at 000000000DD53220

DpShMCreate: allocated tm_adm_list at 000000000DD5DA40

DpShMCreate: allocated tm_adm at 000000000DD5DA90

DpShMCreate: allocated appc_ca_adm at 000000000E2B03B0

DpShMCreate: allocated comm_adm at 000000000E2BFDC0

DpShMCreate: allocated slock_adm at 000000000E34E760

DpShMCreate: allocated file_adm at 000000000E374910

DpShMCreate: allocated vmc_adm_list at 000000000E3CDA70

DpShMCreate: allocated vmc_adm at 000000000E3CDB20

DpShMCreate: allocated gw_adm at 000000000E3D7AF0

DpShMCreate: allocated j2ee_adm at 000000000E3D7B30

DpShMCreate: allocated ca_info at 000000000E3D8AA0

DpCommAttachTable: attached comm table (header=000000000E2BFDC0/ft=000000000E2BFDD0)

MtxInit: -2 0 0

DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm

Wed May 23 10:32:31 2012

GwDpInit: attached to gw_adm at 000000000E3D7AF0

Wed May 23 10:33:58 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2254ms (tl=2000ms; UC)

Wed May 23 10:47:35 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2252ms (tl=2000ms; UC)

Wed May 23 10:57:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 11:12:41 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 11:27:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2554ms (tl=2000ms; UC)

Wed May 23 11:42:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2558ms (tl=2000ms; UC)

Wed May 23 11:57:34 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 12:07:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 12:22:40 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 12:37:40 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 12:52:38 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2553ms (tl=2000ms; UC)

Wed May 23 13:07:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2554ms (tl=2000ms; UC)

Wed May 23 13:22:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2554ms (tl=2000ms; UC)

Wed May 23 13:37:32 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 13:47:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 14:02:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 14:17:34 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2252ms (tl=2000ms; UC)

Wed May 23 14:27:39 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 14:42:38 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 14:57:38 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Wed May 23 15:12:40 2012

NiHLGetNodeAddr: to get 'XXXXXX' failed in 2251ms (tl=2000ms; UC)

Hope you can help me

Regards

Mark

SLOG00.LOG.zip

[Former Member · Accepted solution]

i just saw in tms alert viewer that the first alert was

File \\******\sapmnt\trans\bin\TPPARAM could not be opened for reading (Permission denied)

But i have given full access to these folders. is it something else i should do?

Regards

Mark

[former_member189725 · Accepted solution]

Can you check in STMS -- systems overview -- SAP system --Check -- Transport directory .

Is the transport directory shared properly ??

Can run check if you can access the directory \\******\sapmnt\trans\bin\  from Start --> Run in the Windows server ??

Regards

Ratnajit

[Former Member · Accepted solution]

Hi,

as Ratnajit suggested please perform as below.

check in STMS -- systems overview -- SAP system --Check -- Transport directory

check in STMS--systems overview--- sap system --- check --TP

above checks should be good.

always tp and r3trans should be latest version.

Thanks,

Venkat

[Former Member · Accepted solution]

I did the check with the transport directory and that was ok.

But when i check the transport tool. i get this error under RFC ping:

timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time

out during connection setup (check that partner exists

tp version is 266

R3trans is version  6.19 (release 720 - 06.04.10)

[Former Member · Accepted solution]

Hi Mark,

I feel  this could be the problem of tp. Have you tried to use latest tp version?

Also go through

1541076 - Preliminary checks and troubleshooting for transport
issues

Is this a first system in the transport domain?

In case you are adding the system in the Transport domain, try using the same tp as your TR Domain.

Regards,

Vishal

[Former Member · Accepted solution]

Hi All sorry for the late answer. You partly correct about the TP version i already had upgraded. but some how i got a wrong version. so i upgraded it again and it worked. thanks a lot.

[Former Member]

I simply upgraded the whole kernel and now it worked. I simply did the upgrade eailier with the wrong version.

[former_member189725]

Can you paste the last few lines tp system log (SLOG) .

That can give some more info .

Regards

Ratnajit

[Former Member]

5FCCA4E1A044F1279551000C293D5029                                                                                                          ** EMF20120523134328000488800012Bc        SAPSYS                          RSBTCRTE                                0001                                                                83CCA4E19E15F1039551000C293D5029                                                                                                          ** EME20120523134328000488800012Bc        SAPSYS                          RSBTCRTE                                0001WF-BATCH        750                                             83CCA4E19E15F1039551000C293D5029                                                                                                          ** EME20120523134328000488800012Bc        SAPSYS                          RSBTCRTE                                0001Job: SWWDHEX                              13402800              83CCA4E19E15F1039551000C293D5029                                                                                                          **pE0A20120523134328000488800012Bc        SAPSYS                          RSBTCRTE                                0001&aWF-BATCH&b750                                                 83CCA4E19E15F1039551000C293D5029                                                                                                          **

[Former Member]

I have also attached the log file.

Thanks a lot