-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC_COMMUNICATION_FAILURE #291
Comments
Hello @CodingQueries2023, docker port is irrelevant for RFC connection configuration. Please check similar questions
|
Hi @bsrdjan , Could you please suggest how to debug or go about this issue |
Which connection parameters are you using and did you already test with niping: |
Hi @bsrdjan , I am using these parameters: Could you please let me know if there is any issue with the parameter or if need to change anything here. |
GWSERV is used for server connections. in combination with GWHOST, not ASHOST. I cannot help with connection parameters' details because it depends on your ABAP system settings. Connection parameters are documented in sapnwrfc.ini file, in SAP NW RFC SDK folder "demo". There you may find when and how to use which parameter. You can also check with your ABAP system admin. If you have access to SAPGUI client, you can use the same parameters used in SAPGUI client for your ABAP system. |
Please re-open if needed |
On server I am getting the error RFC_COMMUNICATION_FAILURE and it is automatically trying to connect to our IP with PORT 3300, which is a wrong port. My correct PORT is 3629 but instead of 3629 it is trying to connect to 3300 and is getting failed to connect to. In my docker file I have mentioned the PORT 3629 and not 3300. Is there anything that you can suggest about the issue?
The text was updated successfully, but these errors were encountered: