RFC to external program - timeout during allocation CPIC-CALL:

[Former Member]

Hello,

I have run external app through RFC in SAP. In "Program ID" I have pasted application path "C:/ ..... / sample.exe" , other options is setting as default.

I got , below error:

	timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
.	ERORR: timeout during allocate
	LOCAL: SAP-Gateway on host srv53 / sapgw00
	DETAILS.: no connect of TP "path external application exe"
	COMPONENT: SAP-Gateway
	COUNTER: 288108
	MODULE: gwr3cpic.c
	LINE: 6178
	RETURN CODE: 242
	SUBRC: 0
	VERSION: 700
	TIME: Thu Aug 08 10:52:49 2013
	VERSION: 2

Anyone could explain me what do I wrong, step by step? I'm beginner

thanks

[Former Member · Accepted solution]

Hi,

Go to SM59 under TCP/IP section look for RFC called SERVER_EXEC do connection test on this and see if it works.

If it does not you will have to redeploy the RFCSDK componensers for rfcexec as this does not get distributed with the kernels anymore.

Also if the rfcexec is there and the RFC test works correctly in SM59 you will have to verify the configuration and set it up to allow externel programs and so forth.

Refer to notes:

Note 1581595 - rfcexec and startrfc missing after upgrade

Note 676938 - Known problems with the RFCEXEC program

Note 27517 - Installing RFCSDK

This can get rather complex so you may have to contact SAP AG for assistance

Example http://howtosap.blogspot.com/2011/03/create-rfc-tcpip-connection-and.html

Kind Regards,

Johan

Message was edited by: Johan Van Zyl

[Former Member · Accepted solution]

Hi Johan.

From above link with create rfc tcpip connection(on blogspot):

In "Program ID" should I paste my *.exe application path ?

In my SAP installation folder, I have not folder called my hostname (from sy-host field). In the above example R3DEV. I have not also rfcexec.exe in my SAP installation folder.

Test connection in SERVER_EXEC also does not work.

Message was edited by: O K

Message was edited by: O K

[Former Member]

Hello OK,

You need to ensure that saprfc.ini file is maintained with apprpriate detail of SAP application server. Once the below paramters have been maintained in saprfc.ini you must restart the external application.

DEST=MYDEST

TYPE=

PROGID=mydest

GWHOST=nnn.nnn.nnn.nnn

GWSERV=sapgw??

RFC_TRACE=

You can find saprfc.ini file in external application installation directory.

You also need to ensure that RFC created(using SM59) in SAP system must have same detail(ex program id) as maintained in saprfc.ini file.

[Reagan]

Hello

If the RFC is used to connect to an external application then you need to create an RFC connection with connection type T and activation type as registered server program with the Program ID specified in it.

Regards

RB

[Former Member]

Can I only do this by Registered Server Program? I would do this, by "Start on Front-End Work Station", but it still not working.Still, I'm getting "timeout during allocation".

Message was edited by: O K

[former_member215981]

Hello OK,

you could use "Start on Front-End Work Station" as well, in this case, you have to ensure the external program's network can connect to  the sap server's network.

Best Regards,

Yong Luo

[AtulKumarJain]

hi OK,

Could you please run report RSTPTEST in se38.

Please provide result of that.

Also please check RFC destination CALLTP_*

Best Regards,

Atul

[Former Member]

Hi Atul Jain,

RSTPTEST shows "CALLTP_WindowsNT"

[AtulKumarJain]

Hi OK,

Could you please check the RFC destination CALLTP_WindowsNT in sm59 .

and provide the result.

Also please paste the output of RSTPTEST here.

BR

Atul

[Former Member]

CALLTP_WindowsNT in sm59:

Logon	87 msec
Transfer of 0 KB	0 msec
Transfer of 10 KB	1 msec
Transfer of 20 KB	1 msec
Transfer of 30 KB	1 msec

Output RSTPTEST:

tp Interface

    Host Name             srv53

    Version               1.80

    Transport Directory   \\srv53\sapmnt\trans

    Logging               On (TPLOG contains 59152 entries)

Transport Profile

    Path                  \\srv53\sapmnt\trans\bin\TP_DOMAIN_EMU.

    Profile               TP_DOMAIN_EMU.PFL is readable

    Version               Version 0004 (domain DOMAIN_EMU)

RFC Destination

    Destination           CALLTP_WindowsNT

    tp Path               C:\usr\sap\EMU\DVEBMGS00\exe\tp.EXE

    tp Executable         Size: 8.095.016 bytes

    RFC Ping              Link setup: 87 msec

tp Call

    RFC Link              tp was started successfully

    tp Version            372.04.10 (n .ow.unkn)

    DB Connect            Link to database successful

    Offline Call          tp started in background

I would , simply run exe application, without "timeout during allocation" using "Front-End Work Station"

[Former Member]

Hi,

The "registered program id" is the name or handle that your program will register in the sap gateway.  For example, you could call this "Sample" or "MyProgram", but it's best to use something that is relevant to the connection type or system it's coming from.  Just put "Sample" as the registered program id.

You then need to start the external program which connects to the SAP Gateway and see if it is registered with transaction SMGW.

Try this for a start.

Regards,

Graham