Error while Configuring JCO on Solaris

Hi all,
I configured JCO according to installation instructions in the documentation shiped with installation bundle, classpath and LD_LIBRARY_PATH variables are set correctly and I can echo and varify the paths. But whenever I access any class of JCO from JSP or run sapjco.jar from its folder, it throws an exception and restarts the server. I would highly appreciate any hint.
Here is error message with -stdout option:
mazda:dv1adm 44% java -jar sapjco.jar
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [/usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path/libsapjcorfc.so: ld.so.1: java: fatal: /usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path/libsapjcorfc.so: wrong ELF class: ELFCLASS64]. java.library.path [/usr/j2sdk1.4.2_04/jre/lib/sparc/client:/usr/j2sdk1.4.2_04/jre/lib/sparc:/usr/j2sdk1.4.2_04/jre/../lib/sparc:/usr/sap/DV1/SYS/exe/run:/usr/sap/DV1/SYS/exe/runU:/usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path:/opt/dazel/lib:/usr/lib]
        at com.sap.mw.jco.JCO.<clinit>(JCO.java:731)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:141)
        at com.sap.mw.jco.About.<init>(About.java:33)
        at com.sap.mw.jco.About.main(About.java:90)
X connection to mazda:13.0 broken (explicit kill or server shutdown).
mazda:dv1adm 45% java -jar sapjco.jar -stdout
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [/usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path/libsapjcorfc.so: ld.so.1: java: fatal: /usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path/libsapjcorfc.so: wrong ELF class: ELFCLASS64]. java.library.path [/usr/j2sdk1.4.2_04/jre/lib/sparc/client:/usr/j2sdk1.4.2_04/jre/lib/sparc:/usr/j2sdk1.4.2_04/jre/../lib/sparc:/usr/sap/DV1/SYS/exe/run:/usr/sap/DV1/SYS/exe/runU:/usr/sap/DV1/DVEBMGS00/j2ee/sapjco-install-path:/opt/dazel/lib:/usr/lib]
        at com.sap.mw.jco.JCO.<clinit>(JCO.java:731)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:141)
        at com.sap.mw.jco.About.<init>(About.java:33)
        at com.sap.mw.jco.About.main(About.java:90)
SAP Java Connector (JCo)
Copyright (c) 2000-2004 SAP AG. All rights reserved.
Version Information
Java Runtime:
Operating System:    SunOS 5.9 for sparc
Java VM:             1.4.2_04 Sun Microsystems Inc.
Java Codepage:       ASCII
Versions:
JCo API:             2.1.3 (2004-03-08)
JCo middleware:      Library not found
JCo library:         Library not found
RFC library:         Library not found
Paths:
JCo classes:         System-defined path
JCo library:         Library not found
RFC library:         System-defined path
Manifest
Manifest-Version: 1.0
Implementation-Version: 20040430 0858 [2.1.3 (2004-03-08)]
Specification-Title: SAP Java Connector
Specification-Version: 2.1.3
Implementation-Title: com.sap.mw.jco
Main-Class: com.sap.mw.jco.About
Created-By: Ant 1.4.1
Implementation-Vendor-Id: com.sap
Implementation-Vendor: SAP AG, Walldorf
Specification-Vendor: SAP AG, Walldorf

Somthing similar is happening to me as well... I found <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/bc-jas/~form/handler">note 542175</a> sounds interesting, but I'm still trying to figure out how to apply to my tricky scenario (MDM!)

Similar Messages

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 Defloo

Hi
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 Configuring Repository INS0017: Installation of the seeded data

I am getting error while configuring repository at 36%
Error:
Seeding Failed:
The warehouse builder workspace owner installation failed on user OWBSYS.
INS0017:Installation of the seeded data failed java.io.FileNotFoundException:
xmlClasses.xml (Access is denied)
Operating system: Windows 2008 server 64 bit
Database: Oracle 11g Release 11.2.0.1.0 64 bit
Log file is not created in given location(Unified repos)

Hi David,
But we have successfully Created the Repository(Using Repository Assistance) using OWB 10.2.0.4 on Oracle 11.1.0.7 Db on Solaris OS.
and i also checked the Metalink it say the OWB 10.2.0.4 can be used with Oracle 11.1.0.7 Db.
Nawneet

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 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.
Rajendra

Hello 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.

Getting an error while configuring VMM for System Center 2012. error - An internal error has occurred trying to contact an agent on the WIN-NTJU8CNU server: : . Ensure the agent is installed and running.

Hi,
I am trying to install "System Center 2012 - Virtual Machine Manager by Using a Pre-Configured VHD".
I downloaded install guide & the binaries from http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=10712
I have followed the installation document & getting an error while configuring VMM for System Center 2012.
error details from log file given below:
01:12:24:VMMPostinstallProcessor threw an exception: Threw Exception.Type: Microsoft.Carmine.WSManWrappers.WSManProviderException, Exception.Message: An internal error has occurred trying to contact an agent on the WIN-NTJTNEJ1UCN.mydomain.com server: : .
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
01:12:24:StackTrace:   at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(WsmanSoapFault fault, COMException ce)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.RetrieveUnderlyingWMIErrorAndThrow(SessionCacheElement sessionElement, COMException ce)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Invoke(String actionUri, WSManUri targetUri, Hashtable parameters, Type returnType, Boolean isCarmineMethod, Boolean forceResponseCast)
   at Microsoft.Carmine.WSManWrappers.AgentManagement.AssociateLibrary(WsmanAPIWrapper wsmanObject, String CertificateSubjectName, String& ExportedCertificate, ErrorInfo& ErrorInfo)
   at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.AssociateAgentServer(String fullyQualifiedServerName)
   at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.AssociateDefaultLibraryServer()
   at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.SetupLibraryShare()
   at Microsoft.VirtualManager.Setup.InstallItemCustomDelegates.PangaeaServerPostinstallProcessor()
01:12:24:InnerException.Type: System.Runtime.InteropServices.COMException, InnerException.Message: There is a time and/or date difference between the client and server.
01:12:24:InnerException.StackTrace:   at WSManAutomation.IWSManSession.Invoke(String actionUri, Object resourceUri, String parameters, Int32 flags)
   at Microsoft.Carmine.WSManWrappers.MyIWSManSession.Invoke(String actionUri, Object resourceUri, String parameters, Int32 flags)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Invoke(String actionUri, WSManUri targetUri, Hashtable parameters, Type returnType, Boolean isCarmineMethod, Boolean forceResponseCast)
01:12:24:ProcessInstalls: Running the PostProcessDelegate returned false.
01:12:24:ProcessInstalls: Running the PostProcessDelegate for PangaeaServer failed.... This is a fatal item. Setting rollback.
01:12:24:SetProgressScreen: FinishMinorStep.
01:12:24:ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs
I have completed MSSQL server configuration and while configuring VMM the below error displayed in the wizard:
An internal error has occurred trying to contact an agent on the WIN-NTJTNEJ1UCN.mydomain.com server: : .
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
I have checked that the following services are running:
1) Verified WS-Management srvice 2) MSSQL server + MSSQL (agent) 3)SC VM Manager Agent 4) Windows management instrumentation .
I have joined the VM (on which installing SC VMM) in a domain(as per install guide) and installing VMM using domain account & it is in local Administrators group.
Also I would like know if there is any stand alone SC VMM installer. If yes then please let me know the installer location & install guide.
thanks.
====

Have you installed AppController on the same machine with VMM?

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

Error while configuring work repository details in topology Manager

Hi,
Could anyone pls advice, is it possible creating more than one Master repository connection for the same instance.
When i try to do so, am getting the below error while configuring the work repository details in topology manager.
“A work repository already exists for this connection.
Enter the repository password to declare it in your Master Repository”
I tried with both the new master and work repository password. But no luck.
Previous Master & work details:
Master: PCS_MASTER
Work:PCS_WORKREP
New Details
Master: PCS_MASTER_INT
Work:PCS_WORKREP_INT
Instance: PCBID
Am trying to create new master repository for PCS_MASTER_INT.

In the same oracle schema you can have only 1 master and 1 work repository. Usually they take 2 schema (1 for each).
If you need 2 master repository you have to use 2 different jdbc path. I'm using a db with several master / work, each repo has got its schema..

Error while Configuring environment parameters

Hi,
I am installling Oracle Utilities Business Intelligence 2.3.2 version . I am getting error while configuring Environment Paramameters
Database- Oracle 11g R2
OS- Windows Server 2008
1. Environment Description
Environment Description: DEV01
2. Business Application Server Configuration
Business Server Host: 01HW342889
WebLogic Server Name: myserver
Business Server Application Name: SPLService
MPL Admin Port Number: 6502
MPL Automatic startup: false
3. Web Application Server Configuration
Web Server Host: 01HW342889
Web Server Port Number: 6500
WebLogic SSL Port Number: 6501
Web Context Root: ouaf
WebLogic JNDI User ID: systemjndi
WebLogic JNDI Password: ENC(tEky0TX65m0nDNIlnX
CcwlbnXl2b1kMnvE8DD0wfI1Y=)
WebLogic Admin System User ID: {3DES}gg8gG+5N+gwJBPWG
IhRRuQ==
WebLogic Admin System Password: {3DES}gg8gG+5N+gwJBPWG
IhRRuQ==
WebLogic Server Name: myserver
Web Server Application Name: SPLWeb
Application Admin User ID: appladmin
Application Admin Password: ENC(OrIg4HyDLxi2kQ6uSs
cBz4cubUr2U5BbRl75SY2pP6Q=)
Expanded Directories: false
Application Viewer Module: true
4. Database Configuration
JDBC Name: oubi-jdbc
MPL Database User ID: SPLADMV2
MPL Database Password: ENC(mfG7quacTagw5qEvov
oaQIRpnogRvroY4NcXp6WZCZo=)
XAI Database User ID: SPLADMV2
XAI Database Password: ENC(tNfRJUthvYQR990TzW
314nXU+5jWBuYBDs5AgT5qG7g=)
Batch Database User ID: SPLADMV2
Batch Database Password: ENC(L5BXr/lXp/riShr9Lp
kFDsgUIjDm5I6TJU5Suz0Wy/k=)
JDBC Database User ID: SPLADMV2
JDBC Database Password: {3DES}L43JfrbOrCtupkwm
4I/Adw==
Database Name: DEV1
Database Server: 01HW342889
Database Port: 1701
ONS Server Configuration:
Database Override Connection String:
Oracle Client Character Set NLS_LANG: AMERICAN_AMERICA.UTF8
5. General Configuration Options
Batch RMI Port: 6509
Batch Mode: CLUSTERED
Coherence Cluster Name: OUBICLUSTER1
Coherence Cluster Address: 172.25.138.45
Coherence Cluster PORT: 6508
Coherence Cluster Mode: dev
Each item in the above list should be configured for a successful install.
Choose option (1,2,3,4,5, <P> Process, <X> Exit): P
--> Calculating additional variables ... done.
--> Writing variables to E:\OUBI2\ouaf\temp\FW.V4.0.2\tmp\2011-06-10-0954\ENVIRO
N.INI ... done.
Can't open E:\OUBI2\ouaf\temp\FW.V4.0.2\install_FW_E:\OUBI2\ouaf\DEV01.log for o
utput at E:\OUBI2\ouaf\temp\FW.V4.0.2\data\bin\perllib/SPL/splLog.pm line 190.
"ERROR - Detected while running install.plx."
Thks,
Mohan

This is a common error people get when configuring Repository Service in Admin Console...
Main reason for this is that there is an incompatible bit versions of Oracle Database and Informatica Server and windows. Try to reinstall Oracle DB or Infa Server and tryconfiguring the same it will work
Or it could be parameter issues if it is linux...
Please mark helpful this post

Error while configuring talent profile for ESS

Dear Experts
I am having following error while configuring talent profile for ESS:
The URL http://pplkhidr05.ppl.com.pk:8000/sap/bc/webdynpro/sap/hrtmc_employee_profile was not called due to an error.
Note
The following error text was processed in the system TRG : Access via 'NULL' object reference not possible.
The error occurred on the application server PPLKHIDR05_TRG_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: GET_PLVAR of program /1BCWDY/81IYQOEI3SKMOOB9TXW5==CP
Method: IWCI_HRTMC_TP_SHARED_DATA~GET_PLVAR of program /1BCWDY/81IYQOEI3SKMOOB9TXW5==CP
Method: OVERRIDE_EVENT_OIF of program /1BCWDY/828X5HC99194NVUUKJ30==CP
Method: IWCI_IF_FPM_OIF_CONF_EXIT~OVERRIDE_EVENT_OIF of program /1BCWDY/828X5HC99194NVUUKJ30==CP
Method: GET_UIBBS_FOR_EVENT of program /1BCWDY/7V06LYNNPH3D2G2T1W0Z==CP
Method: IWCI_IF_FPM_FLOORPLAN_COMP~GET_UIBBS_FOR_EVENT of program /1BCWDY/7V06LYNNPH3D2G2T1W0Z==CP
Method: IF_FPM_FLOORPLAN~GET_UIBBS_FOR_EVENT of program CL_FPM_OIF_INTERNAL===========CP
Method: GET_NEXT_UIBBS of program CL_FPM========================CP
Method: PROCESS_EVENT of program CL_FPM========================CP
Method: RUN_EVENT_LOOP of program CL_FPM========================CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system TRG in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server PPLKHIDR05_TRG_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server PPLKHIDR05_TRG_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Any suggestions on how to resolve the error?
Regards
Imran

Imran,
check this thread
http://forums.sdn.sap.com/click.jspa?searchID=43957204&messageID=8996092
Thanks
Bala Duvvuri

Error While Configuring the Shared Service with Active Directory

Hi All,
I am getting a error while configuring MSAD with Shared Service, when entering the User Id and password and clicking next, the following error is displayed:
"EPMCSS-05180:Failed to validate Security configuration. Failed to connect. Invalid values for Base DN, User DN or Password. Enter valid value(s). Root Cause : [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]"
The AD user has the read access to the all users and group in Active Directory. If I use an Active Directory user with Admin privilege, It is getting connected.
But client is not ready to provide the Admin Access due to their internal policy and I also don't have any document which says admin privilege is required. According to the document,the user should have the following privileges only.
"The distinguished name of the user that Shared Services should use to bind with the user directory. This user must have search privilege on the RDN attribute within the DN. For example, in the dn: cn=John Doe, ou=people, dc=myCompany, dc=com, the bind user should have search access to the cn attribute.Special characters in User DN must be specified using escape characters. See “Using Special Characters” on page 46 for restrictions.
Example: cn=admin,dc=myCompany,dc=com
But I am getting confused with the statement "This user must have search privilege on the RDN attribute within the DN". Is it not search privillege?
Can anybody help me with required privilege for Active Directory user to configure with Shared Service.
Thanks in Advance,
Sunil

Thank you All,
i tried connecting using AD Browser from Microsoft, and it went in properly. then i found out that the AD Team here were giving a Wrong Credentials to connect, they Gave me HYP_OID which infact turned out to be a Principal name instead of a 'cn'.
after searching in the AD Browser i found the correct cn which is "Hyperion OID", then it went to the second Screen where now i am trying to search for the Users based on thier Job Nature.
Thank you for all the Support Guys, you both "Celvin" and "John" are the Top Guys under my Search list for any technical Assistance.
Thank you once again Friends....
Regards,
Sunil...
Shantan....

ColdFusion 11 wsconfig.exe -- Error while configuring connector for IIS.

I ran into a problem with my ColdFusion 11 64-bit installation/migration on a Windows Server 2012 R2/IIS 8.5. I was following the ColdFusion 11 Lockdown Guide - Pete Freitag (very helpful) and I ran into problems on page 35 "Run the ColdFusion Web Server Configuration Tool". When I attempted to do this for ALL IIS websites I encountered a Windows error [APPCRASH - Exception Code:c0000005]. Also, note my Administrator-Command Prompt window provided this error message "Error while configuring connector for IIS. Make sure you have administrator privileges". However, I did not experience this error with all of the migrated sites. I traced my steps backward to discover the problem. I used the Microsoft Web Deployment tool (good tool) to migrate the old IIS websites to the new IIS. I utilized Metabase Explorer the IIS 6.0 Resource Tools to discover that some of the migrated sites that were crashing did not have the key/value ID:6006 | Name: DefaultDoc. Once I added this key and redeployed the site the ColdFusion 11 connector (wsconfig.exe) worked fine. In addition, I added this key/value to some of the larger previously migrated sites in IIS 8.5 ("Default Document") and it worked with the connector as well.
Knowing how IIS encapsulates information the DefaultDoc key/value should have passed from the website setting. Why would this make wsconfig.exe crash?
Thanks in advance and I hope this saves someone from hours of research and frustration.

DiscoDelight,
Have you forwarded this information directly to the ColdFusion product team? If not, I'll try to draw their attention to it. Only a few of them are active on these forums, so this issue might be overlooked.
-Carl V.
EDIT: I just pinged them on Twitter to take a look at this post.
EDIT #2: They just pinged me back that they are looking into it.

Windows 8.1 Hyper-V - Error while configuring the hard disk 0xC03A0014

Hello. I have just enabled Hyper-V on my Windows 8.1 laptop.
Dell Latitude E7440 i7-4600U @ 2.10GHz
I can create a Virtual-Switch but I am unable to create a new Hard Disk or Virtual Machine within Hyper-V. I get the same error for both processes.
Error: The Virtual Machine Management Service encountered an error while configuring the hard disk on virtual machine New Virtual Machine.
Failed to create the virtual hard disk.
The system failed to create C:\Users\user\Documents\Test\New.vhdx .
Failed to create the virtual hard disk
The system failed to create C:\Users\user\Documents\Test\New.vhdx . A Virtual disk support provider for the specified file was not found. (0xC03A0014).
I have ran all Dell Client System updates and all of windows updates.
I have attempted to create a virtual machine on the current SSD and also an external drive. The same error appears.
I have also attempted to create a virtual hard disk via Hyper-v with a Base vhdx, still the same error occurs. I've tested the base image on other laptops of the same model and windows 8.1 without issue.
Any thoughts on how I can fix this?
Thank you,
-Jake

Hi Jake,
"Enable Data Execution Protection (DEP) in the BIOS and make sure the Format of drive file system is not fat32.
1. Uninstall Intel Active System Monitor 3.0, if installed.
2. Disable "Intel IPMI Service" and "Intel Monitoring Agent" Service.
3. Open regedit and locate: HKLM\System\CurrentControlSet\Services\imbdrv.
4. Change the Start Key to 4 (Disabled).
5. Locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97D-E325-11CE-BFC1-0 8002BE10318}.
6. Take ownership of the ‘Properties’ key.
7. Give yourself full permission for this key.
8. Now locate the properties key; if you see a ‘Security’ entry there, that is your problem. Delete this key.
9. Try attaching or adding the VHD again after rebooting.
If above steps did not help, add the Network Service account to Local Administrator group."
It is quoted from the similar thread below :
http://social.technet.microsoft.com/Forums/windows/en-US/55085ff3-0f26-41bd-b590-bb3490e2d6f5/win-7-professional-a-virtual-disk-support-provider-for-the-specified-file-was-not-found?forum=w7itprovirt
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

TR: Thread Package error while configuring

De : Joel RIANDEY
Date : mercredi 24 septembre 1997 12:42
A : Francois BOUCHARD
Objet : Thread Package error while configuring
I've got the following error while trying to assign a partition on a node during configuration.
SYSTEM ERROR: This component cannot be moved to this node. Node does not
support logical component
Class: qqsp_ErrorDescriptor
Error Time: Wed Sep 24 11:08:34
Exception occurred (locally) on partition "Forte_cl0_Client", (partitionId
= 172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1, taskId =
[172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1.54]) in application
"Forte_cl0", pid 183 on node JOELR in environment nt_dvpte.
USER ERROR: The node ORDAM-NT_DVPT is unable to support this partition
(LaunchCcsProject_cl0_Part1). This is because either all of the restricted
projects required by the partition have not been installed on the node or the
node does not have the external resource or thread package that the partition
uses. This partition requires the restricted project(s) <none> and the thread
package Forte.
Class: qqsp_UsageException
Error #: [1301, 460]
Detected at: qqem_LogicalPartition::Assign at 4
Last TOOL statement: method AppComponentVM.Install
Error Time: Wed Sep 24 11:08:34
Exception occurred (locally) on partition "Forte_cl0_Client", (partitionId
= 172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1, taskId =
[172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1.54]) in application
"Forte_cl0", pid 183 on node JOELR in environment nt_dvpte.
The partition is containing a library wrap object which Multithreaded attribute is set to FALSE;
The node to which I want to transfer the partition is a NT node while my library remains in an AIX one.
Nevertheless I can drag my partition if this library Multithreaded attribute is set to TRUE but I need it to be positionned at FALSE.
I) Anyone could tell me if there is a solution for assigning such partition on such node ?
II) What is "the thread package Forté' ?

De : Joel RIANDEY
Date : mercredi 24 septembre 1997 12:42
A : Francois BOUCHARD
Objet : Thread Package error while configuring
I've got the following error while trying to assign a partition on a node during configuration.
SYSTEM ERROR: This component cannot be moved to this node. Node does not
support logical component
Class: qqsp_ErrorDescriptor
Error Time: Wed Sep 24 11:08:34
Exception occurred (locally) on partition "Forte_cl0_Client", (partitionId
= 172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1, taskId =
[172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1.54]) in application
"Forte_cl0", pid 183 on node JOELR in environment nt_dvpte.
USER ERROR: The node ORDAM-NT_DVPT is unable to support this partition
(LaunchCcsProject_cl0_Part1). This is because either all of the restricted
projects required by the partition have not been installed on the node or the
node does not have the external resource or thread package that the partition
uses. This partition requires the restricted project(s) <none> and the thread
package Forte.
Class: qqsp_UsageException
Error #: [1301, 460]
Detected at: qqem_LogicalPartition::Assign at 4
Last TOOL statement: method AppComponentVM.Install
Error Time: Wed Sep 24 11:08:34
Exception occurred (locally) on partition "Forte_cl0_Client", (partitionId
= 172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1, taskId =
[172B8B7C-C095-11D0-9ECC-3870EE77AA77:0x33ae:0x1.54]) in application
"Forte_cl0", pid 183 on node JOELR in environment nt_dvpte.
The partition is containing a library wrap object which Multithreaded attribute is set to FALSE;
The node to which I want to transfer the partition is a NT node while my library remains in an AIX one.
Nevertheless I can drag my partition if this library Multithreaded attribute is set to TRUE but I need it to be positionned at FALSE.
I) Anyone could tell me if there is a solution for assigning such partition on such node ?
II) What is "the thread package Forté' ?

Error while Configuring JCO on Solaris

Similar Messages

Maybe you are looking for