cancel
Showing results for 
Search instead for 
Did you mean: 

TCP/IP RFC destination

Former Member
0 Kudos

Hello all,

i am getting error when am testing T type connection

Connection error Error opening an RFC connection.

for example

error description

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

[Thr 218] * LOCATION SAP-Gateway on host s96sxicg.edc.corpintra.net / sapgw00

[Thr 218] * ERROR registration of tp AI_DIRECTORY_SXI from host s96saptg not

  • allowed

[Thr 218] *

  • TIME Tue Jan 13 02:30:50 2009

[Thr 218] * RELEASE 640

[Thr 218] * COMPONENT SAP-Gateway

[Thr 218] * VERSION 2

[Thr 218] * RC 720

[Thr 218] * MODULE gwxxrd.c

[Thr 218] * LINE 3521

[Thr 218] * COUNTER 2745

[Thr 218] *

[Thr 218] *****************************************************************************

[Thr 218] *** ERROR => SAP_CMACCPTP: wrong rqtype SAP_ACCPTP [r3cpic_mt.c 9257]

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

what actually it looks for?

prgram id mentioned in SAP level and visual admin is same

i hope it only looks for program id in source and destination and gate way details

not only for this destination am getting error for some other destinations which are using gateway

Thanks

Ramesh reddy

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi ramesh ,

Plz check both systems user Ids type.

Regards,

Prabaharan B

Former Member
0 Kudos

Hello Ramesh,

can you stop and start the JCO once on Visual Admin.

Also check the gateway information on JCO defined on Visual admin.

If this doesn't work.

on ABAP go to SMGW -> go to logged on clients and check for errors.

Probably Gateway would have reached max connections too.

Try restarting the Gateway service once which will fix the issue.

Regards

Vivek

TomCenens
Active Contributor
0 Kudos

Dears

For future reference / searches of other community members:

registration of tp AI_DIRECTORY_SXI from host s96saptg not allowed and wrong rqtype SAP_ACCPTP point out that the gateway is not allowing the connection thus the security settings are the cause of this.

Please refer to:

Note 1434117 - Bypassing sec_info without reg_info

Note 1444282 - gw/reg_no_conn_info settings

Note 1298433 - Bypassing security in reginfo & secinfo

http://help.sap.com/saphelp_nw70ehp3/helpdata/en/e2/16d0427a2440fc8bfc25e786b8e11c/content.htm

Check parameter setting gw/reg_no_conn_info in your managed SAP system as well as gw/reg_info and gw/sec_info and maintain the reginfo and secinfo file

reginfo


TP=* HOST=*

secinfo


TP=*, USER=*, HOST=*, USER-HOST=*

The above allows everything. You can use this as start point. You have to restart your gateway to apply the change. You can restart your gateway by killing the gwrd process, don't use kill -9 as you want it to auto-restart. Of course connections that have been made are lost when you restart your gateway.

Check log files dev_rd on the SAP system where your gateway resides and dev_server0 on an AS Java based SAP system that connects using JCO destinations to a ABAP based gateway.

Kind regards

Tom



Former Member
0 Kudos

Tom,

Thanks for that post (and all of your blogs that I just found!!). 

I was curious if you might have any insight into what seems like an anomaly related to the gateway.  I've recently refreshed an EHP6 sandbox system from development.  The kernels are equal between the two (720EXT #327) as should be the profiles.  I've certainly checked all of the gw* parms.  I'm attaching the gateway parms from SMGW (edited the hostname).

The issue is that the sandbox seems to have some additional pieces in the secinfo and reginfo "internal defaults" that are not in the dev system. Neither have these parms set.

When I display in the dev system (reginfo in this case but the same behavior for secinfo):

#VERSION=2

#

# file E:\usr\sap\DEV\DVEBMGS00\data\reginfo.DAT not found, use internal default

#

P TP=*

However, in the sandbox system:

#VERSION=2

#

# file E:\usr\sap\DVX\DVEBMGS00\data\reginfo.DAT not found, use internal default

#

P TP=* HOST=local

P TP=* HOST=internal

This has the result that the SLD registration from a Java stack is denied.

To 'get around' this issue for the sandbox I will create the two files - but was curious if you have any feedback?

Thanks ahead of time!

Former Member
0 Kudos

Hi

what you are saying is right it will only look for programme id

check the user id for both the RFC's if possible reset the passwords

Thanks

Uday

Former Member
0 Kudos

Everything is correct userid,password,program id,gate way details

i tried to created another RFC destination with same Program id in source and destination but sill same error repeats

Regards

Ramesh reddy

Former Member
0 Kudos

Hello guys, I'm getting the same error. Did you solve this problem anyway?