cancel
Showing results for 
Search instead for 
Did you mean: 

SAP.Connector.RfcCommunicationException

Former Member
0 Kudos

When call SAPProxy function, a SAP.Connector.RfcCommunicationException raised

Please help me to analysis the cause and solution.

My doubt is if the Gateway is indispensible for a .NET Connector function call

Thanks in advance

Detail information:

Exception.Message:

Connect to SAP gateway failed\n

Connect_PM GWHOST=157.55.20.224, GWSERV=sapgw00, ASHOST=157.55.20.224, SYSNR=00\n\n

LOCATION CPIC (TCP/IP) on local host\n

ERROR partner not reached (host 157.55.20.224, service 3300)\n\n

TIME Thu Dec 09 13:13:01 2004\n

RELEASE 620\n

COMPONENT NI (network interface)\n

VERSION 36\n

RC -10\nMODULE ninti.c\n

LINE 979\n

DETAIL NiPConnect2\nSYSTEM CALL SO_ERROR\n

ERRNO 10060\n

RRNO TEXT WSAETIMEDOUT: Connection timed out\n

COUNTER 1\n

The code lines as following:

string cs = "ASHOST=157.55.20.224 SYSNR=00 CLIENT=000 USER=xxxx PASSWD=xxxxxx";

// construct the proxy with connection string

SAPProxy1 proxy = new SAPProxy1(cs);

// create a SAP Table variable

BRFCKNA1Table tblCust = new BRFCKNA1Table();

// call the RFM method on the proxy

try

{

proxy.Rfc_Customer_Get("","A*", ref tblCust);

}

catch(SAP.Connector.RfcCommunicationException exp)

{

MessageBox.Show(exp.Message);

return;

}

Accepted Solutions (1)

Accepted Solutions (1)

reiner_hille-doering
Active Contributor
0 Kudos

There seems to be some(network) problem to connect your SAP server. Try "ping 157.55.20.224". If this works also try "telnet 157.55.20.224 3300".

Might be that your SAP server is behind a SAPRouter. In this case you need to put the SAPRouterString in fron of the ASHOST parameter in connection string.

Former Member
0 Kudos

Thank you for your prompt answer.

Our R/3 Server is located at just the same LAN and same ip subnet. e.g. I access it from 157.55.20.221

But the telnet 157.55.20.224:3300 command do not success.

I suspect our system missing some component which has not been instatlled.

How to verify my suspect?

reiner_hille-doering
Active Contributor
0 Kudos

Then it's likely that your system number is NOT 0, because Gateway port is allways calculated as 3300+SystemNumber.

Former Member
0 Kudos

Thank you again.

the system number is 0, we use this number to connect SAPGUI to the R/3 system. And the BOR and RFC functions can be browsed in Server Explorer. I think the system number has no problem.

If there is any problem with the connections string?

reiner_hille-doering
Active Contributor
0 Kudos

If Server Explorer is working you best drag the server node to a Forms or Component designer to create and initialized Destination and take this to connect.

Former Member
0 Kudos

Your first answer already address the problem.

Finally I found the firewall cause the problem, similar to a gateway difficulty.

Thank you very much for your patient explanations.

Former Member
0 Kudos

Hi Reiner,

One of my partners are having this problem...

1. They are having a dev server of ip 200.1.12.xx and remote site has network with ip 171.xxx.xxx.xxx

2. Another subsidiary needs to use NCo to access this server

3. They are using two firewalls, one from Buiding A and another in Building B

4. all ports of firewalls are open, there IP mapping from firewall in Building A to IP in firewall in Building B.

5. Building A being the remote building, can log on via SAP GUI, however, unable to connecto via NCo

6. What seems to be the problem and what can I tell the basis guy to check?

How does NCo support firewalls and waht is the best way to work around this?

Your help is much appreciated.

Cheers

reiner_hille-doering
Active Contributor
0 Kudos

RFC (and thus NCo) is just using TCP connection on port 3300+SystemNumber. Best test is allways "telnet <host> <port>". If this works, NCo should work as well.

BTW: SAPGUI is using port 3200SystemNumber. If you use LoadBalancing via Message-Server you also need the MessageServer-Port. This is not fixed, but often it is 3600SystemNumber.

Answers (0)