on 08-12-2012 11:14 PM
.[cf=com.sap.security.core.persistence.datasource.imp.R3Persistence][md=searchPrincipalDatabags()][cl=null]#J2EE_GUEST#0##78E667C6E10211E1BA330015179469EE#44B98735E11A11E19D3D000000B4605E-0#78e667c6e10211e1ba330015179469ee#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Java###An exception was thrown in the UME/ABAP user management connector. This exception might be caused by incorrect user input. It is written to the trace to assist incident analysis by SAP. Only messages also appearing in the log require administrator assistance.
[EXCEPTION]
{0}#1#com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=01 GWHOST=localhost GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '127.0.0.1:sapgw01' not reached
TIME Wed Aug 8 07:31:13 2012
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3286
DETAIL NiPConnect2: 127.0.0.1:3301
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 77
at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.execute(R3JCo640Proxy.java:473)
at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserExistenceCheck(R3Persistence.java:7895)
at com.sap.security.core.persistence.datasource.imp.R3Persistence.getExistenceCheckResult(R3Persistence.java:2749)
at
Hi All,
Thank you for your suggestions. The issue reason has been tracked and resolved. There was a line in server0 log, where there was a reference to sql connection line and a tablespace reference. On further investigation it was found that PSAPSR3DB tablespace was full.
After extending the tablespace the java server has successfully started and the issue has been resolved.
Thanks Adam and Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is your system part of High Availability Setup?
it looks to me that one of the cluster node is not reachable.
Please in the Cluster
Regards
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We need to check first if hostname/port resolution works well, if gateway is running and if it can be reached at all.
Attache the outcom of these commands:
- niping -v -H localhost
(this has to resole localhost as 127.0.0.1)
- niping -v -S sapgw01
(this has to resolve sapgw01 as 3301)
- niping -v -H 3301
(this has to resolve 3301 as sapgw01)
- niping -c -H localhost -S sapgw01
(this has to come back with 'connection to server OK' or similar)
And attach dev_rd, too.
Best regards,
Adam Csaba Goetz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.