Skip to Content
0
Former Member
Jul 22, 2010 at 05:21 AM

CTS+ PI Export fails: Error retrieving JCO destination

664 Views

I'm setting up CTS+ for my PI landscape. I'm following the instructions in "Best Practices for Implementing CTS+" (April 2008) and "How Tou2026 Configure Enhanced CTS for SAP NetWeaver Exchange Infrastructure 7.0 SPS14" (March 2008).

Things were going well until I tried to export an object. At that point I was prompted to choose an export method and chose "Transport using CTS". This leads to the select objects step which completes successfully.

In the next step (Select Transport Request), however, I stop with an error saying "Error retrieving JCO destination". The log starts out:

====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.misc.api.ResourceException: Error retrieving JCO destination
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getTransportRequest(SyncCtsWrapper.java:127)
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getCtsTransportRequests(SyncCtsWrapper.java:51)
	at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.getCtsTransportRequests(TransportServiceImpl.java:602)
	at com.sap.aii.ib.server.transport.TransportServiceBean.getCtsTransportRequests(TransportServiceBean.java:113)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)

then continues

Serialized cause: com.sap.tc.di.draft.ts.TsConfigurationException: Error retrieving JCO destination
	at com.sap.tc.di.draft.cts.impl.adapters.jco.JCoAdapter.initializeJCo(JCoAdapter.java:69)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.JCoAdapter.<init>(JCoAdapter.java:44)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapterNew.<init>(TmsJCoAdapterNew.java:73)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsFactory.createTmsAdapter(TmsFactory.java:37)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsCommonProvider.createConfiguration(TmsCommonProvider.java:22)
	at com.sap.tc.di.draft.config.ts.RegistrationFactoryImpl.createConfig(RegistrationFactoryImpl.java:56)
	at com.sap.tc.di.draft.ts.impl.TransportManagerImpl.getConfig(TransportManagerImpl.java:96)
	at com.sap.tc.di.draft.ts.impl.TransportManagerImpl.getMyDefaultRequest(TransportManagerImpl.java:70)
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getTransportRequest(SyncCtsWrapper.java:124)

There's nothing here which tells me which JCO destination is missing or misconfigured.

I have configured the CTSserver destination in my dev system's NWA and, for testing purposes, have tested that it connects with my userid and password. (Once I know that this works I'll change that to SSO with SAP logon tickets.)

How do I debug this?

How do I identify the missing or broken JCO destination?