on 05-21-2009 4:29 AM
i have created a existing project from DTR. I checked it out. It wasnt checked out by anyone else. I was able to check out various controllers in the DC and edit them.Problem arises when I try to create a new context attribute in component controller and try to map this from Component controller to View Controller. It gives me the warning message that view.xlf and controller.xlf file are already checkout by someone else. But when we check with the person who is appearing to have checked out these files, we find no open activity.
if we ignore this msg and carry on changes, no issues come up in building,activation and release of the component. However when we try to assemble the component, following error comes and assembly fails:
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Creation of PropagationList failed
Has any one experienced such a scenerio. If yes, can you please tell me, how to resolve such an issue.
Edited by: rajeev parmar on May 21, 2009 8:12 AM
Hi rajeev parmar,
Where are you checking for open activity?
To know the opened activity go to the below link and follow the steps:
http://<dtr-server-hostname>:<portnumber>/dtr/system-tools/reports/ActivityQuery
1. Select the workspace.
2. Enter the username in the User field.
3. Check opened only check box
4. Click on show.
It will list out all the open activities for the given user in selected workspace.
Some activities may kept open and will not be listed in the NWDS for the user because of some reasons like:
1. After creating an activity if you delete the NWDS metadata then that activity will not be shown in the NWDS. But still it will be opened activity only and shows warning when you try to check out the same files again.
You can revert such activities in the above mentioned URL.
Coming to assembly error, It is not related to this open activity problem.
Let me know if you need any clarifications.
Regards,
Jaya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi jaya,
Assembly is still failing with this error:
Info:Starting Step Repository-export at 2009-05-21 16:45:11.0325 +8:00
Info:Component:dhl.com/EZYBILL
Info:Version :ZPQ_nEzyBill_C.20090521084511
Info:1. PR is of type TCSSoftwareComponent
Info:the workspace will be read from DTR
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Creation of PropagationList failed
Request path: prop/dhl.com_EZYBILL 20090521164511410
Error Condition: . Response status = 500 (Internal Server Error):communication error: VcmFailure received: Creation of PropagationList failed
Request path: prop/dhl.com_EZYBILL 20090521164511410
Error Condition: . Response status = 500 (Internal Server Error)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Creation of PropagationList failed
Request path: prop/dhl.com_EZYBILL 20090521164511410
Error Condition: . Response status = 500 (Internal Server Error)
at com.sap.cms.tcs.client.DTRCommunicator.readWorkspaceData(DTRCommunicator.java:226)
at com.sap.cms.tcs.client.DTRCommunicator.readWorkspaceData(DTRCommunicator.java:235)
at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:173)
at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:324)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:677)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1510)
at com.sap.cms.pcs.assembly.AssemblyQueueHandler.execAssembly(AssemblyQueueHandler.java:818)
at com.sap.cms.pcs.assembly.AssemblyQueueHandler.startAssembly(AssemblyQueueHandler.java:133)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:829)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startAssembly(LocalCmsTransportProxyLocalObjectImpl0_0.java:2036)
at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:14081)
at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4685)
at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2303)
at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1487)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2520)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:283)
at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:388)
at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:328)
at com.sap.cms.ui.wl.AssemblyOptions.onActionStartAssembly(AssemblyOptions.java:276)
at com.sap.cms.ui.wl.wdp.InternalAssemblyOptions.wdInvokeEventHandler(InternalAssemblyOptions.java:339)
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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
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: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)
Info:Step Repository-export ended with result 'fatal error' ,stopping execution at 2009-05-21 16:45:15.0735 +8:00
Hi rajeev parmar,
Don't know the exact reason why assembly is failing.
But I can say that it is not related to your .xlf file activity problem.
Try to check in Component Build Service (For consolidation workspace) whether all the DC's are build successfully or not.
You can go to component build service by following URL:
You can also find this by:
1. Go to Development Configurations perspective
2. Select Transport View
3. In the Right Corner -> In the Options select "Go to CMS Web UI"
4. Select Component Build Service
Note: Select the buildsapce to Consolidation workspce. (Which is <workspace>_C)
Hope this helps!
Regards,
Jaya.
this issue was due to no free space in DB server. just free space there and issue gets resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.