on 03-30-2016 8:40 AM
Hi Experts,
is there anything to consider after switching from saplogon.ini to the new SAPUILandscape.xml concept?
We do have a customer using BEX-Analyzer. Since moving from SAPGui 730 (saplogon.ini) to SAPGui 740 (SAPUILandscape.xml) he faced issues when using SNC protected GUI-entry using BEX-Analyzer.
SAPGui is working fine with SSO.
Error is like this:
____________________________________________________
RFC_ERROR_COMMUNICATION
Nachricht
SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM GWHOST=x.x.x.x, GWSERV=sapgwxxs, SYSNR=00
LOCATION CPIC (TCP/IP) on local host
ERROR partner ‚x.x.x.x:4800' not reached
TIME Mon Nov 16 14:18:48 201x
RELEASE 740
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE D:/depot/bas/740_REL/src/base/ni/nixxi.cpp
LINE 3324
DETAIL NiPConnect2: x.x.x.x:4800
SYSTEM CALL connect
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection t
____________________________________________________
Any idea, what this error means?
Using the same with SAPGui 730 works fine.
I will be able to figure this out onsite tomorrow, any help appreciated
Thanks,
Carsten
PS: Port 4800 is blocked by Firewall. It was never open before and the same does work with SAPGui 730
Hi Carsten,
SAP corrected a bug with 7.40.
BEx uses RFC. Insecure RFC port is 33xx, secure (SNC based) RFC port is 48xx. For a long time Bex used insecure port 33xx for SNC based RFC connection.
This was corrected but does not seem to be well documented.
So the correct solution is: Open port 48xx in your firewalls and add it to saprouttabs if necessary.
Regards,
Lutz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.