Error when creating a JCo destination

Dear All,
I am trying to create a JCo destination using the 'Content Administrator' but am getting the following error:
"Please choose another name for the new JCo destination. The defined name 'SLD_PROBE_XYZ' is used in the SLD."
It seems that whatever name I give the JCo destination, a similar error occurs.
I have read a couple of pdf's on JCo destinations but to no avail. Any pointers would be much appreciated...
Kind Regards
Chris Jackson

>Hi,
> "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed >attempts"
As you can clearly see that logs are stating that user you are entering in JCO destination to connect to backend system has wrong password.
Check the password of the user that you are entering in JCO destination.
Thanks
Sunny

Similar Messages

Error while creating the JCO destinations

Hi All,
I am getting the following error while creating the JCO destinations.
<b>There are no message servers maintained in the associated SLD. Please contact your system administrator.</b>
Please help me in resolving this
Thanks

http://help.sap.com/saphelp_erp2005vp/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Creating New Web AS ABAP Technical Systems
/*Reward if helpful
Message was edited by:
Anant
Message was edited by:
Anant

CUP 5.3 (SP9) Error message when creating a JCO Destination

Dear Experts,
When I try to create a new JCo Destination in Web Dynpro Content Administrator, I get the following error message and I cannot create a connection in CUP:
"com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts"
Please give me some advice if you can.
Thanks,
HM

>Hi,
> "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed >attempts"
As you can clearly see that logs are stating that user you are entering in JCO destination to connect to backend system has wrong password.
Check the password of the user that you are entering in JCO destination.
Thanks
Sunny

Error when trying to create a JCO Destination

Hi
I receives the following error when trying to creat a JCO Destination, clicking on the button in the host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
I get the following error:
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:880)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
     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:274)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:740)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
     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:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     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:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Any ideas?
Regards
Kay-Arne

Hi,
Have you configured your SLD? Check JCO Destination error out or search for "com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus" in the SDN forums.
Best regards,
Vladimir

ERROR WHEN I CREATE A JCo DESTINATIONS

Hi to all
I have the SLD running. I want create two JCo destinatios. I want create a Web Dynpro application with adaptive RFC Model.
But, I login to http:///webdynpro/dispatcher/sap.com/tcwdtools/Explorer
and when I attempt create a JCo destinations, appear the following error:
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:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:985)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
    ... 45 more
Can someone say me, why occurs this error ? I have reviewed all my configuration, but I haven´t found nothing.
Thank you very much.
Regards
Dario Rodriguez

I think while creating the JCOs you must hav left some field with a NULL value.Try to check out that all the connection properties hav been specified correctly also make sure that the connection pooling has a small range.

Error occurs when creating a new destination in HCI OData Provision Administration

Hi,
An error occurs when creating a new destination in HCI OData Provision Administration.
Please see the screen shot in attachment.
Any help will be appreciated!
Thanks,
Li-hua

It's the same issue as in MissingResourceException when trying to create a destination. Changing the destination name should do the trick.
(still looking for the GWaaS colleagues to fix the original issue.)

Publish to portal error when creating a iview

hi gurus,
I have done complete BI-EP integration. SSO is also working fine. But when i publish a query from query designer to portal, i am geting a error when creating a iview for the query as show below.
Error:
Java system error: call FM RSRD_X_MAP_TO_PRTL_USERS_PROXY to ProgId EPD_PORTAL_B07 on host epdev with SSO not authorized: Authentication failed.
when i manually create a BI Query iview,its working fine but to create a iview from publish to portal in query designer it is througing me error.
Regards

yes i have used that tool,,,i am getting below error.
RED
Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
RED
Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
RED
Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Calls from WebAS ABAP to WebAS Java will fail because the certificate of the BI mastersystem is not imported into J2EE ticket keystore Import the certificate to establish a trust relationship -
RED
The issuer DN of the imported ticket 'EPD_certificate' is the same as the issuer DN of SAPLogonTicketKeypair-cert Most likely, you are running an Add-In Installation. See note 917950, section 'Add-In Installation and importing Certificates with identical system ID (SID)' for details Display note 917950
I have checked everything,,but still geting red lights
Regards

Unable to create the Jco destination

Hi Experts,
I am facing a strange issue, As part of ESS and MSS i have to create some Jco destinations in the Wedynpro content administrator.I am giving the all the necessary information for the Jco creation when i click on Finish, jco is not getting creted.
And the status is in Red color...
Can any one help me what i am missing???

Hi Anil,
Hope you are doing good.
Is the SLD up and running?
If the issue persists:
1.)Delete all the JCO destinations from Content Admin and then from SLD
2.)Restart the complete cluster once and do a SLD data trigger.
3.)Then recreate all the jco destinations again from content admin. (Important note: using the "New JCO Message Server Destination" button in SLD will create an inconsistent state. Please do not use it.)
let me know how this goes.
Thank you!
Kind Regards,
Hemanth
SAP AGS

Unable to create a jco destination using remote AS Java system on myjava sy

Dear SAP Gurus,
I had ce 7.1 and nw 2004s based AS java Systems.I want to create a jco destination in my CE 7.1 system using usermapping data of nw 2004s for jco communication.So i created a AS Java system of NW2004s in my CE 7.1 SLD .when i try to create a jco destination using the AS JAVA as Nw2004s system it is not creating .Please help me to solve this issue.
regards,
vanamaSanthosh.

Hi vanamaSanthosh
try this
1. In your CE1 System where u define your JCO destination, Go to C:\WINDOWS\system32\drivers\etc
open hosts file and define the identity of AS System like <IP address> <name of the system>
for example 159.858.2.45 abcd
restart the server and then check.
Best Regards
Satish Kumar

Error when creating index with parallel option on very large table

I am getting a
"7:15:52 AM ORA-00600: internal error code, arguments: [kxfqupp_bad_cvl], [7940], [6], [0], [], [], [], []"
error when creating an index with parallel option. Which is strange because this has not been a problem until now. We just hit 60 million rows in a 45 column table, and I wonder if we've hit a bug.
Version 10.2.0.4
O/S Linux
As a test I removed the parallel option and several of the indexes were created with no problem, but many still threw the same error... Strange. Do I need a patch update of some kind?

This is most certainly a bug.
From metalink it looks like bug 4695511 - fixed in 10.2.0.4.1

Vehicle Scheduling Error:Error when creating transport structures in live C

HI Gurus,
We have one background job defined for Vehicle scheduling, which shows completed successfully but in log it says that :
: Error when creating transport structures in liveCache and Not possible to schedule shipment in the planning horizon.
My planning horizon is for 90 days from current date and demand horizon is for 30 days.
I have checked the VS profile and i dont find any problem with profile.
Can you please help me in finding what exaclty went wrong
Thanks,
AMol

Try This..
1. Open the crystal client on your local machine and import that particular report.
2. Do Database -> Verify Database. Then refresh the report on your PC and make sure that it returns data as expected.
3. Export it back to repository and try scheduling it again. You can verify through CMC for Crystal Reports under " Database Configuration" property to make sure it points to the right ODBC.
Let us know.

Error when creating a folder ,iviews in the portal

Dear sap gurus ,
I m facing a error when creating a Folder or an iview in my portal i'm using EP 7.0 sp11 ,The error is :
Portal Runtime Error
An exception occurred while processing a request for :
<b>iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.defaultFolderWizard
Component Name : com.sap.portal.admin.defaultwizards.DefaultFolderWizard
SQLException is not transient, error code = 1654, sql state = 72000 Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-01654: unable to extend index SAPSR3DB.SYS_C004057 by 128 in tablespace PSAPSR3DB at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.executeBatch(Oracle10gPreparedStatement.java:100) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:991) at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:270) at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:259) at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:518) at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:544) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1374) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1128) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1087) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:843) at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:190) at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:191) at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:254) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:147) at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:624) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:619) at com.sap.portal.admin.wizard.folderwizardpanes.SavePane.doAfterSubmit(SavePane.java:59) at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:356) at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174) at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99) at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98) at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209) at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215) at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753) at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240) at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522) at java.security.AccessController.doPrivileged(Native Method) at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156) 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:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) .
Exception id: 10:50_23/11/07_0005_16892850
See the details for the exception ID in the log file</b>
Thanks and Regards,
sathya

Hi Sathya
The following line in your log tells you what is wrong:
ORA-01654: unable to extend index SAPSR3DB.SYS_C004057 by 128 in tablespace PSAPSR3DB
This is a configuration that you or the dba people need to do. The first thing I would check is if autoextend is on/off on your tablespace PSAPSR3DB. If it's 'off' you either need to put it to 'on' or manually extend the size of your tablespace depending on how much harddrvive space you have to play with. Here is a more detailed solution on how to do it:
Oracle Error : ORA-01654: unable to extend index string.string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Br
Göran

Error when creating a FDM application on SQL Server 2005

Hi,
we are getting this error when creating a FDM application on SQL Server 2005
Error: EPMCSS-07003: Failed to validate identity. Invalid identity . Check identity.[SET_ROLES_LIST]
We are using Windows System Integration although we have also tested with sa user.
Any ideas?
Thanks

Based on the error message it appears to be having a Shared Services issue. Verify that the "ADMIN" account is being used for the HSS connection and that you are using "ADMIN" to create the application and see if the same error is returned.

Error when creating a webpart page in site pages - Sharepoint 2013

Hi,
I am getting Unexpected error when creating a new webpart page in site pages on sharepoint 2013 site.
I have no clue on this.
Any help is much appreciated.
Thank in advance.
Smile Always

Hi Smile,
For troubleshooting this issue, let's verify the followings:
Whether you can create wiki pages well.
Whether this issue occurs for other sties.
Whether all users have this issue. Please test with Site administrator, compare the result.
As Naveen said, please check the log file to find more information about this issue. The path of the log file is: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Error when Creating a ServiceClientFactory instance JAVA API

When invoking Assembling a PDF document quick start I'm having a compilation error when creating a ServiceClientFactory instance:
//Create a ServiceClientFactory instance
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(connectionProps);
The error is: The type com.adobe.idp.Context cannot be resolved. It is indirectly referenced from required .class files
All the required jars are a path.
What esle can be a problem ?
Thanks, Yan

Since you are using SOAP, you need to have the AXIS jars available. They are in the LiveCycle_ES_SDK\client-libs\thirdparty directory:
activation.jar (required for SOAP mode)
axis.jar (required for SOAP mode)
commons-codec-1.3.jar (required for SOAP mode)
commons-collections-3.1.jar (required for SOAP mode)
commons-discovery.jar (required for SOAP mode)
commons-logging.jar (required for SOAP mode)
dom3-xml-apis-2.5.0.jar (required for SOAP mode)
jaxen-1.1-beta-9.jar (required for SOAP mode)
jaxrpc.jar (required for SOAP mode)
log4j.jar (required for SOAP mode)
mail.jar (required for SOAP mode)
saaj.jar (required for SOAP mode)
wsdl4j.jar (required for SOAP mode)
xalan.jar (required for SOAP mode)
xbean.jar (required for SOAP mode)
xercesImpl.jar (required for SOAP mode)

Error when creating a JCo destination

Similar Messages

Maybe you are looking for