on 12-02-2009 12:55 PM
Hello,
We installed CTS+ in our PI system landscape (SP14).
I did the configuration as per the guide
How Tou2026 Configure Enhanced CTS for SAP NetWeaver Exchange Infrastructure 7.0 SPS14
Version 1.10 u2013 March 2008
com.sap.tc.di.draft.ts.TsExecutionException: Error executing function (check stacktrace for details):CTS_FILE_APPEND_TO_REQUEST, (service=com.sap.tms) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsServiceException(TmsJCoExceptions.java:72) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsException(TmsJCoExceptions.java:33) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:526) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.handOverAsStream(TmsTransportService.java:253) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.requestUpdate(TmsTransportService.java:202) at
com.sap.tc.di.draft.ts.impl.TransportRequestImpl.transmit(TransportRequestImpl.java:97) at
com.sap.tc.di.draft.ts.impl.TransmissionPackageImpl.transmit(TransmissionPackageImpl.java:49) at
com.sap.aii.ib.server.transport.impl.service.AsyncCtsWrapper.executeCtsRequest(AsyncCtsWrapper.java:91) at
..
I checked the steps thrice, everything is setup as said.
But I still the following error, while trying to attach objects to an already created "Request"
We are longer using CTS+
However the issue was not resolved when we abandoned it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
rest of the log...
com.sap.aii.ib.server.transport.impl.service.CmsAndCtsNotifier.executeCtsRequest(CmsAndCtsNotifier.java:125) at
com.sap.aii.ib.server.transport.impl.service.CmsAndCtsNotifier.processMessage(CmsAndCtsNotifier.java:55) at
com.sap.aii.ib.server.notification.AbstractMessageReceiver.onMessage(AbstractMessageReceiver.java:137) at
com.sap.jms.client.session.Session.run(Session.java:715) 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:102) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.mw.jco.JCO$Exception: (126) REQUEST_ALREADY_CLOSED: Request D3XK900246 can no longer be modified. at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.getException(TmsJCoAdapter.java:152) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:119) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:132) at
com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:521)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gautam,
the problem is ''REQUEST_ALREADY_CLOSED: Request D3XK900246 can no longer be modified'.
This means that the transport request D3XK900246 which is selected for the attachment of your export is already closed (=released).
This means youhave to get a new Transport Request before you can attach the export.
Usually this can only happen if you leave the page "select transport request" in transport export wizard open for to long an the request
which is shown is closed meanwhile by some other action. Please press therefore the "refresh" button within that dialog page.
If the problem persists then use the link "transport organizer" there and check if you really find a not released transport request for
your user there. If not please create one.
Might also be a good idea to turn the auto creation of transport requests on in the STMS -> system overview -> transport tool -> WBO_GET_REQUEST_STRATEGY = Auto.
Best regards
Frank
Hi,
'auto' is not a validt value for the parameter WBO_GET_REQ_STRATEGY. You can use 'SMART or Tagged. Take a look at http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm for details
kind regards
karin
Hi
yes, Karin is right, sorry.
The values in WBO_GET_REQ_STRATEGY are Tagged and Manual
The values for WBO_REL_ REQ_STRATEGY are Smart and Auto
So please try WBO_REL_ REQ_STRATEGY = Auto
In older versions it had been important to use a capital letter 'A'.
So check that you use 'Auto' and not 'auto'. Just to be on the save side.
To examine the problem more in details you can also set the get request strategy
WBO_GET_REQ_STRATEGY = Tagged
This creates automatically a new request if no open request can be found for the given user.
Best regards
Frank
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.