• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 10570
  • Last Modified:

SAP - StartRFC partner not reached

I 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
0
ButtonDownBobby
Asked:
ButtonDownBobby
1 Solution
 
ButtonDownBobbyAuthor Commented:
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.
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now