Release for transport fails due missing successfull activation request

[Former Member]

Dear colleagues,

I have done some adaptions for an existing DC in the NWDI environment, checked appropriate activities in and activated those. In ChaRM I marked the transport task I need for the transport and would like to release the transport in the "Transport View" of NWDS. Indeed, this fails:

Exception stack:

Nachricht:   Error getting release proposal for system 'XXX' and component 'WSComponent: vendor=xx.xxxx name=XXXXX': No successfull activation request found for activity 'xxxxx' (owner: xxxxxxx , ID: 94555887321c11e684bf0000067a9512, Compartment: xxxxxxxx). In this case only an SCA export with CM Services Export Service is possible. (View menu - Go to Export Service)

[EXCEPTION]

com.sap.di.cts.export.service.api.exception.DIExport_GetReleaseProposalException: Error getting release proposal for system 'XXX' and component 'WSComponent: vendor=xxxxxx name=xxxxxxxx': No successfull activation request found for activity 'xxxxxx' (owner: xxxxxx, ID: 94555887321c11e684bf0000067a9512, Compartment: xxxxxxxx). In this case only an SCA export with CM Services Export Service is possible. (View menu - Go to Export Service)

at com.sap.di.cts.export.service.core.DIExportServiceManager.getReleaseProposalWS(DIExportServiceManager.java:1306)

at com.sap.di.cts.export.service.core.DIExportServiceBean.getReleaseProposalWS(DIExportServiceBean.java:875)

at sun.reflect.GeneratedMethodAccessor1072.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:186)

at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)

at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)

at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)

at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)

at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)

at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:468)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:262)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Ganze Nachricht ausblenden

Gewichtung:   Error

Datum:   2016-07-19

Uhrzeit:   09:08:58:582

Kategorie:   com.sap.di.cts.export.service.core.DIExportServiceBean

Ort:   com.sap.di.cts.export.service.core.DIExportServiceBean.getReleaseProposalWS

Anwendung:   sap.com/tc~di~cts~config~service~appl

Thread:   Thread[HTTP Worker [@1064653176],5,Dedicated_Application_Thread]

Datenquelle:   j2ee/cluster/server0/log/defaultTrace_00.trc

Argumente:   

ID der Passport-Benutzeraktivität:   a97aae374d7f11e6be300000067a9512

Nachrichten-ID:   

Sitzung:   17024

Transaktion:   

Benutzer:   xxxxxx

Zeitzone:   +0200

Kundennachrichtenkomponente:   BC-CTS-CMS

Laufzeitkomponente:   sap.com/tc~di~cts~config~service~appl

Korrelations-ID:   108696850000000005

Passport-Sitzung:   A97AAE374D7F11E6BE300000067A9512

Passport-Verbindung:   

Passport-Verbindungszähler:   0

Host:   dnzjci10

System:   XXX

Instanz:   XXX

Knoten:   server0

Protokoll-ID:   C0008366C05A020F0000000000B7009A

Im probably missing something, since I still have too little knowledge regarding NWDI use, could somebody give me a clue please? Thank you very much,

regards

[former_member189220 · Accepted solution]

Hello Lawrence,

The error messages explains you have to use the "Export SCA".

More details about the symptom of this event in this SAP note:

1909778 - CM Services: Release of activities to CTS+ not working

In order to Use Export Service in NWDS:

This is available from within Transport View in NWDS in the top right.

Doing an export with Export Service of CM Services, the activities should all be released.

http://help.sap.com/saphelp_nw73ehp1/helpdata/EN/87/9a15275b8f4b5382084b385c8b83dc/content.htm

Please let me know if you need some more help.

Regards

[Former Member · Accepted solution]

Milen, thank you very much. I ran through the note and checked the prerequisites for both cases:

-> CBS is higher then 7.31: yes, 7.40 SP12

-> check the delta between activity date and log expiration in CBS buildspace config:

I also dont see any possible problems

Reason 2 would be: different DC in activity and releasing, not the case as far I understood it. Wouldnt even know how to manage something like this at all?

Is it possible the note isnt applicable for my case? Thank you,

cheers

[Former Member · Accepted solution]

In order to Use Export Service in NWDS:
This is available from within Transport View in NWDS in the top right.
Doing an export with Export Service of CM Services, the activities should all be released.
http://help.sap.com/saphelp_nw73ehp1/helpdata/EN/87/9a15275b8f4b5382084b385c8b83dc/content.htm



Please let me know if you need some more help.

Unfortunately I cant go that way, since its explicitly forbidden by the security guidelines of my customer, afaik

cheers

[former_member189220 · Accepted solution]

Hello Lawrence,

The note is correct. I mean it is great that you do meet both the requirements (I was not sure of your NW AS Java version).

However, I am not sure I do fully understand "the security guidelines". Do you mean you do not have access to the CM Services as well?

Please allow me to elaborate...

You enter in Export Service in CM Services - Development Configuration - CTS System

You do select "Export SCA" (this is the 1st step)

In 3rd step "Options" Include Sources should be 'ticked-in' as option (next to Include Archives) Otherwise it is possible the Activities not to be released from NWDS

If this is done you should be able to release this activity in the NWDS.

Provided you still do face problems please would you attach some screenshots from the CM Services as well.

Regards

[Former Member · Accepted solution]

Thank you Milen, I followed your instructions and it worked like a charm. I assumed I will need to add the SCA manualy to my transport package after export, but I was wrong: it automatically was appended on the right package. I was told in the past by some colleagues of my manual adding of any files to ChaRM tickets isnt allowed at all, so I thought the workaround you mentioned isnt possible, sorry my fault. Thank you very much for providing support on this issue,

cheers

[former_member189220 · Accepted solution]

Hi Lawrence,

No bother at all.

I am happy you did manage to solve the problem and you might continue with your software logistics process.

If you face any other issue please let me know.

Regards