on ‎2009 Jan 27 6:15 AM
Hi
I have created a RFC with type T. When I am testing the same through SM59, I am getting error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program <program name>not registered
Error Details LOCATION: SAP-Gateway on host xxxxxx / sapgw01
Error Details DETAIL: TP <program name> not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 6268
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Tue Jan 27 00:56:55 2009
Error Details VERSION: 2
Can anybody help me in this?
Thanks in advance
Request clarification before answering.
Hi Basis Experts
I am having problems while testing an RFC connection PI_RFC in one of our PI quality system.
Here is the Error log
Logon Connection Error
Error when opening an RFC connection
ERROR: program PI_RFC not registered
LOCATION: SAP-Gateway on host bp1xeuaa202 / sapgw01
DETAIL: TP PI_RFC not registered
Details COMPONENT: SAP-Gateway
COUNTER: 15866
MODULE: gwr3cpic.c
Details RETURN CODE: 679
We tried restarting the JCO-RFC provider service in VA,also tried restarting the Gateway service, tried registering the RFC using below command
rfcexec u2013g PI_RFC -a bp1xeuaa202 -x sapgw01
rfcexec u2013D PI_RFC
the command didnt gave any output also in SMGW tcode we didnt get the entry(PI_RFC) under system type as registered server.
Still we are facing the same issue, can anyone please help us in resolving this issue.
Regards
Syed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sanjay
We have already done with putting gateway hostname and service,still same issue. however we have not maintained the JCO RFC in VA but this is to inform u for all other systems we have not created the particular JCO RFC in VA but still that is working fine.
Please suggest anything else if we can check?
Regards
Syed
Hi,
I have faced the same issue and this is because of new security parameter set for Gateway server.
Please refer to Note 1480644 - gw/acl_mode versus gw/reg_no_conn_info. You can resolve this issue by setting ABAP Parameter gw/acl_mode = 0 in your BW / BI system or following the instructions mentioned in the note .
Regards
Bhupesh Akkineni
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 6 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.