on 11-02-2005 9:43 AM
Hello,
we have a SAP/R3 system (QW8) which we bound to an WebAS successfully ( that means that RFC call via rz70 was successful and system was added to technical landscape also).
When we try to create JCo connection, we get the following
Failed to ping JCo destination 'test2'.
or
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=pwdf0672 GROUP=PUBLIC R3NAME=QW8 MSSERV=sapmsQW8 PCS=1 ERROR partner not reached (host 10.17.73.95, service sapmsQW8) TIME Wed Nov 02 10:41:00 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8634 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
The system is there, we can ping it via cmd line and we added sapmsQW8 3225 to the services file also. The PUBLIC group does also exist.
When we used rz70 we took "localhost" and "sapgw25" as params.
So maybe anybody can help us out with that,
Clemens
Hi Dharmi,
so after a little bit of work - I tried to bind an other system (QB8)... it also only worked in single server connection, not with metadata nor with load-balancing. It gives me the same error - partner not reached.
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
Best would be to open an OSS message. I am curious to know:
1. Did you look into all the links that i sent you? Did you try to trace?
2. Did u try by specifing SAPRouter? (as mentioned in the link)
3. Did you check the SLD Data Supplier for ABAP?
4. Do you have a J2EE engine also to make an RFC connection?
Best regards,
Dharmi
Dharmi,
Thank you for your help - I was also off till today... So I restarted the whole a thousand times - no effect.
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
Hereby a help on SLD :
http://help.sap.com/saphelp_nw04/helpdata/en/15/b4ba8f207a40ab8d28165cf3b04de4/frameset.htm
till then I would try to catch hold of tech guy.
Regards,
Dharmi
Hello again,
I spoke to a tech staff member and here is the result:
We were able to telnet our R/3 system on port 3325 by
telnet 10.17.73.95 3325, but not with port 3625.
According to him, there are no firewalls etc. between both systems and the question/suggestion was to check, if there is an application on R/3 that waits for 3625 and if so, why does this app not respond and I should check while in R/3 if there is a log somewhere saying that I am expected at 3625...question now is: does that help further? How can I check that?
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
Sorry for the delayed reply. Since I am working from home I cannot answer your questions at this moment but would be able to do that only on Monday.
One thing that I noticed most people advicing on SDN was to restart your server after you put entry in the services file. Did you restart after you got the Binding right? That mite help since with the last post of yours I did not see any post / anyone asking you to restart the server. Do let me know if it helped
Have a nice weekend.
Regards,
Dharmi
Message was edited by: Dharmi Tanna
Hello Clemens,
No tech guy. I am able to telnet our message server. You can try to trace / have a look at the log by following this link:
http://help.sap.com/saphelp_nw04/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
JCO_ERROR_COMMUNICATION / RFC_ERROR_COMMUNICATION :
Exception caused by network problems, connection breakdowns, gateway problems, unavailability of the remote SAP system, etc.
-get the host of the SAP System from dev_jrfc.trc or the JRFC trace; ping the SAP system from command line; check routers, gateways, SAP systems
Best regards,
Dharmi
Hi Dharmi,
I tried this - it is not possible to connect.
I'll await what the tech-staff says and then let's see...
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dharmi,
so I tried telnet - connection (on port 23) is not possible. So I should have a word with our tech-staff here,maybe?
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dharmi,
I took "localhost" (I got that from rz70) and tried again,
the app-data works , meta-data doesn't.
I have pwdf0672 as central app server and
pwdf0721 as secondary - does that influence it?
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
I just spoke about your problem to the technical person here, he suggested that "Partner not reach error" that you get could be because of the firewall, he also suggested if you could telnet the message server and see if that works?
The reson for not getting that error in the Apllication data according to him is bcos the Application data goes via GUI.
Can you try telnet?
Best regards,
Dharmi
Hi Bala,
so I did what you suggested - even if I assumed that all the settings should be perfectly done when running rz70 on the R/3 system - no change, error appears nevertheless.
What I am wondering about is that this only appears with meta_data connections and when I try to use load-balanced connections... if I use single server connection with application data JCo it just runs fine.
Is there possibly an issue when using a VPN within the network?
Regards,
Clemens
PS: Is there a way to add the logon group afterwards?
Message was edited by: Clemens Leider
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you , Bala!
Could you tell me how and where I add the group?
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure.
I guess you might have set up an ABAP stack already as you are using different server for accessing R/3. Anyways, here are the steps to set-up an ABAP stack in SLD.
1)open the URL http://<hostname>:<httpportnumber>/sld/index.jsp
2)Click <b>Administration</b> tab and select <b>Import</b> under the Content flag.
3)Specify the path to the suitable CR-Content file (zip file:CRCONTENT13_0_10002694.zip for web AS 6.20)and click Import.The file upload will take some time.Wait until the file gets uploaded successfully.
4)Click <b>Home</b> tab and choose <b>Technical Landscape</b>
5)Choose "<b>Web AS ABAP</b>" from the Technical System Type drop down.
6)Click "<b>New Technical System</b>".You'll get a pop-up
7)Choose "<b>Web AS ABAP</b>" in the "<b>Technical System Wizard</b>" (pop-up)
8)Choose <b>Next</b> and specify all the relevant details of the R/3 system to which u r connecting.
9)Choose <b>Next</b> and specify all the required details for your Application Server and Message Server.(Add a group called <b>PUBLIC</b> to the Log On Groups)
10)Click <b>Next</b> and specify the <b>Hostname</b> of the App Server and click "Add".
11)Click <b>Next</b> and specify the "<b>Client Number</b>" and its "<b>Logical Name</b>".
12)Choose <b>Nex</b>t and select "<b>SAP WEB AS 6.</b><the version number of the AS>".Click "Add" . By default all the components will get selected. Just Scroll down the wizard and click "<b>Finish</b>".
Your Jco destinations should work now.
Bala
Hello Dharmi,
yes - the WAS and the R/3 system do run on different servers within the same network. I can ping both of them sucessfully from command line - so they are there and reachable ( and I do not get the point why it says "partner not reached" as in Single Server Connection it works, doesn't it?)
Regards
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
Yes, you are right in the single server connection it does work. With Dictionary metadata by default it is load balancing, I would however ask you to try one more thing:
In the 4th step where you select the message server just try to give the SAP router and that you can pick up from rz70 (hostname).
Let me know what happens!
Best regards ,
Dharmi
Hello Dharmi,
I thank you for your help again - here is what I expirienced just now (by try-and-error):
When I create an Application Data Connection and choose "Single Server Connection" instead of the load-balanced one, then it works perfectly! I can test it and ping it sucessfully...does that recall any idea in you?
When I create a Meta-Data-Connection then still the error
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=pwdf0672 GROUP=PUBLIC R3NAME=QW8 MSSERV=sapmsQW8 PCS=1 ERROR partner not reached (host 10.17.73.95, service sapmsQW8) TIME Wed Nov 02 13:59:11 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8625 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
comes up.
kind regards,
Clemens
Message was edited by: Clemens Leider
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
Congratulations. Thatz what I told you in the early post "assuming you selected single server connection".
Now the next part,
Assuming you have used the same steps as of ModelData still a checklist:
1. client 100
2. Local engine
3. Dictionary Data -> No selection of server is possible here, by default load balance.
4. Message Server -> ****IMP*** if you select the message server name form the dropdown list it should come up automatically with the Logon Group name***** Does this happen???
5. Lastly, password in capital
Best regards,
Dharmi
Message was edited by: Dharmi Tanna
Dharmi,
I did as you wrote - I can select the messageserver and as Logon Group PUBLIC this goes automatically - giving username and pw in capital gives me the following
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=pwdf0672 GROUP=PUBLIC R3NAME=QW8 MSSERV=sapmsQW8 PCS=1 ERROR partner not reached (host 10.17.73.95, service sapmsQW8) TIME Wed Nov 02 14:26:14 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8625 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 2
kind regards,
Clemens
Hi Dharmi,
If I test the SLD Connection ( Check SLD Connection - Test Connection ) then it gives me it was successfully tested. So that seems to work.
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
It is surprising that both application and dictionary data doesn't work. Application data is one which always works on the first creation itself.
Sorry I cannot think of other possibilities to your problem. Somebody from SAP needs to help you.
Best regards,
Dharmi
PS Just one suggestion, try to use meaningful names like TEST_MODELDATA or TEST_RFC_METADATA and Good Luck.
Hi Dharmi,
I appreciate your help very much!
So I created a JCo "test3" with Client 100 and I checked "Use local Engine" and it is an "Appl.Data" Connection
I provided my username and password in capitals of the R/3 system and Group is PUBLIC.
The ping fails and when testing it gives:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=pwdf0672 GROUP=PUBLIC R3NAME=QW8 MSSERV=sapmsQW8 PCS=1 ERROR partner not reached (host 10.17.73.95, service sapmsQW8) TIME Wed Nov 02 11:25:20 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8625 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
When I set up the same thing wit "Dictionary Meta Data" it says:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=pwdf0672 GROUP=PUBLIC R3NAME=QW8 MSSERV=sapmsQW8 PCS=1 ERROR partner not reached (host 10.17.73.95, service sapmsQW8) TIME Wed Nov 02 11:27:37 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8625 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dharmi,
As I said - the RFC works ( when using it via rz70) but when I create JCo Connections I can't ping the system -
Failed to ping JCo destination 'test2'.
When testing the JCo Connections I get the error as above.
Regards,
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Clemens,
I perfectly understand that from RFC it works and doesn't work with Jco!
Can we try to look into the details and find the cause?
1. The Status is green so you get the option to ping or test the connection, the name test2 does not tell me whether it is a ModelData or MetaData type of connection so Can you please answer to that first?
If the above is clear to me we can look into further details. There mite be one minute detail that you mite be overlooking so if we work together step by step we can solve it.
Best regards,
Dharmi
Hello Clemens,
Both the Jco Connections are not working???
Best regards,
Dharmi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.