- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI am trying to connect to an SAP server through StartRFC.exe. It is called from a custom commandline app and the parameters are passed through a config file. We have two servers setup; one for development and QA and the other is production.
The purpose of calling StartRFC is to load an idoc file into SAP. The file is copied from our windows box to the unix box containing SAP through samba. Once the file is copied startrfc is invoked from the windows box.
Now on the develompent server we do not have any issues but, when we switch over to production we have connection issues. The following is the error msg:
Error:
RFC Call/Exception: open
Group Error group 102
Key RFC_ERROR_COMMUNICATION
Message Connect to SAP gateway failed
Connect_PM DEST=PRD, GWHOST=ourserver, GWSERV=sapgw00, ASHOST=ourserver, SYSNR=02
LOCATION CPIC (TCP/IP) on local host
ERROR partner not reached (host ourserver, service 3300)
TIME Mon Feb 09 10:44:48 2009
RELEASE 620
COMPONENT NI (network interface)
VERSION 36
RC -10
MODULE ninti.c
LINE 976
DETAIL NiPConnect2
SYSTEM CALL SO_ERROR
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 1
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ButtonDownBobbyPosted on 2009-03-03 at 06:02:54ID: 23783757
Found out what was going on here. In the StartRFC.exe parameter there is a one parameter "-x" which is "gateway service" The "service definition name" was pointing to a port number that was not being used. Instead another port number was assigned to accept the remote commands. The one that was correct had it's own "service definition name" and all we had to do was change it in the parameters. I had one of our unix guys who had access to the box go through this for me so i'm a little lite on the details here. He did mention he had a script that mapped a process to the port and found out that the port # in the error did not match the port that was discovered. Hope this helps someone else.