TMS Configuration problem - SET_CODEPAGE_FAILED

[Former Member]

I have just installed a new system "CRM 7.0/NW 7.01". The first thing I am doing is configuring TMS in client 000. When I try to distribute the configuration I get an error: TMS Configuration could not start transport control program TP. SET_CODEPAGE_FAILED.

I looked at all the previous posts and have done all the prework: ENV variable dbms_type = ora and I upgraded the kernel to current.

In TMS I don't get an error when I check the connection or when I check the transport directory. It only happens when I check the transport tool. Here is the error message from the dev logs:

• Trace file opened at 20110210 131154 Eastern Standard Time, SAP-REL 701,0,125 RFC-VER U 3 1215400 MT-SL

======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

ABAP Programm: SAPLSTPA (Transaction: SPAM)

Called function module: RFC_TP_INTERFACE_VERSION

User: PREED (Client: 000)

Destination: CALLTP_WindowsNT (handle: 3, 64588453, {254135E0-9A35-F1B2-8C05-0013724E7C66})

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3348

CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829

Thu Feb 10 13:11:14 2011

• ERROR => GwISearchPartner: timeout, partner LU: >SITASERV44<, TP: >C:\usr\sap\CR3\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c 6349]

• ERROR => GwISearchPartner: HOST: SITASERV44, conv ID: 64555875 [gwr3cpic.c 6362]

Thank you for your assistance.

Peggy

[Former Member]

Re: TMS Configuration problem - SET_CODEPAGE_FAILED

Hi everyone,

Go through the note 1913011,to eradicate such kind of errors.

Found Helpful please reward.....

Regards

Mohammed Samiullah

[Former Member]

I found my problem. I had to update the etc/host file with the fully qualified name.

thanks,

Peggy

[Former Member]

I was also facing same issue.

I had following entry in my profile :

SAPGLOBALHOST = solman

system/type = DS

SAPFQDN = solman.server.com

SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)

Due to this at the place of solman.server.com as gateway it was taking solman.solman.server.com

Solution : fix the profile parameter or simply pass an entry (as alias) in the host file as solman.solman.server.com

Took me 2 hours to figure it out. Thanks Peggy you gave a good clue.

Regards,

Vikash

[Former Member]

I updated my kernel to the latest and updated TP to an even higher level than the stack. It is still happening but the message is different. Here is what is in SMGW. I can't figure out why the client says SITASERV and not SITASERV44.

LU Name SITASERV SITASERV44.sitacorp.com

TP Name sapgw00 sapgw00

Host name maggie.nethosters.com SITASERV44

Host Addres 216.9.68.26 192.168.128.44

Syst.Type LOCAL_R3 LOCAL_R3

Number 0 0

[Former Member]

1. I got an error when I did the test in SM59.

2. I regenerated the RFC destinations with no problem.

3. I got the same error when I did the test again in SM59.

4. Here is the output of SMGW:

Thu Feb 10 17:04:47 2011

• ERROR => GwISearchPartner: timeout, partner LU: >SITASERV44<, TP: >C:\usr\sap\CR3\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c 6349]

• ERROR => GwISearchPartner: HOST: SITASERV44, conv ID: 78033078 [gwr3cpic.c 6362]

Thu Feb 10 17:08:02 2011

• ERROR => GwISearchPartner: timeout, partner LU: >SITASERV44<, TP: >C:\usr\sap\CR3\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c 6349]

• ERROR => GwISearchPartner: HOST: SITASERV44, conv ID: 78222109 [gwr3cpic.c 6362]

[Former Member]

Hi

1. check transportool in tcode SPAM or stms.

2. Check TP log in tcode STMS

The issue could be for your kernel level.

Regards

William Neira

[Former Member]

I spoke too soon. I'm still getting an error with the RFC-Ping when I try to use the transport tool.

CR3 System CR3

RFC Ping timeout during allocate / CPIC-CALL: '..

tp Call

RFC Link timeout during allocate / CPIC-CALL: '..

Thank you for your assistance.

Peggy

[Former Member]

HI

follow the steps:

1. In your system in to tcode SM59 -> TCP/IP connections

2. perform connection test on CALLTP_XXXX

3.

a. If the result get any error

login on to domain controller 000 client

run tcode STMS -> overview -> systems -> extras -> generate RFC destinations.

b. If don't get any error please run SMGW and paste trace file here.

Regards

William Neira

[Former Member]

I found the problem. It is in note 1335799.

Ensure file libsapucum.dll is

on both directories - <instance>\exe and SYS\exe\uc\NTAMD64.

(Once I put this dll in both directories, it seems to be working)

Thanks,

Peggy

[Former Member]

I copied the wrong dev_rfc log:

• Trace file opened at 20110210 130049 Eastern Standard Time, SAP-REL 701,0,125 RFC-VER U 3 1215400 MT-SL

======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

ABAP Programm: SAPLSTPA (Transaction: )

Called function module: RFC_TP_INTERFACE_VERSION

User: TMSADM (Client: 000)

Destination: CALLTP_WindowsNT (handle: 3, 63913828, {953F35E0-66FD-F1C8-8C05-0013724E7C66})

SERVER> RFC Server Session (handle: 1, 63911750, {983F35E0-5E6B-F160-8C05-0013724E7C66})

SERVER> Caller host:

SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)

SERVER> Called function module: TMS_CI_START_SERVICE

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3348

CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829