cancel
Showing results for 
Search instead for 
Did you mean: 

call tp connection error in sap ides ecc6.0

Former Member
0 Kudos

hi

we recently install ecc6.0 ides on windows2003 ,mssql2005 database....i got error when checking rfc connection with sm59

when i check i got this error connection test  CALLTP_WINT FAIELD

HOW TO RESOLVE THE ISSUE?

Accepted Solutions (0)

Answers (5)

Answers (5)

farkathulla_cikkanther
Active Participant
0 Kudos

Hello,

  there might be reason for environment variable fault.  please check your environment variables

DBMS_TYPE=MSS

MSSQL_DBNAME=sid

MSSQL_SCHEMA=sid

MSSQL_SERVER=host name

SAPEXE=sap exe directory path.

SAPLOCALHOST=HOST NAME

SAPSYSTEMNAME=SID

if you find any fault over there please correct or create a new environment variable like above and run ntenv2reg in sapexe directory which will store this values in registry then Restart and try again. If you have fine working system means please compare this variables.  May this will help you.

Regards,

Farkath C

Former Member
0 Kudos

Hi,

Since it is IDES system SAP is going to provide all demo data and some demo RFC destinations. Try to check which system it is trying to communicate?(Mostly which ever system it is pointing it will not be available in your network). Just try to configure system as single system(domain controller) and check the issue.

Regards

Praveen

Former Member
0 Kudos

Hi,

Can you please attach the error screenshot?

THanks and Regards,

Vimal

Former Member
0 Kudos

Hi,

Which RFC connection you are checking.

Please let me know the RFC and attach the error screen shot.

Thanks

Kishore Cherukumalla

Former Member
0 Kudos

this is the  error screen shot for the problem

JPReyes
Active Contributor
0 Kudos

Check the developer trace dev_tp and post error messages here.

Regards, Juan

Former Member
0 Kudos

Hi Juan

thanks for the rpelay .. i was trying locate dev_tp.on in this path E:\usr\sap\AA4\DVEBMGS00\work....

but there is no file in the name dev_tp...

so how can i find the file

regards

vreddy

AtulKumarJain
Active Contributor
0 Kudos

Hi Vreddy,

Please check the dev_rd log as it is showing there is issue with gateway.

you can check gateway status in t-code smgw.

if it is not running you can start it

please check below link for more info

http://help.sap.com/saphelp_nw04/helpdata/en/bb/9f13194b9b11d189750000e8322d00/content.htm

Best Regards,

Atul

Former Member
0 Kudos

Hi atul

thanks for the replay, this is log file for dev_rd... i find some error how to trouble shoot?

---------------------------------------------------

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

---------------------------------------------------

Thu Mar 21 14:49:27 2013

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

systemid   562 (PC with Windows NT)

relno      7000

patchlevel 0

patchno    137

intno      20050900

make:      multithreaded, Unicode, 64 bit, optimized

pid        3276

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

gateway (version=700.2007.10.01)

gw/local_addr : 0.0.0.0

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Bind service sapgw00 (socket) to port 3300

GwPrintMyHostAddr: my host addresses are :

  1 : [192.168.1.159] aafour (HOSTNAME)

  2 : [127.0.0.1] aafour (LOCALHOST)

  3 : [25.33.150.4] aafour (NILIST)

Full qualified hostname = aafour

DpSysAdmExtCreate: ABAP is active

DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

DpShMCreate: sizeof(wp_adm)                    25168          (1480)

DpShMCreate: sizeof(tm_adm)                    5652128          (28120)

DpShMCreate: sizeof(wp_ca_adm)                    24000          (80)

DpShMCreate: sizeof(appc_ca_adm)          8000          (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm)                    552080          (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)                    0          (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)                    0          (72)

DpShMCreate: sizeof(vmc_adm)                    0          (1864)

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

DpShMCreate: sizeof(gw_adm)          48

DpShMCreate: SHM_DP_ADM_KEY                    (addr: 000000000F250050, size: 6348592)

DpShMCreate: allocated sys_adm at 000000000F250050

DpShMCreate: allocated wp_adm at 000000000F252150

DpShMCreate: allocated tm_adm_list at 000000000F2583A0

DpShMCreate: allocated tm_adm at 000000000F258400

DpShMCreate: allocated appc_ca_adm at 000000000F7C2060

DpShMCreate: allocated comm_adm at 000000000F7C3FA0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000F84AC30

DpShMCreate: allocated gw_adm at 000000000F84ACB0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000F84ACE0

MtxInit: -2 0 0

Thu Mar 21 14:53:35 2013

GwDpInit: attached to gw_adm at 000000000F84ACB0

***LOG Q0I=> NiIRead: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 4424]

*** ERROR => NiIRead: SiRecv failed for hdl 2 / sock 484

    (SI_ECONN_BROKEN/10053; I4; ST; 192.168.1.159:4877) [nixxi.cpp    4424]

*****************************************************************************

*

*  LOCATION    SAP-Gateway on host aafour / sapgw00

*  ERROR       connection to partner 'aafour:4877' broken

*

*  TIME        Thu Mar 21 14:53:35 2013

*  RELEASE     700

*  COMPONENT   NI (network interface)

*  VERSION     38

*  RC          -6

*  MODULE      nixxi.cpp

*  LINE        4424

*  DETAIL      NiIRead

*  SYSTEM CALL recv

*  ERRNO       10053

*  ERRNO TEXT  WSAECONNABORTED: Software caused connection abort

*  COUNTER     1

*

*****************************************************************************

*** ERROR => GwIRegProg: GwRead failed (NIECONN_BROKEN) [gwxxrd.c     15663]

***LOG Q0I=> NiIRead: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 4424]

*** ERROR => NiIRead: SiRecv failed for hdl 2 / sock 484

    (SI_ECONN_BROKEN/10053; I4; ST; 192.168.1.159:4914) [nixxi.cpp    4424]

*****************************************************************************

*

*  LOCATION    SAP-Gateway on host aafour / sapgw00

*  ERROR       connection to partner 'aafour:4914' broken

*

*  TIME        Thu Mar 21 14:53:35 2013

*  RELEASE     700

*  COMPONENT   NI (network interface)

*  VERSION     38

*  RC          -6

*  MODULE      nixxi.cpp

*  LINE        4424

*  DETAIL      NiIRead

*  SYSTEM CALL recv

*  ERRNO       10053

*  ERRNO TEXT  WSAECONNABORTED: Software caused connection abort

*  COUNTER     2

*

*****************************************************************************

*** ERROR => GwIRegProg: GwRead failed (NIECONN_BROKEN) [gwxxrd.c     15663]

regards

vreddy

AtulKumarJain
Active Contributor
0 Kudos

Hi Vreddy,

It seems there is issue with network.

you can check with your network team and please check  SAP Note No. 500235

Best Regards,

Atul

Former Member
0 Kudos

Hi

thanks for the replay i thing it was not net work programe...

Check the basic functionality of the NI-layer

---------------------------------------------

To perform a self test on the local host start niping with

option -t. The last line of the output should contain

"*** SELFTEST O.K. ***" if no problems occured.

C:\Documents and Settings\aa4adm.AAFOUR.000>niping -s -10

Test Program for NI-Layer (network interface), Version 38, October 18 2004

running modes

start server     niping -s

start client     niping -c

self test        niping -t

verify nodeaddr  niping -v

additional options

-H hostname    name of server-host                   (default localhost)

-S service     service-name or port-number           (default 3298)

-K sncname     SNC-name server                       (default no SNC)

-B bufsize     size of data-buffer                   (default 1000)

-L loops       number of loops                       (default 10)

-V tracelev    trace level (0 - 3)                   (default 1)

-T tracefile   name of trace file                    (default stdout)

-I idle time   maximum idle time                     (default 300 sec)

               t > 0  shutdown after t secs idle

               t = 0  no automatic shutdown

               t < 0  shutdown after -t secs idle or

                      first client disconnect (server only)

-R             raw mode

-P             detail print

expert options

-N timeout     for completion of fragmented packages (default 200 msecs)

-O             one way mode

-Q maxbytes    fragment test mode

-D delay       delay between sends                   (default 0 msec)

Check network connection between host A and B on NI-level

---------------------------------------------------------

Start niping as a server (option -s) on host A. Then start

niping as a client (option -c) on host B.

The client sends <loops> packets of size <bufsize> which are

echoed by the server. The client then displays the average,

maximum and minimum round trip time.

Check the basic functionality of the NI-layer

---------------------------------------------

To perform a self test on the local host start niping with

option -t. The last line of the output should contain

"*** SELFTEST O.K. ***" if no problems occured.

C:\Documents and Settings\aa4adm.AAFOUR.000>

theser are niping details

regards

vreddy

JPReyes
Active Contributor
0 Kudos

Can you post the SM59 test error?

Regards, Juan