RFC SAPDB_DBM fails to execute sapdbmrfc: timeout durring allocate

We are building a copy of Production APO and Live Cache systems for special project. Prod environment consists of two servers, and so does the copied environment. APO and its Oracle DB start OK. LC, on separate server, also seems to start OK - we can connect via command line (dbmcli, and SAPDB Gui). However, APO cannot reach LC - source of failure seems to be SAPDB_DBM.
When I test the RFC SAPDB_DBM it fails with:
"ERROR     timeout during allocate
LOCATION   SAP-Gateway on host apohost1 / sapgw30
DETAIL     no connect of TP sapdbmrfc from apohost1 after 22 sec
COMPONENT SAP-Gateway
COUNTER    20
MODULE     gwr3cpic.c
LINE       5778
RETURN CODE 242
SUBRC      0
RELEASE    46D
TIME       Fri Dec 30 11:05:39 2005
VERSION    2"
We have APO 3.1 on Oracle 9i, and LC 7.4.2.
Thank you,
Drew Andreatta

Hi,
I have the same problem, but my versions are SCM 5.00, HP-UX B.11.23 U ia64, ORACLE 10.2.0.2.0 and live cache 7.6.01.09, SAP Kernel 700 patch 95.
When starts Live cache it works well, but after some hours the Communication between SCM and Live cache is lost its sends the next error in LC10.
Name and Server     : LCD - fedvap01
DBMRFC Function     : DBM_CONNECT
Error               : Communication Error
Error Message       : Error when opening an RFC connection
and the test for RFC SAPDB_DBM
Cancel
timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' Timeout al intentar establecer
ERROR: timeout during allocate
LOCATION: SAP-Gateway on host fedvap01 / sapgw01
DETAIL: no connect of TP sapdbmrfc from host fedvap01 after 20 sec
COMPONENT: SAP-Gateway
COUNTER: 1965
MODULE: gwr3cpic.c
LINE: 5873
RETURN CODE: 242
SUBRC: 0
RELEASE: 700
TIME: Mon Apr 23 12:20:42 2007
VERSION: 2
For RFC SAPDB_DBM_DAEMON
Connection Error
Error when opening an RFC connection
ERROR: program dbmrfc@sapdb not registered
LOCATION: SAP-Gateway on host fedvap01 / sapgw01
DETAIL: TP dbmrfc@sapdb not registered
COMPONENT: SAP-Gateway
COUNTER: 1968
MODULE: gwr3cpic.c
LINE: 1694
RETURN CODE: 679
SUBRC: 0
RELEASE: 700
TIME: Mon Apr 23 12:21:06 2007
VERSION: 2
The comand dbmcli -s dbm_getpath IndepProgPath sends /sapdb/programs.
Please HELPME.
Minerva Paredes

Similar Messages

RSTPTEST , RFC ping failed RFC error text: timeout during allocate / CPIC-C

Hi all,
I was transporting the request in my landscape last week and all of sudden transports in acceptance system is not working and I am getting a error message as
Could not start transport control program tp
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: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
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).
SMGW logs are as follows:
Tue Jun 16 12:04:28 2009
ERROR => GwISearchPartner: timeout, partner LU: >hostname<, TP: >M:\usr\sap\SID\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c 6135]
ERROR => GwISearchPartner: HOST: hostname conv ID: 50323660 [gwr3cpic.c 6148]
, This is the 3 system landscape, common transport directory in development system.
Actions taken:
Restarted the systems (PRD queue is working but not acceptance queue)
DIR_TRANS and Permission were given already and able to ping from all the sytem
Host and service entry were maintained already.
RFC connections were woring fine without errors
I have seen many threads but none of the thread is solved my problem.
Please suggest
Vijay

Hello,
Thanks fpr your reply and I tried the steps which you said and the result is same error for both the options.
1 & 2 Answers :
Could not start transport control program tp
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: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
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).
SMGW logs are as follows:
Tue Jun 16 12:04:28 2009
ERROR => GwISearchPartner: timeout, partner LU: >hostname<, TP: >M:\usr\sap\SID\DVEBMGS00\exe\tp.EXE< http://gwr3cpic.c 6135
ERROR => GwISearchPartner: HOST: hostname conv ID: 50323660 http://gwr3cpic.c 6148
I think this is not able to contact the domain controller.
But I can see the checks are fine from checking the transport directory.
Vijay

Error in START_SHDI_FIRST... RFC logon fails

Hello All,
I cannot get past a step in the enhancement package 4 installation. The step is called: START_SHDI_FIRST. The error says to troubleshoot by looking at 2 logs, STARTSFI.LOG and DEVTRACE.log.   extracted below.
The problem can be described this way. The step begins as the installer tries to start the shadow system.   The first attempt stopped and I could see that the shadow was not started. I used the information in note 525677 to manually start the shadow and could verify that it was starting.
The screen says to retry until I can logon to the shadow.   I am able to logon as user SAP* with password pass in client 000.   I am not able to logon as myself and receive the message: Logon not possible (error in license check).
As SAP* I use the transaction SLICENSE, and could see that the maintenance certificate had expired. I loaded that certificate without an error.
I also see that the hardware key information is missing. SAP* is not allowed to update that information.
I believe that no other user will be able to logon as long as the license is an issue.   The installer is trying to do a remote logon to verify that the system is up (my interpretation) .
I also see this information in the shadow system dev_W1 log.
M *** ERROR => ThMsGetHardwareId: ThOpcodeToMsg failed (1) [thxxmsg.c    3095]
M ***LOG Q16=> ThGetMsHwId, DpMBufHwIdGet (HWID_PENDING) [thxxmbuf.c   511]
M *** ERROR => SlicLikeyGetHardwareKey: no hwid from MSG server: -1 [sliclikey.c 1301]
M *** ERROR => likey_get_validity_dates: Error getting the hardware key. You might find some information in file "dev_ms" on the message server
M
M Thu Jul 29 15:18:28 2010
M *** ERROR => ThCheckReqInfo: message send/receive failed [thxxhead.c   17580]
M
M Modeinfo for User T8/M1
So, am I correct in seeing that the missing hardware key is the problem in the shadow system?   Any ideas would be appreciated, otherwise I will clear the systems out and start over. Thanks.
Pat.
Below is the DEVTRACE   (extract)
Directory: /usr/sap/TEH/EHPI/abap/log
Name:       DEVTRACE.LOG
trc file: "dev_disp.new", trc level: 1, release: "701"
sysno      15
sid        TEH
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    69
intno      20020600
make:      single threaded, ASCII, 64 bit, optimized
pid        103802
Thu Jul 29 14:54:58 2010
kernel runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
length of sys_adm_ext is 364 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (15 103802) [dpxxdisp.c   1287]
     shared lib "dw_xml.so" version 69 successfully loaded
     shared lib "dw_xtc.so" version 69 successfully loaded
     shared lib "dw_stl.so" version 69 successfully loaded
     shared lib "dw_gui.so" version 69 successfully loaded
     shared lib "dw_mdm.so" version 69 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3615
MtxInit: 30000 0 0
Thu Jul 29 14:54:59 2010
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation std
<ES> Info: use normal pages (no huge table support available)
EsStdUnamFileMapInit: ES base = 0x7000000b0000000
EsStdInit: Extended Memory 4096 MB allocated
<ES> 1023 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
Thu Jul 29 14:55:00 2010
WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13279]
DpSetProcessPriority: Run priority for work process startup adjusted to 20
DpSetProcessPriority: Run priority for work process startup adjusted to 20
Thu Jul 29 14:55:01 2010
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 9
    (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1816]
Thu Jul 29 14:55:19 2010
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Thu Jul 29 14:55:53 2010
***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
ERROR => NiPConnect: SiConnect failed for hdl 3 / sock 10
    (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Thu Jul 29 14:56:34 2010
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5007]
trc file: "dev_ms", trc level: 1, release: "701"
[Thr 01] Thu Jul 29 14:54:56 2010
[Thr 01] MsSOsPrivInit: Run priority adjusted to 12
[Thr 01] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    63
intno      20020600
make:      multithreaded, ASCII, 64 bit, optimized
pid        103801
[Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 103801) [msxxserv_mt. 1853]
[Thr 01] Thu Jul 29 14:54:57 2010
[Thr 01] SigISetDefaultAction : default handling for signal 20
[Thr 01] ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3239]
[Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1 / sock 7
    (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:3615) [nixxi.cpp    3239]
[Thr 01] *** ERROR => MsSCommInit: NiBufListen(3615) (rc=NIESERV_USED) [msxxserv_mt. 10222]
[Thr 01] *** ERROR => MsSInit: MsSCommInit (internal) [msxxserv_mt. 1903]
[Thr 01] *** ERROR => main: MsSInit [msxxserv_mt. 5983]
[Thr 01] ***LOG Q02=> MsSHalt, MSStop (Msg Server 103801) [msxxserv_mt. 6030]
trc file: "dev_rd", trc level: 1, release: "701"
Thu Jul 29 14:55:00 2010
Shared memory semaphore administration area size = 10608
Thu Jul 29 14:55:06 2010
***LOG S00=> GwInitReader, gateway started ( 103807) [gwxxrd.c     1758]
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    68
intno      20020600
make:      single threaded, ASCII, 64 bit, optimized
pid        103807
gateway runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
gateway (version=701.2009.09.28)
gw/local_addr : 0.0.0.0
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
Thu Jul 29 14:55:09 2010
CCMS: Checking Downtime Configuration of Monitoring Segment.
Bind service sapgw15 (socket) to port 3315
GwPrintMyHostAddr: my host addresses are :
1 : [10.127.0.100] omni (HOSTNAME)
2 : [127.0.0.1] LOOPBACK (LOCALHOST)
Full qualified hostname = omni.plastekgroup.com
DpSysAdmExtCreate: ABAP is active
DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
MtxInit: -2 0 0
Thu Jul 29 14:55:47 2010
GwDpInit: attached to gw_adm at 700000080599e90
Thu Jul 29 14:55:48 2010
DpSetProcessPriority: Run priority for gwrd adjusted to 12
AN EXTRACT OF STARTSFI_LOG
Directory: /usr/sap/TEH/EHPI/abap/log
Name:       STARTSFI.LOG
1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20100729145436")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '14', GwService = 'sapgw14'
4 ETQ399 Environment variables:
4 ETQ399   dbs_db4_schema=<null>
4 ETQ399   auth_shadow_upgrade=<null>
4 ETQ399 Set environment for standard connect:
4 ETQ399 ENV: dbs_db4_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=0
4 ETQ399 Set RFC variables for standard connect:
4 ETQ399 System-nr = '14', GwService = 'sapgw14'
4 ETQ399 Set tool parameters for standard connect:
4 ETQ399   default TPPARAM: DEFAULT.TPP
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 ENV: dbs_db4_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=1
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '15', GwService = 'sapgw15'
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399   default TPPARAM: SHADOW.TPP
4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
2 ETQ399 Starting shadow instance
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2 ETQ399 Stopping shadow instance
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
2 ETQ231 RFC Login failed
2 ETQ353 Starting system
3 ETQ399 Executing command: 'startsap SID(TEH) INSTANCE(15) PROFILE('/usr/sap/TEH/EHPI/abap/TEH/SYS/profile/START_DVEBMGS15_omni')'.
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally

Hi,
You are getting this error because your hardware key in the license installed in slicense is wrong. Since upgrade tries to login with ddic user and if there is problem with license then only SAP* user is allowed.
Please perform below steps to resolve the problem. Check at OS level what is the hardware key, if the hardware key that is present in slicense is different then generate a permanent license of that hardware key and apply it in shadow instance. After that check whether you are able to login with user other than SAP*, if yes, then repeat the phase.
Please perform above steps and let us know the result.
Thanks
Sunny

What is the best Resolution for this Error: Failed to execute IS server package because of error 0x80131904. Server:

Dear Forum Members,
I have an SSIS running perfectly when i run it in Visual Studio Shell. I have organized it into a job which runs well on SQL Server agent at intervals.
However, suddenly, i started having this error as stated in the title. Please find details of the error below and kindly help resolve it ASAP.
Error Details:
Date 1/27/2015 11:24:00 AM
Log Job History (FmdqSync)
Step ID 1
Server ITGTESTSERVER
Job Name FmdqSync
Step Name S1
Duration 00:00:30
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:24:00 AM Failed to execute
IS server package because of error 0x80131904. Server: ., Package path: \SSISDB\FMDQSync\FMDQServerDataSync\FMDQServerDataSync1.dtsx, Environment reference Id: NULL. Description: Timeout expired. The timeout period elapsed prior to completion of
the operation or the server is not responding. The statement has been terminated. Source: .Net SqlClient Data Provider Started: 11:24:00 AM Finished: 11:24:30 AM Elapsed: 30.187 seconds. The package execution
failed. The step failed.

Hi Sadeeq,
Based on your description and the error message, it should be a timeout issue when the ADO .NET Source connects to the source database. So, please refer to the following two suggestions:
Double click on the ADO .NET Connection Manager, click the All tab, and set the “Connect Timeout” property to a bigger value. By default, it is 15 seconds.
Increase the DefaultBufferSize value of the Data Flow Task. By default, the DefaultBufferSize is 10 (MB), you can increase it to a value that is less than 100 (MB).
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Timeout during allocate of Vertex RFC

Hi Guys.
Im facing this odd issue after an offline backup is completed and brings the system.
As you can see the Vertex RFC is no longer working and displays a timeout issue after a Sales programs tries to reach it.
Also when testing the RFC is unable to initialize.
M *****************************************************************************
M *
M * LOCATION    SAP-Gateway on host etgrws01.entegris.com / sapgw20
M * ERROR       timeout during allocate
M *
M * TIME        Tue Dec 28 16:43:08 2010
M * RELEASE     640
M * COMPONENT   SAP-Gateway
M * VERSION     2
M * RC          242
M * MODULE      gwr3cpic.c
M * LINE        1854
M * DETAIL      no connect of TP /boltons/D01/vertex/3.3/TransLink/verrfc from
M *              host etgrws01.entegris.com after 22 sec
M * COUNTER     6378
M
A RFC 1448 CONVID 40614370
A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPECMINIT
A RFC> ABAP Programm: CL_XTAX_RULES_RFC=============CP (Transaction: VA02)
A RFC> User: VMESENBR (Client: 200)
A RFC> Destination: VERTEX (handle: 3, , )
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
[abrfcio.c    7933]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1464
CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =VERTEX
HOST =etgrws01
PROG =/boltons/D01/vertex/3.3/TransLink/verrfc
[abrfcio.c    7933]
That /boltons/D01/vertex/3.3/TransLink/verrfc is located on the same server as the SAP application, so i cannnot figure out why is showing partner not available/timeouts, when is pinging a program on the same server.
I have tried restarting the Dispatcher
rfc/use_gwstart =1
Increased CPIC timeout value gw/cpic_timeout =120 (Increased CPIC timeout)
I have also searched thru these notes but still no luck
Note 581509 - Reasons for timeout during allocate
Note 638701 - Starting RFC servers takes too long
Note 948636 - Starting executables locally using RFC
The only workaround for this, is restarting the SAP Application, in order to have the RFC working again, but this seems an overkill to fix an RFC Ping Issue.
All ECC Systems have the same program version and configuration but only Dev system is facing this.
The whole point of this, is why when the system is shut down in order to perform an offline backup causes this, and the only way to fix this, is shutting down/start up the system again.
If you have some ideas of what could be causing this, it's would be highly appreciated.
Martin

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

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

I am having this error pop up very frequently on some new SAP systems. This will randomly happen and keep us from being able to release transports and import them in STMS. I receive the following error:
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: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
- When I check the Transport Tool (STMS: import queue> check> transport tool) I get the following information:
timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time
out during connection setup (check that partner exists
- When checking the TP System Log I receive the same error. The RSTPTEST report does not give any additional information. SM21 shows a warning and an error:
Warning:
Communication Error, CPIC return code 020, SAP Return code 456
Dialog Process No. 000
Problem cl: SAP web AS problem
Package: STSK
Further Details:
Module Name: thxxhead
Line: 7488
Error Text: 020456
Caller: ThRecei
Error:
Problem cl: transaction problem
Package: STTO
All of these errors are only pointing to a time out. I cannot figure out why this is happening. I checked the TMS RFC connection in SM59 and they are fine. I have been able to work around this issue in 2 different ways. First, I can delete the files in the "\trans\tmp" directory on the server. Sometimes this resolves the error. Else I have to restart the system.
I need to understand where this issue is coming from and how to resolve it. It is becoming more and more frequent. Thank you for your help!

Hi,
i have had similar issues during this week. After looking for a solution everywhere i found out that i didn't set up the FQDN on this system.
Symptoms were:
se38 > RSTPTEST timed out sometimes(not always)
sm59 > TCP/IP connections > CALLTP_WindowsNT > test connections timed out sometimes (again, not always)
STMS Overview > Systems: I was not always able to distribute and activate configuration from the Domain controller via Extras > Distribute and Activate Configuration (it died on the mentioned system)
Transports failed mostly with the same error.
The error log was somewhere deep in ST11. It could not resolve our FQDN.
The solution, for me, was to add our FQDN to the WINDIR\System32\drivers\etc\hosts file.
We upgraded the kernel as well (from 7.20 patch 046 to most current) but this didn't help.
The FQDN is a concatenation of computer name and dns suffix of the network (if you have none, you can add one via rightclick on the used network adapter>ipv4>properties>Advanced>DNS tab, so in the end the host file looked like
127.0.0.1 localhost computer-name.ourSuffix.com
After this line has been added, the error stopped and the transports work again.
I hope it helps. Good luck.

Failed to execute with the error Error occurred when starting the parser: t

Dear All
I am getting this error
""A database error occurred. The database error text is: The MDX query SELECT { [DASKA1EDEL2DMLXTQ62S595QV].[DB7BP4A8AMQTUD3DPEEPS4J87] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CALMONTH].[LEVEL01].MEMBERS, [DASKFZ1TRFOLNTG78G0HH2B87].MEMBERS ), [0MATERIAL].[LEVEL01].MEMBERS ), [0PLANT].[LEVEL01].MEMBERS ), [0COMP_CODE].[LEVEL01].MEMBERS ), [0ACTDELDATE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES MEMBER_NAME, MEMBER_CAPTION ON ROWS FROM [0IC_C03/ZMATSTOCK] failed to execute with the error Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'. (WIS 10901)""
I already went to similar kind of error solution in forum,but this error is coming for one web I query,all other reports are working fine.
I already implemented note 1032461

Hi,
Under normal circumstances it should be enough to restart the connection service.
As far as we know there is no formal solution to this problem from SAP yet but restarting the connection service is much less of an interuption compared to restarting the the SIA.
Re-starting the connection service should resolve this issue. since, Connection service is only related to DeskI and Rich Client re-statrng wonu2019t impact other business objects components including java report panel.
All the Best,
Madhu....

Connect from SAP gateway to RFC server failed - Java StandAlone app X SAP RAC System

Dears,
I'm developing a Java application (RFC SERVER) with JCo3 and I need to connect to SAP RAC system.
I have configured the TCP/IP connection via transaction SM59, but when I try to start my server I face the error below (dev_jco_rfc.trc):
==========================================================================================
**** Error file opened at 20140714 112024 Brasilia Time Rel 3.0.10 (2013-08-08) [720.440]
Error: >Mon Jul 14 11:20:24,636<    RfcException: [null]
    message: Connect from SAP gateway to RFC server failed
Connection parameters: TYPE=A DEST=VSPAGUE ASHOST=cpe1601 SYSNR=01 SAPROUTER=/H/155.56.49.28 PCS=1
LOCATION    SAP-Gateway on host ld7624.dmzwdf.sap.corp / sapgw01
ERROR       hostname 'cpe1601' unknown
TIME        Mon Jul 14 16:20:25 2014
RELEASE     740
COMPONENT   NI (network interface)
VERSION     40
RC          -2
MODULE      /bas/740_REL/src/base/ni/nixxhl.cpp
LINE        193
DETAIL      NiHLGetNodeAddr: hostname cached as unknown
COUNTER     3
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
==========================================================================================
This problem happens when my app executes the line:
JCoServer myServer = JCoServerFactory.getServer(myServerName);
My system properties:
jco.client.lang=EN
jco.destination.peak_limit=10
jco.client.client=800
jco.client.passwd=********
jco.client.user=********
jco.client.sysnr=01
jco.destination.pool_capacity=3
jco.client.ashost=/H/155.56.49.28/H/cpe1601
jco.server.connection_count=3
jco.server.gwhost=/H/155.56.49.28/H/cpe1601
jco.server.progid=VSPAGUE
jco.server.gwserv=sapgw01
jco.server.repository_destination=VSPAGUE
Using SAP Logon i can connect to server cpe1601 system E16 without problems.
Please, I really need some help, because my knowledge on SAP platform is minimum.

Hi Markus,
Changing ASHOST=ld7624.dmzwdf.sap.corp as you have suggested, I got the error message: Connect to SAP gateway failed ...
As you could see, the host I'm connecting is from SAP RAC Service.
Here in our company we have only SAP Logon and my RFC Application, and I can connect to SAP remote system via SAP Logon with this settings:
System Connection Parameters
Description: SAP ECC 6.0
Application Server: cpe1601
Instance Number: 01
System ID: E16
SAProuter String: /H/155.56.49.28/H/
Below the connection information I received from SAP RAC SUPPORT for testing purposes:
    E16 System:
    SID: E16
    Client: 800
    System Number: 01
    Server: cpe1601
    Component Version: SAP ERP Central Component 6.0 Enhancement Pack 6 Suite on HANA
    User: ********
   Password: ********
   SAProuter String:
   If you don't plan to use SAPRouter at your end,
   /H/155.56.49.28/H/

Crystal report- Connect from SAP gateway to RFC server failed

Hi All,
I am trying to connect to a SAP R3 system from crystal reports but it gives me below error.
Please note : Transports have been imported and also the roles CRYSTAL_ENTITLEMENT and CRYSTAL_DESIGNER. My user is a member of these roles which were release along with Best practice reports v1.31
Error :
Logon failed.
Details: CMALLC : rc= 27 > Connect from SAP gateway to RFC server failed
Connect_pm GWHOST=10.10.4.63, gwserv=SAPGW30, SYSNR= 30
Location SAP-gateway on host ply.log.com/sapgw30
Error timeout during allocate
TIME ....
Release 700
Component SAP Gateway
Version 2
RC 242
Module gwr3cpic.c
LINE 1996
Detail no connect of TP sapdb30 from host 10.10.4.63 after 20 sec
Can you please help us solving this error.
Thanks
Chetan

Hi Stratos,
The SAP Version is ECC 6.0.
The below transports have been imported.
u2022 Open SQL Connectivity transport (K900574.r21 and R900574.r21)
u2022 Info Set Connectivity transport (K900575.r21 and R900575.r21)
u2022 Row-level Security Definition transport (K900576.r21 and R900576.r21)
u2022 Cluster Definition transport (K900585.r21 and R900585.r21)
u2022 Authentication Helpers transport (K900578.r21 and R900578.r21)
Thanks & Regards,
Chetan

Connect from SAP gateway to RFC server failed

Good day and a happy new year to you all!
I am failing to connect to my SAP BW system from BEx. The logon fails with this message:
>>>>>Start<<<<<<<<<<
Error Group
RFC_ERROR_COMMUNICATION
Message
Connect from SAP gateway to RFC server failed
Connect_PM GWHOST=10.16.64.77, GWSERV=sapgw02, ASHOST=10.16.64.77, SYSNR=02
LOCATION    SAP-Gateway on host bwsys / sapgw02
ERROR       timeout during allocate
TIME        Sat Dec 31 13:16:19 2005
RELEASE     640
COMPONENT   SAP-Gateway
VERSION     2
RC          242
MODULE      gwr3cpic.c
LINE        1785
DETAIL      no connect of TP sapdp02 from host 10.16.64.77 after 22 sec
COUNTER     2
>>>>>>>>>END<<<<<<<<<<<<
I only experience this problem when connecting using any BEx component, but, I can successfully connect to the SAP BW system from SAP gui.
Additionally, I have the service 'sapdp02' defined in the services file, both on the workstation and the server.
What could be wrong or missing in my configuration?
Regards,
Joao.

hi Joao,
check if oss note 447882 relevant
you may ask basis for help
Symptom
You want to access the customer system using the BEx Analyzer.The connenction fails:The system displays the error RFC_ERROR_COMMUNICATION.In the detail screen, the system displays message "Partner not reached" (host 192.168.4.2, service sapgw 00).
Other terms
SAP Gateway, RFC_ERROR_COMMUNICATION, partner not reached
Reason and Prerequisites
The SAP gateway host is deactivated or the TCP/IP port 33xx (where xx corresponds to the system number) is not open.
Solution
Issue statement ping <IP address> (In this example:192.168.4.2) No reply: Boot SAP Gateway host required.
An answer:Check whether the TCP/IP port 33xx is open (where xx corresponds to the system number) and start the SAP gateway.
The TCP/IP port is also partially defined in the services file as an sapgw<SID> or sapgwxx entry (where xx corresponds to the system number). The services file is in the Windows directory or in WinNT/System32/drivers/etc.

Error: Connect from SAP gateway to RFC Server failed

Hi
I am trying to connect SAP server using the java (JCO connection), and getting following error. While I am able to connect to the same sever using SAP Logon pad with the same ipaddress (hostname) and logon credentials.
Please kindly help.
Erro: Connect from SAP gateway to RFC server failed.
Connect_PM GWHOST = hostname, GWSER = sapgw03, ASHOST=hostname, SYSNR=03
LOCATION SAP-Gateway on host hostname / sapgw03
ERROR timeout during allocate
TIME Wed Oct 31 05:31:45 2007
RELEASE 640
COMPONENT SAP-Gateway
VERSION 2
RC 242
MODULE gwr3cpic.c
LINE 1795
DETAIL no connect of TP sapdp03 from host hostname after 22 sec
COUNTER 3

Hi K Patil,
Acording to me you are faceing this issue because the entry of your backend System is not in the SLD (System Landscape Directory ) of your server.
to make this work you have to make entry in the SLD of your server
fort that plesae acess this link.
Re: JCo connection Error
Re: wt is SLD.. how to do configure it
Please Reward Points if Helpfull.
Regards
Vinit
Edited by: Vinit Soni on Dec 19, 2007 7:20 AM

RFC Ping failed while making test in RFCPTEST

Hello
I successfully installed SAP NetWeaver 7.01 ABAP Trial Version under Windows XP SP3.
Problem is that when I'm trying to configure STMS, I'm getting error "Could not start transport control program tp".
Help for this error says:
Could not start transport control program tp
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: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
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.
When I perform tests with program RSTPTEST all are fine except RFC Ping.
Please help.
S.

I have the same error as what the thread starter have encountered.
Transport control program tp could not be started
Message no. TP608 Diagnosis
This is the error on the gateway trace file:
Thu Mar 19 11:09:46 2009
ERROR => R3ISearchPartner: timeout, partner LU: > <hostname> <, TP: >/usr/sap/<SID>/SYS/exe/run/tp< [gwr3cpic.c 6016]
ERROR => R3ISearchPartner: HOST: <hostname>, conv ID: 39145879 gwr3cpic.c 6029
Any idea how to solve this?
Edited by: Melvin Caceres on Mar 19, 2009 4:01 AM
Edited by: Melvin Caceres on Mar 19, 2009 4:02 AM

Failed to execute query

HI Genius,
I have designed on MDX Query. That Query is working in Crystal Report.
I have successfully exported universe from this query.
Now I want to use this universe in Query As A Web Service. I found universe of this query in QaawS.
I am able to see their fields in Build your Qurey Screen. While I am trying to give next step I am getting below error:
getDocumentInformation exception(Error: WIS 10901)
A database error occured. The database error text is: The MDX query SELECT {[ D5272819TYMKSLULVBEJECDFM].[D56FMXBBON4I2150PKSHY65TU]} ON COLUMNS, NON EMPTY [D5271SCO6VP1B3P598D4OMO2]. MEMBERS ON ROWS FROM OFIGL_C10/ZIDHA_pnl_REP1 failed to execute with the error See RFC trace file or SAP system log for more details. (WIS 10901)
Please help me ASAP.
Note: There is No Hyperlink in this document.
Warm Regards,
Rishit Kamdar

Hi,
I would suggest to post your question here [BusinessObjects Integration Kits;.
Regards,
Stratos

RFC Execution Failed - Error

Hi,
When I am trying to create MBO, RFC execution is failing. Error showing in Error log as below. SUP Version : 2.0.
java.lang.RuntimeException: Failed to execute EISOperation.
                at com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:283)
                at com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:165)
                at com.sybase.uep.tooling.eis.SapEISOperationImpl.execute(SapEISOperationImpl.java:450)
                at com.sybase.uep.tooling.ui.dialogs.preview.ExecuteSection.getRecordSet(ExecuteSection.java:289)
                at com.sybase.uep.tooling.ui.dialogs.preview.ExecuteSection.access$300(ExecuteSection.java:75)
                at com.sybase.uep.tooling.ui.dialogs.preview.ExecuteSection$3.run(ExecuteSection.java:192)
                at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: Failed to execute JCA operation
                at com.sybase.vader.da.jca.JcaInteractionOperation.execute(JcaInteractionOperation.java:171)
                at com.sybase.vader.statistics.MonitoringOperation.execute(MonitoringOperation.java:65)
                at com.sybase.vader.service.interaction.PipelineCompositeInteractionOperation.execute(PipelineCompositeInteractionOperation.java:55)
                at com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:265)
                ... 6 more
Caused by: java.lang.NullPointerException
                at com.sybase.vader.jca.sap.connector.cci.SapFunctionModuleDynamicMetadataMappedRecord.put(SapFunctionModuleDynamicMetadataMappedRecord.java:272)
                at com.sybase.vader.jca.sap.connector.cci.SapRootInteraction.execute(SapRootInteraction.java:100)
                at com.sybase.vader.da.jca.JcaInteractionOperation.execute(JcaInteractionOperation.java:145)
                ... 9 more
Help me ...

Hi,
did you try to switch to the advanced developer profile and to deactivate the result check ?
Best Regards,
Stefan
Edited by: Stefan Wawrzinek on Jan 11, 2012 12:10 PM

RFC connection failed - When using code created by "GENERATE PHP" button

Hi All,
I can use the saprfc_test.php to login, call a BAPI and return data from SAP. But on the same BAPI screen if I click the generate php button and copy the new .php file into my /htdocs/saprfc folder and execute it the browser it returns with "RFC connection failed"
I am totally stuck, please can anybody help?
Rob.

I needed to specify "MSHOST"=>"", Its strange that this was not neccessary for interactive scripts but the problem is solved

RFC SAPDB_DBM fails to execute sapdbmrfc: timeout durring allocate

Similar Messages

Maybe you are looking for