Jco connection Test error

Hi Exports,
When I test the Jco connection below error message getting,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=csslecc GROUP=SPACE R3NAME=ECC MSSERV=sapmsECC PCS=1 ERROR service 'sapmsECC' unknown TIME Fri Aug 28 04:38:05 200 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsECC' not found SYSTEM CALL getservbyname_r COUNTER 1
Kindly help me to solve this problem.
Thanks
Jibin.

Hi Jibin
This is mostly likely due to JCO or network setup rather than the ESS/MSS application
Please see the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
In particular check network services as per note
Note 52959 - sapms..., sapdp.., sapgw.. unknown (or not found)
Please check JCO connection settings as well as per
Note 723562 - SAP Java Connector: Configuration and Requirements
Please check availability of message server and that user terminal can ping Portal server
and Portal server can ping ECC server
Hope this helps
Best wishes
Stuart

Similar Messages

JCO Connection test fails taking wrong IP Address

Hi All,
We are configuring JCO Destinations(MODEL & METADATA) for ECC 6.0 system. Our portal is on EP7.0 SP8. Our server i.e.ECC and Portal are in two different networks.
The problem here is, for our ECC system we have two IP Addresses.
1. Internal IP Address (130...*) -- on which our ECC system is configured
2. External IP Address (10...*) -- to access the ECC from outside network.
We are able to connect to ECC system with external IP address from Portal server using SAP GUI. We have configured hosts file entries referring ECC system for external IP.
We have configured the ECC system in SLD and configured the JCO destinations for the same. But, Connection tests to the JCO system are failing (partner not reached) as it is referring to internal IP even though we have configured ECC system for external IP address in portal server.
We are getting the follwoing error for JCO Connection test:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=sapsys GROUP=ESS R3NAME=SYS MSSERV=sapmsSYS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '130.7.8.88:sapgw00' not reached TIME Thu Dec 21 10:25:24 2006 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
Why JCO destinations are trying to connect ECC system using the internal IP address even though we didn't mention it anywhere in our portal server configurations?
Please Suggest
Thanks much in advance.
Cheers...
S..S

Hi
Please try this:
First remove the configured ECC from SLD.
Logon the SAP R/3 (ECC).
Run rz70 (T-code).
Enter the serverIP:port of the EP server in the host.
Enter the sapgw in the service.
Check the option SLDRFC for test and activate the current configuration
Then again add the ECC in your SLD.
And please check the entry in the host file also and try to ping the ECC server from the EP server.
Hope this will help you.
Thanks & regards
Arun Singh

System Configuration - SAP Web AS Connection - connection tests error

hi
I have a SAP ECC 6.04 and sap portal 7.01
When I entered in option System Administration / System Configuration / System Landscape / Portal Content Tree / Systems / SAP_ECC (System created by me)
I founded the following error (in SAP Web AS Connection / Tests the connection to an SAP Web Application Server )
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
5. The host name htc-svr-erp.humantech.es was resolved successfully.
6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.
...also see a red "X" near a title SAP Web AS Connection
I have other system (old system). It dont have the last error, I show the properties of the "old system"(without error) and the "new system" (with error) for your analisys
In "old sap system", stack java + abap
http://img830.imageshack.us/img830/9755/oldsysstack.jpg
In "new sap system", stack java separated abap
http://img97.imageshack.us/img97/8627/newsysstack.png
In Portal
In "old system", I created "SAP_HCM" System
In "new system", I created "SAP_ECC" System
The "Connector" view (Object Option)
http://img706.imageshack.us/img706/3776/oldsysconnector.jpg (Old System)
http://img269.imageshack.us/img269/914/newsysconnector.jpg (New System)
*The "Internet Transaction Server (ITS)" view (Object Option)
http://img824.imageshack.us/img824/5043/oldsysits.jpg (Old System)
http://img822.imageshack.us/img822/1314/newsysits.jpg (New System)
The "User Management" View (Object Option)
http://img20.imageshack.us/img20/8646/oldsysuserman.jpg (Old System)
http://img97.imageshack.us/img97/5339/newsysuserman.jpg (New System)
The "Web Application Server" View (Object Option)
http://img101.imageshack.us/img101/6155/oldsyswas.jpg (Old System)
http://img69.imageshack.us/img69/434/newsyswas.jpg (New System)
My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
I run tcode RZ10 in backend after "Extended Maintenance"
http://img15.imageshack.us/img15/8711/oldsysrz10.jpg (Old System) (Here do not exist parameter icm/server_port_1 )
http://img512.imageshack.us/img512/9268/newsysrz10.jpg (New System) (Here do not exist parameter icm/HTTP/j2ee_0 , is it correct?)
Which of these two syntax is correct? 80 + instance or 4200 (any number of port)
also in SAP Systems, I run tcode SICF and enter in "Port Information"
http://img265.imageshack.us/img265/5281/oldsysport.jpg (Old System) (two ports)
http://img441.imageshack.us/img441/7905/newsysport.jpg (New System) (three ports)
The "Information" view (Object Option)
http://img13.imageshack.us/img13/2012/oldsysinfo.jpg (Old System)
http://img714.imageshack.us/img714/6941/newsysinfo.jpg (New System)
My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
because the paremeter "Created by" is the user j2ee admin , I created the system manually or Should the user create pcd_service ?
The "No Category" group (Object Option)
http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg (Old System)
http://img193.imageshack.us/img193/3800/newsysnoncat.jpg (New System) (in this System does not exist the parameter sysnr , is it correct?)
The "Permisions" Option
http://img825.imageshack.us/img825/886/oldsyspermin.jpg (Old System)
http://img243.imageshack.us/img243/2057/newsyspermin.jpg (New System)
The "Delta Link Tracer" Option
http://img716.imageshack.us/img716/798/oldsysdelta.jpg (Old System) (two levels)
http://img828.imageshack.us/img828/8057/newsysdelta.jpg (New System) (three levels, is it correct?)
the other view the same (Old Sytem and New System)
The "Connection Test" Option
http://img412.imageshack.us/img412/5789/oldsystest.jpg
http://img243.imageshack.us/img243/5237/newsystest.jpg
Edited by: Ivan Quiroz on Sep 21, 2010 12:42 PM

 Excuse me, because the message Editor has problems, I edited with html tags for best view 
 
 hi
 
 I have a SAP ECC 6.04 and sap portal 7.01
 
 When I entered in option System Administration /System Configuration /System Landscape / Portal Content Tree / Systems /SAP_ECC (System created by me)
 
 I founded the following error (in SAP Web AS Connection / Tests the connection to an SAP Web Application Server )
 
 SAP Web AS Connection
 Test Details:
 The test consists of the following steps:
 1. Checks the validity of system ID in the system object.
 2. Checks if the system can be retrieved from the PCD.
 3. Check whether a SAP system is defined in the system object
 4. Validate the following parameters: WAS protocol; WAS host name
 5. Checks if the host name of the server can be resolved.
 6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
 7. Checks HTTP/S connectivity to the defined back-end application
 
 Results
 1. The system ID is valid
 2. The system was retrieved.
 3. The system object represents an SAP system
 4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
 5. The host name htc-svr-erp.humantech.es was resolved successfully.
 6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.*
 7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.

 
 ...also see a red "X" near a title SAP Web AS Connection
 
 I have other system (old system). It dont have the last error, I show the properties of the "old system"(without error) and the "new system" (with error) for your analisys
 
 In "old sap system", stack java + abap
 
 <a href=http://img830.imageshack.us/img830/9755/oldsysstack.jpg>Stack Java + Abap<a>
 
 In "new sap system", stack java separated abap
 
 <a href=http://img97.imageshack.us/img97/8627/newsysstack.png>Stack Java and Stack Abap</a>
 
 In Portal
 
 In "old system", I created "SAP_HCM" System
 In "new system", I created "SAP_ECC" System
 
 The "Connector" view (Object Option)
 
 <a href=http://img706.imageshack.us/img706/3776/oldsysconnector.jpg> (Old System)</a>
 <a href=http://img269.imageshack.us/img269/914/newsysconnector.jpg> (New System)</a>
 
 The "Internet Transaction Server (ITS)" view (Object Option)
 
 <a href=http://img824.imageshack.us/img824/5043/oldsysits.jpg> (Old System) </a>
 <a href=http://img822.imageshack.us/img822/1314/newsysits.jpg> (New System) </a>
 
 The "User Management" View (Object Option)
 
 <a href=http://img20.imageshack.us/img20/8646/oldsysuserman.jpg> (Old System) </a>
 <a href=http://img97.imageshack.us/img97/5339/newsysuserman.jpg> (New System) </a>
 
 The "Web Application Server" View (Object Option)
 
 <a href=http://img101.imageshack.us/img101/6155/oldsyswas.jpg> (Old System) </a>
 <a href=http://img69.imageshack.us/img69/434/newsyswas.jpg> (New System) </a>
 
 My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
 
 I run tcode RZ10 in backend after "Extended Maintenance"
 
 <a href=http://img15.imageshack.us/img15/8711/oldsysrz10.jpg> (Old System) (Here do not exist parameter icm/server_port_1 )</a>
 <a href=http://img512.imageshack.us/img512/9268/newsysrz10.jpg> (New System) (Here do not exist parameter icm/HTTP/j2ee_0 , is it correct?)</a>
 
 Which of these two syntax is correct? 80 + instance or 4200 (any number of port)
 
 also in SAP Systems, I run tcode SICF and enter in "Port Information"
 
 <a href=http://img265.imageshack.us/img265/5281/oldsysport.jpg> (Old System) (two ports) </a>
 <a href=http://img441.imageshack.us/img441/7905/newsysport.jpg> (New System) (three ports) </a>
 
 The "Information" view (Object Option)
 
 <a href=http://img13.imageshack.us/img13/2012/oldsysinfo.jpg> (Old System) </a>
 <a href=http://img714.imageshack.us/img714/6941/newsysinfo.jpg> (New System) </a>
 
 My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
because the paremeter "Created by" is the user j2ee admin , I created the system manually or Should the user create pcd_service?
 
 The "No Category" group (Object Option)
 
 <a href=http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg> (Old System)</a>
 <a href=http://img193.imageshack.us/img193/3800/newsysnoncat.jpg> (New System) (in this System does not exist the parameter sysnr , is it correct?) </a>
 
 The "Permisions" Option
 
 <a href=http://img825.imageshack.us/img825/886/oldsyspermin.jpg> (Old System) </a>
 <a href=http://img243.imageshack.us/img243/2057/newsyspermin.jpg> (New System) </a>
 
 The "Delta Link Tracer" Option
 
 <a href=http://img716.imageshack.us/img716/798/oldsysdelta.jpg>(Old System) (two levels) </a>
 <a href=http://img828.imageshack.us/img828/8057/newsysdelta.jpg> (New System) (three levels, is it correct?) </a>
 
 the "System Aliases" Option
 
 <a href=http://img265.imageshack.us/img265/7574/oldsysalias.jpg> (Old System) </a>
 <a href=http://img256.imageshack.us/img256/9817/newsysalias.jpg> (New System) </a>
 
 The "Connection Test" Option
 
 I based in <a href= http://img64.imageshack.us/img64/6638/essalias.jpg> ESS SAP Documentation </a>
 
 In the seven point is diference (blue box) in the <a href=http://img412.imageshack.us/img412/5789/oldsystest.jpg> (Old System) (SAP_HCM System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.) </a> and <a href=http://img243.imageshack.us/img243/5237/newsystest.jpg> (New System) (SAP_ECC System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.)</a>
 
 I desactivated Firewall in my SAP Server and reviewed in <a href=https://forums.sdn.sap.com/thread.jspa?threadID=946905>SAP Forums </a> my problem but nothing
 
 Could This error also could be the problem that I get an error in the JCO Destination?
 
 <a href=http://img819.imageshack.us/img819/826/oldsysjcosso.jpg>(Old System) (Succesfully)</a>
 <a href= http://img822.imageshack.us/img822/4226/newsysjcosso.jpg>(New System) (com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized)</a>
 
 because I configure SSO correctly (I configured last year SSO in "Old System"),I run tcode SSO2
 
 <a href=http://img709.imageshack.us/img709/7194/oldsyssso2.jpg>(Old System)SSO2 Tcode</a>
 <a href=http://img830.imageshack.us/img830/9704/newsyssso2.jpg>(New System)SSO Tcode</a>
 
 <a href=http://img185.imageshack.us/img185/9279/newsyssso22.jpg>(Old System) SSO2 Tcode Details</a>
 <a href=http://img227.imageshack.us/img227/416/oldsyssso22.jpg>(New System) SSO2 Tcode Details</a>
 
 <a href=http://img530.imageshack.us/img530/8710/newsyslog.jpg>(New System) In the SAP Logs: *** J2EE_ADM_DA1 | USERMAPPING.USE | USER.R3_DATASOURCE.J2EE_ADM_DA1 | | systemtype=[(none)], system=["UMESystemLandscapeDummy"], uses strong encryption=[false], remote user ID=[(none)] ***
</a>

JCO Connection giving error when try to edit or preview it.

Hi,
We have in our project PD6(Portal) only java stack & CD1(ECC6.0) system is acting as respective backend.
The JCO connection has already been configured for it,but when I try to edit or preview one of the JCO connection it is giving below error.
Error :
500   Internal Server Error
Failed to process request. Please contact your system administrator.
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
    ... 45 more
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please let us know your input on this.
Regards
Nilesh

Likely Cause would be some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
empty) in SLD. Once you have configured your SLD please also ensure that you have selected the relevant u201CMessage Server Connectionu201D. The Message Server, System Name and Logon Group must not be left empty. Ensure that SLD contains up-to-date and complete information about backend systems.
Check that the SLD is setup properly, check whether you have registered the system through config tool into SLD If not please register system into SLD so that all the parameters are transfered to SLD automatically. You need to do this even the u201CTest Connectionu201D to SLD is successful. Once you are registered you should be able to create the JCO destinations with out any issue.
Thank you.
Shyam

WSRP connection test error

Hi,
I'm testing WSRP Consumer functionality with NetWeaver Portal SP 10. I have my own WSRP producer (WSRP4J with Pluto) which works fine with other consumers (e.g Liferay portal). I do the necessary steps to register a WSRP producer and perform a connection test with the following result:
Producer object was found
Could not retrieve the WSDL file; the handshake URL may not exist or may be invalid
What exactly does this mean? Which possible error sources do I have to check? The WSDL file is accessible by the portal, I used an XML-iView, telnet and common browser access to test this. The producer was tested with other consumers. Where can I find the log files of the WSRP connection test?
Any help will be appreciated.
Regards,
Kevin

Hi All,
Please make sure you have set the proxy settings in System administrator->Service confiuration->Application->com.sap.portal.ivs.httpservice->Services->Proxy. Please make sure you changed the 'Overwrite JVM...' property (if exists in your vertion) to 'true', save and only then restart the httpservice.
In order to trace the WSRP funcionality to a log file, please use the visual admin and in the Log Configurator -> Locations -> com.sap.portal.ivs.wsrp.consumer switch the tracing level to 'All' / 'Debug' and save. the logging will be sent to the latest defaultTrace file under \JC<xx>\j2ee\cluster\server<y>\log\
Thanks,
Avi.

DBCO connection test error

Hi, All
I defined db connection with DBCO and I configured tnsname.ora.
I test tnsping and logon remote DB using sqlplus.
both are OK.
but!!
I check DBconnection with DB02 and then occured error.
next test connection is OK.
so the CBO program use the DBCO is failed at first time and the next execute is OK.
we use ECC 6.0 , Oracle 10.2.0.4, kernel 185
I attach dev_w log
==================================================
B Connect to EBIZPRO as kbizpro with EBIZPRO:KO16KSC5601
C *** ERROR => Characterset 'KO16KSC5601' not supported.
http://dboci.c 2371
C *** ERROR => OCI-call 'OCIErrorGet' failed with rc=100
==================================================
we use characterset 8500
how can I do?/
thanks

Hi, Markus
Thanks for ur reply.
as you sad, only correction is unicode conversion?
but I wonder, next test is conneting using DBCO
test in DB02
-- MESSAGE Database connection EBIZPRO established successfully
and program using DBCO is working well.
only first connention is fail cause of above error.
I checked NLS_CHARACTERSET in Database
SELECT VALUE FROM V$NLS_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';
value --> WE8DEC
how can I do except unicode conversion ?
thanks again

PI : unable to connect to IR with cache connectivity test via RWB

Hi,
Please help to resolve the issues.
Server Details: SAP PI 7.0, SUNSOLARIS with DB2.
PI server was working fine without any issues for the past 2 weeks, Unfortunately issue is the connection failure.
PI services were unable to interlink internally.
cache connection Test Error Below:
Connection to system null using application null lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/conntest/int?" with user "PIRWBUSER". Response code is 404, response message is "Not Found"
SLDCHECK done with success,SPROXY no issues,
users are not locked & password not changed.
Thanks,
Bala

After full cache refresh. with SXI_CACHE i got cache error "UPDATE" detail error as below.
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 404, response message is "Not Found"
     at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doGet(HmisServletImpl.java:640)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Error while testing JCO connections

Hi,
Can anyone please help me with the following error.I am getting this when I'm testing my JCO connection :
RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=cgnsap13 SYSNR=01 GWHOST=cgnsap13 GWSERV=sapgw01 PCS=1 LOCATION SAP-Gateway on host cgnsap13 / sapgw01 ERROR max no of cpic clients exceeded (300)
Thanks and regards,
Lisha

Hi
Please ensure that you have the msgserver entry in your services file. The problem you are getting is because of the message server. you need to have a entry like
sapms<System ID> tcp/3601
Also go to your SAP logon pad and check for groups. and type the sid in the box along with the appserver and then click on generate list. You should get some logon groups. If not you can be sure that your message server is not configured properly. Talk to your SAP Basis person
regards
Ravi

Error in JCo Connection creation

Hi All,
When I create a JCo connection on my local J2EE it fails with the error enclosed as below:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=frces4066 GROUP=PUBLIC R3NAME=AM1 MSSERV=sapmsAM1 PCS=1 ERROR partner not reached (host frces4066, service sapmsAM1) TIME Mon Apr 03 18:44:33 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8596 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
When I try and ping the JCo the error is as enclosed below:
Failed to ping JCo destination WD_COMMITMENT_MODELDATA_DEST
I have maintained the enteries in hosts file as well as the services file and when I telnet the server on port 36XX where XX is the system number of the system I create the JCo for it connects successfully.
When I test the CIM test for the SLD that connects successfully.
Where and why is the JCo failing after creation?
Can someone throw some light on this error.
Thanks in advance for all your help.
Best regards,
Divya

Hi All,
Anyone can help? I got the same problem. It seems that the PUBLIC group in NSP ABAP system can't not be accessed.
Here is my system landscape:
- I have installed the Java and ABAP in the same host
- My ABAP system is NW2004sSneakPreviewABAP, Java is SAPNetWeaver04_SP16Preview
1) I set up SLD successfully (import CIM, run RZ70, the ABAP system shown up in the Technical Landscape in SLD
2) I created JCO destination with Load Balancing but it failed to ping and to test
3) I already define the group 'PUBLIC' in tx SMLG but from SAPGUI I can't add the group. I got the error message "Message Sever could not find any group".
4) The PUBLIC group does not show if I run the program 'lgtst'.
Test lgtst:
===========
c:\usr\sap\NSP\SYS\exe\nuc\NTI386>lgtst.exe -H hpxp2 -S sapmsNSPusing trcfile: dev_lg
list of reachable application servers
[hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
c:\usr\sap\NSP\SYS\exe\nuc\NTI386>lgtst.exe -H hpxp2 -S 3600
using trcfile: dev_lg
list of reachable application servers
[hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
James

JCO Connection error in webdynpro

Hi
I have Ep 7.0, ECC 6.0 (NW2004s)
I am trying to establish JCo connection but we are getting the
following error
"com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect
to message server host failed Connect_PM TYPE=B MSHOST=*****
GROUP=SPACE R3NAME=HEI MSSERV=sapmsHEI PCS=1 ERROR
service 'sapmsHEI' unknown TIME Fri May 30 16:19:20 2008
RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -
3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2:
service 'sapmsHEI' not found SYSTEM CALL getservbyname_r COUNTER 2"
Already i have created TechnicalSystems in the Portal and
I have entered the sevice file in the location of c:\WINDOWS\system32\drivers\etc as "sapms<SID> 3600/tcp" in EnterprisePortal Server.
after that we have restarted the server
Still i am getting same error.
Could you please help us.
Regards
Srinivas

Hi,
First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.
You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And
Similarly For BW Also.
The Given Below Links To Help You SLD Cofiguration For J2EE
http://www.*********************/solution_manager/solution_manager_sld.html
SLD Configuration
3.If You Want To Create JCO Destinations.You Go To Login Portal
Content Administration->Webdynpro->Create JCO Destinatiion
A.General Data -> Specify Model Name,Client And JCO Pool Configuration
B.Specify J2EEE Cluster
C.Destination type
Data Type-> Application DataModel,Dictionary MetaDataMetadata
Destination Type->Load Balancing Or Single Server
D.Specify Either Application Server Or Message Server
E.SecurityUsername,password,confirm password,language
F.SummaryWhole Information
Similarly Metadata Created Follow Same Steps As Above
After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
It's Useful Rewards Points
Bye
Thanks
SubbaRao

Error in launching guided procedure: Error while obtaining JCO connection.

Hello experts,
we've a problem with webdynpro java calling a guided procedure.
We've defined an endpoint for our callable object, as you can see the test of the connection works fine:
In the configuration of our callable object we use the endpoint above:
And we can test the callable object: it works well, call the right BAPI and find the results.
But when the GP is called and this callable object try to call the BAPI in the background it doesn't work at all.
In the log and trace of the portal we find this:
A technical callable object exception ocurred: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
com.sap.caf.eu.gp.model.co.tech.TechnicalCallableObjectException: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:101)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor.run(BackgroundCOExecutorImpl.java:126)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:504)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:581)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessorHelper.processAction(BackGroundActionProcessorHelper.java:183)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.queue.BackgroundCOQueueProcessor.run(BackgroundCOQueueProcessor.java:263)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.caf.eu.gp.base.exception.EngineException: Connection that belongs to connection name SAP_R3_HumanResources could not be loaded from System Landscape Directory (SLD): Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:138)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.analyseConnectionMode(ConnectionDeliverRFC.java:185)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.deliverConnection(ConnectionDeliverRFC.java:91)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SAPSystemConnector.deliverMetaData(SAPSystemConnector.java:116)
at com.sap.caf.eu.gp.model.connect.pvd.saprfc.impl.SAPRFCServiceProvider.executeExternalService(SAPRFCServiceProvider.java:232)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceManager.executeExternalService(ExternalServiceManager.java:139)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:89)
... 9 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:160)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:41)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.resolveClientConnection(SLDConnectionManager.java:169)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:102)
... 15 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'SAP_R3_HumanResources'
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:658)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:485)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:233)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
... 19 more
Caused by: com.sap.tc.webdynpro.services.sal.um.api.WDUMException: No client user defined for the current request (no regular Web Dynpro request as ITask is null.
at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory.getCurrentUser(AbstractClientUserFactory.java:48)
at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.getCurrentUser(WDClientUser.java:67)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:591)
It seems that the GP could not connect to the SLD to call the JCO, but as said before, when we test the callable object, it calls the BAPI without any problem.
We tried to recreat either the JCO and the Endpoint but without success.
Any help will be appreciated.
Thank you.

Hi.
Thanks for your answers.
Here are the things :
From the GP administration, the endpoint's test is working.
From the SLD, the JCO is working too.
From the Web Dynpro Content Administrator, the JCO's test is working too.
From the GP Desing Time, the callable object supposed to call the FM uses the right endpoint, and the test is working too, we retreive data from the backend.
From our app, calling the GP process that includes our callable object, we have errors pasted above...
Regards.

Error with JCO connection ?

Hi,
I used the example TutWD_FlightList yo test Web-dynpro , Then after I deployed to the Server . I enter 'Web-dynpro' to create 2 JCO connections . There were 2 cases :
1. If I chose Application Data & Single Server Connection . Test is OK ( Connection for 'WD_FLIGHTLIST_MODELDATA_DEST' was sucessfully tested with user 'XXX' ) . And the if I run the web-dynpro I get the error :
The initial exception that caused the request to fail, was:
   com.sap.dictionary.runtime.DdException: 'WD_FLIGHTLIST_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_FLIGHTLIST_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
    at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
    at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
    ... 54 more
But If I chose 'Dictionary Meta Data ' ( When create JCO connection ) , The test was not successfull , Here I have only 1 R/3 Server So i do not use message server for load balancing . So In my case How can I do ?
Thanks

hi,
please find out the below link it will be useful to u.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0]
in order to call the BAPIs from the backend system Logical destionations should be created properly for ur R/3 system and they should be in enable mode. please check it once. and also check ur message server once.
Thanks
Anu

JCO Connection error

Hi,
While giving the parameters for JCO connection in SLD(Technical System Type:- Web As Java) I am taking the destination Type as Application Server.
While creating the JCO connection the JCO connection is getting created but while testing the connection I am getting the following error
com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call.Do I need to take destination type as Message Server,what are the Name and Message Server for both?
Please reply.
Regards,
Pawan

Hey in SLD the WEBAS-ABAP technical system is created to identify a SAP system.The common connection properties of the SAP system(like ECC,BW,CRM)are defined under WEBAS-ABAP technical system.For each SAP system one WEBAS-ABAP technical system is created.The changing properties like username password client number of the backend system i.e SAP system are declared under the JCOs.So when you are connecting to SAP system a WEBAS-ABAP technical system should be created and JCOs should be created/specified for webdynpro applications.The JCOs will make use of the WEBAS-ABAP technical system connection properties internally from the SLD also contains the extra connection properties(client no,uname,pwd).So you have to create JCOs when you are communicating with SAP systems.
Note:No need to create JCOs for other systems(non SAP).

JCO connection error explain

Hi All,
I have a list of JCO which is comes with intallation of ESS those starting with "SAP_" all of them are green and ping is successfull
Apart form these I created few system defined JCO connection to connect to backend for the systems I defined.
When I ping the JCO connection using SSO as the autherntication it is successful but the Test fails
giving out this error.
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)
My question is which username and password this is validating to test the connectiion (I gave in SSO as the authentication for creating this JCO) and I do this test by loggin in as the portal admisnitrator
Please explain how it is tested with the backend and what is the username and password used to test the connection since I use SSO as the authentication type and where the username is stored.
Thanks,
Charan

Hey thanks for your reply.
I already login into the portal as the administrator who has all controls on the portal.
user id : adminsitrator
Do you mean this user id (administrator) needs to be created in the backend and given all rights to create a JCO or to test a JCO.
Thanks,
Charan

JCO Connection Errors

Hi Experts,
we have configured the ECC6.0 backend system in to SLD and tested the same, its succesfully running and configured.
next we tried to create the Jco connection(META DATA and MODEL DATA) for the backend system, it was created with out any issues. but whenever going to Test /Ping the JCO connections we got an error.....please find the below error message.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=iginsap1 GROUP=public2 R3NAME=EHT MSSERV=sapmsEHT PCS=1 ERROR       internal error TIME        Mon Jul 18 12:32:52 2011 RELEASE     700 COMPONENT   MS (message handling interface, multithreaded) VERSION     4 RC          -101 COUNTER     5
Note: As per some S-notes, we added the system details in to the Service file and checked the Login group also.
and aso ran below commands at the ECC server
1) niping -v -H iginsap1
2) niping -v -S sapmsEHT
3) telnet iginsap1 sapmsEHT
But still we are getting the same error... please provide the solution as soon as possible..
Regards,
Arjun.

Hi Arjunab,
Have you tried to ping the destination server from the source? Please try to mention the details like below in the source (J2EE Server) host file:
Ip Address of the backend system                FQN                                 hostname
xx.xx.xx.xxx                                       *abcdx.xxxxatxyz.com *            abcd
Hope this will help you.
Regards,
Faisal

Jco connection Test error

Similar Messages

Maybe you are looking for