Symptom
RFC Destination (normally, involved RFC is CALLTP_<OS>) fails; this can be checked by making a Connection Test on transaction SM59:
Work process trace file (dev_w<nr>) contains the following information:
M *** ERROR => ThCPICArgs: NiAddrToHost failed [thxxcpic.c 7402]
A RFC xxxx CONVID xxxxxxxx
A * CMRC=0 DATA=0 STATUS=0 SAPRC=0 ThCPICArgs Illegal CONVID
A RFC> ABAP Programm: xxxxxx (Transaction: SM59)
A RFC> User: <user name> (Client: <cln>)
A RFC> Destination: <RFC Name> (handle: 2, DtConId:
5550D4F5B2C906E0E10080000AC0A823, DtConCnt: 0, ConvId: ,)
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1792
CPIC-CALL: 'ThCPICArgs'
Illegal CONVID
[abrfcio.c 9193]
Error shown can also be:
Connection Error
Error when opening an RFC connection (CPIC-CALL: 'ThCPICArgs' Illegal CONVID ).
ERROR: hostname ‘hostname’ unknown
LOCATION: SAP-Server <server_name>_<SID>_<nr> on host < server_name> (wp <nr>)
DETAIL: NiPGetHostByAddr: ‘hostname’ not found
Error Details CALL: getnameinfo
Read more...
Environment
RFC is defined as Type T (TCP/IP connections), and "Technical Settings" on "Activation type" tab is configured as "Start on Application Server" or “Start on Explicit Host”:
Keywords
KBA , BC-CST-NI , Network Interface , BC-MID-RFC , RFC , BC-NET , Obsolete - Formerly used for network tests , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.