Solution : https://service.sap.com/sap/support/notes/44946 (SAP Service marketplace login required)
Summary :
When a frontend component (e.g., ALE Organisational Architect, FI-LC Excel Reporting) fails during RFC LOGON despite a functioning network connection indicated by an operational SAPGUI, it often suggests issues with network configuration setup. Users should verify connectivity with SAPGUI and adjust the TCP/IP settings as outlined in the OSS under BCNET. Specific attention should be paid to the HOSTS and SERVICES files on the PC, ensuring entries for the SAP Gateway and the frontend’s hostname are properly configured to facilitate successful RFC communication. Additionally, generating RFC trace files and using tools like NIPING.EXE can help diagnose and resolve connectivity problems.
Key words :
services file defines logical port names, respective tcp/ip software stores, fi-lc excel reporting, sapdpxy 32xy/tcp xy, business application component bcnet, logical computer names, tcp/ip software, sapgwqr 33qr/tcp, hosts file defines, remote function call
Related Notes :
| 96907 | SPAM Error: TP_CANNOT_CONNECT_SYSTEM CHECK_REQUIREMENTS |
| 84114 | Modeless F1 help is not started correctly |
| 81846 | Desktop integration: Information & documentation |
| 70597 | InSight: logon to R/3 does not work |