Sap jco connection
hi everyone,
Here 2 problems are there:...............
1) http://localhost:50000/index.html
in browser i got this message
404 Not Found
SAP NetWeaver Application Server 7.10 / AS Java 7.10
The requested resource does not exist.
Details: Go to main page of this application!
2) I just taken web moudle project in that i have taken one java class
I written this program to connect to sap via jco
import com.sap.mw.jco.*;
public class Testing extends Object{
JCO.Client mConnection;
public Testing() {
try {
// Change the logon information to your own system/user
System.out.println("1");
mConnection =
JCO.createClient("001", "userid", "password","language","localhost", "00");
System.out.println("2");
mConnection.connect();
System.out.println("3");
System.out.println(mConnection.getAttributes());
mConnection.disconnect();
catch (Exception ex) { ex.printStackTrace(); System.exit(1);}
public static void main (String args[]) {
Testing app = new Testing();
while i run this java file it get error message: shown in below..............................
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM GWHOST=localhost, GWSERV=sapgw00, ASHOST=localhost, SYSNR=00
LOCATION CPIC (TCP/IP) on local host
ERROR partner not reached (host 127.0.0.1, service 3300)
TIME Wed Jan 31 16:56:55 2007
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8716
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 1
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:1123)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3113)
at com.Testing.<init>(Testing.java:27)
at com.Testing.main(Testing.java:35)
what parameters should i pass to JCO.createClient("................"); here
where should i get this information..................to test connection to sap via jco
thanks,
tony
hi prince,
here j2ee engine is running in sapMMC ,it comes in green color....
plz send me ........
thanks,
tony
Similar Messages
-
Error in SAP JCO connection leads to SAP J2EE engine restart
Hi All
i am using SAP Jco 2.0 to connect to backend.The code runs fine for tables but when i try to access fields like
getExportParameterList().getField("EMPLOYEENUMBER").toString(); it leads to j2ee engine restarts.
Is it a bug?
Is it possible for an exception to restarts server even with error?
Regards
ShankarHi,
Does your application uses any property files or log files? If so, check if they are available in the specified location.
Check the defaultTrace, you will know why the server is getting restarted. Have a placeholder in the defaultTrace so that you can easily identify the error.
Thanks,
Venkat -
SAP Open Hub Vs SAP JCO for Extraction
Hi,
I would like to clarify for SAP JCO connectivity from some third party tool to SAP BW Server in compare to open hub:
We want to connect our internal third party tool to SAP BW/BI server by using Java technology through SAP defined JCO. Later we will create RFC and BAPIs at SAP BW server for data extraction. Those defined BAPIs and RFCs we would call from my java programs.
In such kind of scenario we can extract metadata as well as data for all defined data targets (InfoCube/ODS/DSO/InfoObject) and also can make otherdata load scheduling program to extract data and store it at my non-SAP application.
As per my understanding since we are using SAP provided JCO so there won't be any issue of license for the same. And Open hub require license if it is used to extract and send data from data targets to third party tools.
Can someone confirm for license out of above mentioned cases when exactly it would be required. Mainly I would like to know if we doun't use SAP provided JCO for connectivity and data exttraction then license woould be required or not?
You speedy response would be highly appreciatted.
Regards,
Vivekhi,
refer this links
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b6d59590-0201-0010-5f9d-adb9f6b14d80
help.sap.com/bp_biv270/documentation/SAP_BW_3.5_Functoin_Detail.pdf
www.sapbasis.ru/library/ep_tech_and_program/ep_tech_and_program-7_8.pdf
thanks
naresh -
Cockpit doesnu0092t work (SAP AII 4.0) - Error in JCO connection
Hi all,
After some days working with the "Cockpit" in AII 4.0, today we can not access to it and we dont know why.
When we execute the transaction /AIN/DTUIURL - Auto-ID Cockpit, we do logon and after that it appears the error:
"Failed to process the request. Please contact your system administrator. Pressing on Show Details, in Error stacktrace we can see the following:
"com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.ain.model.utility.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection."
In fact, we have the same problem (an error in JCO connection) when IDOCs try to be sent from R3 to AII or vice versa. We can see in transaction sxmb_moni of XI system this error.
Does anybody know where the problem could be?
Thanks in advance,
XavierHi,
Thank you for this question. What you are reporting looks to me like a bug. The channel for such questions is the Service Marketplace http://service.sap.com/. Please post it there.
Best regards,
Steve -
JCO connection tab in disabled mode in sap J2EE engine/webdynpro/local/proj
Dear all,
I'm developing the simple webdynpro object using netweaver developer studio, but when i deploy it to sap J2ee engine and go there to set the JCO connection, I find the jco connectiuon tab in the diabled mode. I need to configure the new jco connection in order to run the project. Please suggest.
thanks,
Anup.Hi Anup,
You can find service "SLD data supplier" under server->services list.
Refer following links for configuring SLD and JCO connections:
Re: Web Dynpro - Problem with (SLD) JCO Connection
Re: Configuration of SLD
Regards,
Bhavik -
SAP JCo 3.0 - too many network connections
I have implemented a standalone JCo-Client which has to make multiple calls to the same BAPI.
Java 1.5
SAP JCo 3.01
Windows Server 2003
Now I have the problem that each BAPI-Call opens a new network connection (checked with netstat). I use a pooled connection, I have only one JCoDestination object and one JCoFunction object on which I do many function.execute(destination).
Under JCO 2 i used a ClientPool and didn't have the increasing number of network connections.
Any ideas how to solve this.
I add the rump coding so you get the idea:
String destinationName = "ConnPool";
Properties connectProperties = new Properties();
connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "XXX");
connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "5");
connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT, "5");
createDestinationDataFile(destinationName, connectProperties);
int count = 0;
try {
JCoDestination destination = JCoDestinationManager.getDestination(destinationName);
JCoFunction function = destination.getRepository().getFunction("BAPI_NAME");
if (function == null)
throw new RuntimeException("BAPI not found in SAP.");
do {
count++;
try {
JCoStructure importStruktur = function.getImportParameterList().getStructure("IMPORT");
function.execute(destination);
JCoStructure exportStruktur = function.getExportParameterList().getStructure("EXPORT");
catch (AbapException e) {
System.out.println(e.toString());
} while (count < 50000);
catch(JCoException ex) {
System.out.println(ex.toString());
Edited by: Jochen Lang on Apr 29, 2009 1:30 PMFurther testing showed that Pooling connections doesn't affect the number of actual network connections generated.
But with encapsulating the numerous function-calls into a Stateful Connection via
JCoContext.begin(destination);
...lots of function calls...
JCoContext.end(destination);
only one network connection would be used. Sadly I can't use this in my actual application.
Your comments and experiences to this are appreciated!
Greetings Jochen -
SLD configuration - JCO connection with SAP Router
Hi,
I installed the new Sneak Preview SP11 Java Edition including SAP Portal. I tried to run an own Web Dynpro Application with RFC-Access on a R/3 System.
Unfortunately I was not able to get the JCO Connection to run. The R/3 System is reached via SAP Router. I am a little bit confused, because with the last Sneak Preview (SP6 or SP7) this application was running without problems. Of course I thought that this can't be. So I uninstalled SP11 and installed the old version (SP7). I configured the JCO-connection, no problems.
Now I know that this is not my mistake (hopefully ).
If I configured a JCO-connection in SP11 and tried to PING, the first PING was ok. After testing the connection with user, the PING failed. The testing with user returns something like "user or password are not accepted".
Any ideas?
Best regards
RenaldIn your SLD configuration, what do you have as your Logon Group under the message server config. Is it "PUBLIC". if so, then the user id needs to belong to that Logon Group in the system.
Regards,
Rich Heilman -
Problem with JCo Connection Pool
Hi,
I have a problem with using an RFC Model in my WebApplication. So sometimes the access to the function block works, and sometimes it doesn't work. Now I know, that there is a problem with the connection pool. Look at this message:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool WD_X24_MODELDATA_DEST_CPIC_REKTO_DE_useDefinedUser is exhausted. The current pool size limit (max connections) is 10 connections.
So it looks like a problem with closing the JCo Connections after using. Do know where the problem is? Because I'm using many other function blocks with no problems.Hello,
You need to increase the pool size via Visual Administrator.
Server 0 -> Services -> JCO RFC Connections.
Change the pool size from there. I believe a restart is in order.
Regards,
Jan -
Hi there,
I'm trying to generate Java Proxies for SAPJCO using the SAP Java Connectivity Builder (JCB). I got it from the NetWeaver 6.20 Release. The tool installs and runs properly but after putting in the connection properties and klicking "next", the application hangs. When activating System output, I get the error shown below.
I already tried to put all jar files contained in the C:\JBuilder5\lib\ext directiry into the classpath (but none of them contains the class mentioned).
Which is the right (standalone) tool for generating Java Proxies for a standalone Java application?
If it is JCB, is there a bug on the version I use (NetWeaver Release 6.20)?
Any help would be apreciated.
C:\JBuilder5>java -Dlog.handler.FileLog=FileHandler,log.txt -Dlog.logger.com=ALL,FileLog -cp lib/ext/aii_basis.jar;lib/e
xt/aii_ifr_core.jar;lib/ext/aii_ifr_jbtool.jar;lib/ext/aii_lcraccess.jar;lib/ext/aii_msg_runtime.jar;lib/ext/aii_proxy_g
en.jar;lib/ext/aii_proxy_rt.jar;lib/ext/aii_util.jar;lib/ext/aii_util_log.jar;lib/ext/lcrclient.jar;lib/ext/logging.jar;
lib/ext/SapIdeHelp.jar;lib/ext/SapIdeJBUtil.jar;lib/ext/SapIdeJspInsight.jar;lib/ext/SapIdeTaglibReflection11.jar;lib/ex
t/SapIdeTracing.jar;lib/ext/SapIdeUtil.jar;lib/ext/SAPJ2EEEngineJBuilderPlugin.jar;lib/ext/sapjco.jar;lib/ext/SAPmdi.jar
;lib/ext/servlet.jar;lib/ext/tc_sec_core.jar com.sap.aii.ifr.tool.jbuilder.JBuilderTool
#0 12:35:37 [main] DEBUG com.sap.aii.util.misc.api.AIIProperties: Initial AIIProperties
com.sap.aii.client = true
#1 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.standalone" from "null" t
o "true"
#2 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.xml.parserFactory" from "
null" to "com.inqmy.lib.jaxp.SAXParserFactoryImpl"
#3 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.xml.transformerFactory" f
rom "null" to "com.inqmy.lib.jaxp.TransformerFactoryImpl"
#4 12:35:46 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.client.SAPNavigationPane: New file is C:\Documents and Setti
ngs\kalkoo1\Desktop\t.jar
#5 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Client : 010
#6 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Logon Name : kalkoo1
#7 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Password : #########
#8 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Language : EN
#9 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Host name: bgstsapedai01.s
t.behr.de
#10 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for System number : 20
#11 12:36:08 [AWT-EventQueue-0] INFO com.sap.aii.ifr.upload.client.R3LogonScreen: trying to establish connection
#12 12:36:08 [AWT-EventQueue-0] FINEST com.sap.aii.ifr.util.IdentityCheck: Looking up identity
#13 12:36:08 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.util.IdentityCheck: Results of identity check: isIFRServer: false;
isIFRRMIClient: false; isStandaloneIFR: true
#14 12:36:08 [AWT-EventQueue-0] FINEST com.sap.aii.ifr.util.IdentityCheck: Checking IdentityCheck.isIFRServer. Result: f
alse
#15 12:36:08 [AWT-EventQueue-0] INFO com.sap.aii.ifr.upload.sap.SAPConnection: connecting to system 20 on bgstsapedai01.
st.behr.de via JCo
#16 12:36:09 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.sap.SAPUploadSource: init MDI to System bgstsapedai01.st.be
hr.de (system=20, client=010) (BasisRelease: 620)
#17 12:36:09 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.UploadBuffer: new UploadBuffer
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: com/sap/aii/ifr/client/editor/Reference
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethod(Unknown Source)
at java.awt.Component.isCoalesceEventsOverriden(Unknown Source)
at java.awt.Component.access$100(Unknown Source)
at java.awt.Component$2.run(Unknown Source)
at java.awt.Component$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Component.checkCoalescing(Unknown Source)
at java.awt.Component.<init>(Unknown Source)
at java.awt.Container.<init>(Unknown Source)
at javax.swing.JComponent.<init>(Unknown Source)
at javax.swing.JTree.<init>(Unknown Source)
at javax.swing.JTree.<init>(Unknown Source)
at com.sap.aii.ifr.navigation.IFRJTree.<init>(IFRJTree.java:84)
at com.sap.aii.ifr.navigation.IFRTreePane.buildPane(IFRTreePane.java:123)
at com.sap.aii.ifr.navigation.IFRTreePane.<init>(IFRTreePane.java:33)
at com.sap.aii.ifr.upload.client.SAPNavigationPane.<init>(SAPNavigationPane.java:43)
at com.sap.aii.ifr.upload.client.SAPBrowser.setIsConnected(SAPBrowser.java:252)
at com.sap.aii.ifr.upload.client.SAPBrowser$ConnectAction.actionPerformed(SAPBrowser.java:594)
at com.sap.aii.ifr.upload.client.SAPBrowser$NextAction.actionPerformed(SAPBrowser.java:536)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)Hi,
>> Error :- java.lang.NoClassDefFoundError: com/sap/aii/security/proxy/KeystoreHelp
1) Can you check the class path you have mentioned is correctly
2) Setting of the Java in your system ( Desk top /Lap top ) check the Proxy settings
3) Re start the J2EE engine in the server
Regards
Agasthuri Doss -
Data transfer b/w SAP to Java using IDOC and Interface SAP Jco
Dear Experts,
The challenging requirement we are having is, we need to create the interface for data transfer between SAP system and the Java system. The data will be transferred from SAP to java and similarly once some processing done in Java again the details needs to be transferred from Java to SAP.
For this data transferred we are planning to use IDOC process and for interface "SAP Java connector (Version 3.0.5)" we are planning to use. As per our understanding, from Java side one program needs to be written to connect with SAP as "Registered program". This registered program will appear in SAP GATEWAY automatically and using tRFC, TCP/IP connection both SAP and Java system will be connected.
In this case we are having some doubts.
1. The data from SAP is going to be transfered from one Custom transaction (Z tcode). Once "Outbound IDOC" will get triggered and will carry the details. Now the doubt is, whether the data / details will get transfered to JAVA system automatically or we need to perform any other steps from SAP ABAP coding...(like converting in to flat file, XML file and etc) ??
2. We are planning to install "SAP Jco" in Java server. Is this correct...??
3. Other than SAP Jco any other softwares needs to be installed or not..??
4. Since we are going to trigger the "outbound IDOC" from custom transaction, we are planning to develope one program in SE37. Other than this any other program we need to develop or not..??
5. Any sample Java program for the SAP Jco version 3.0.5 to create the "Registered program" with SAP..? (e.g. SAP Listener program).?
If anybody has detailed steps or explanation please share it with us.
Thanks in advance
Warm Regards,
VELHi All,
For the above mentioned issue, we implemented JCo software in JAVA system and created the JAVA program including SAP logon credential details like Client, User name, password and Language details.
When this JAVA program was compiled successfully then, that non SAP system will appear in SAP gateway Tcode.
Once non SAP system started appearing in SAP gateway that means, both SAP & Non SAP are connected automatically.
Regards,
Velmurugan P -
How to use a JCO connection pool in an EJB?
Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
LarsHi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars -
Error while obtaining JCO connection when creating JCO connection
Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_DEST: 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:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at
com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at
com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:95) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) 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:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes DeflooHi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi -
Error while creating jco connection for metadata?
Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: 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:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
RajendraHello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh. -
Error while obtaining JCO connection.
Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
But when it signs the user gets the message Error while obtaining JCO connection.
I was reviewing my WebDynpro on my site by following these steps:
1 I will http://portal:port
2 I clicked Webdynpro
3 I click on Content Administrator
I clicked on 4 Maintain JCO destinations
and then I log shows the following:
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
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:485)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
... 39 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Version null
DOM version null
Client Type ns7
Client Type Profile nn7
ActiveX disabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
J2EE Engine 7.00 patchlevel 109886.44
Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale en_US
Time of Failure Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
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:485)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
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.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:319)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
What should I do??Hi Antonio,
Follow the below note for Jco related troubleshooting.
https://service.sap.com/sap/support/notes/919850
Are you able to see the 4 Jco connections green?
Regards,
Debasis. -
Error while obtaing JCO connection
In Bussiness planning in portal. When i click Planning tab in Enterprise portal, its throwing an error that "error while obtaining JCO connection". I cant proceed furtherI
I am working in my own system.
I have checked many posts and i have done some JCO destinations as per the instructions but it's vain.
The detailed error is as follows;
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(CharRelInst): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.ip.bi.plan.workbench.wdp.InternalInfoprovController.wdGetCharRelInstInterface(InternalInfoprovController.java:296)
at com.sap.ip.bi.plan.workbench.InfoprovController.checkSavable(InfoprovController.java:254)
... 48 more
please give some pointers like what needs to be done JCO settings in Backend.
Thanks in advance.Niranjan,
3 causes and many more....
First and most probable cause is that your CR content in SLD is old....
FIX - to fix this download latest cimsap and crcontent from service.sap.com and implement in SLD.
Second cause user is locked
FIX - unlock in R/3
Third cause could be that the connection pool in JCO is exhausted.
FIX - increase connection pool in JCO.
More causes.
With this new version it appears that any error before connection is created ends up showing this, so I would really go into default trace and look there for original errors, that is the way I found JCO pool was exhausted, that error was not being forwarded and instead it was showing this error...
reward points if helpful
Maybe you are looking for
-
How to Get input from User and Display it's Value
Hi , I need to get 2 inputs from user and to display it's Mutilple Value. The Below Code is working fine to get 2 Input's from user,but it display a Junk value as a Result .How to overcome this Problem. I need to display it's Mutilple(a*b) value of "
-
Server Name Issues (Cable Company Changed, lost Email Server)
Please bear with me as I have a limited knowledge in the finer aspects of the server world. I have searched all over for help with my problem and I have been unsuccessful. I am hoping someone here can help me. My X Server virtually hosts several webs
-
hi there, I have an ipod touch 4th generation which has started to sound 'tinniy' when I play any music from my itunes/music files. The gaurentee is up so no help from Apple. Has anyone else had this problem and any thoughts on how to fix it. I see t
-
I recently upgrade to Mac Os Lion (10.7) and I am unable to open iTunes. I have tried to uninstall it and then install it but no Luck. Any help?
-
Need Help ORA-00257: archiver error. Connect internal only, until freed.
The archive log has exceeded its file limit & hence i'm receiving this error.. The DB we are using is set to in Archive log mode, since i'm using streams in my DB. Now the transactions in DB get archived. I would like to know abt the possible ways of