Assembly failed on Reository export step

[Former Member]

Hi all,

We are on version 04s SP 10. We are trying to assemble the ESS component but the assembly fails at the Repository export step. Following is the error:

Info:Starting Step Repository-export at 2007-03-24 12:05:32.0500 -4:00

Info:Component:sap.com/SAP_ESS

Info:Version :TDI_ESS3_C.20070324160532

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: Could not perform Export Request. Response status = 500 (Internal Server Error):communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error)

com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Could not perform Export Request. 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:1838)

at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:14080)

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:752)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)

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(AccessController.java:215)

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 2007-03-24 12:22:00.0801 -4:00

It will be great if anyone could help us resolve this issue.

Thanks

[Former Member]

Our issue is fixed. It was a database issue. The saptemp table space was getting filled and thats the reason why it was throwing communication exception. Once we increased the memory, the assembly went on fine.

Thanks for all your help.

[Former Member]

And ESS DCs are not broken.

[Former Member]

Thank you for your replies.

For your questions:

1. We have configured the track correctly with all the urls

2.We have imported the 3 dependencies too. Here I have a question. We have imported the dependencies in development and consolidation tab. Do we have to assemble them in assembly tab too? I mean when we assemble the ESS component do we have to assemble the dependencies too?

3.We are facing the issue only with the ESS component. MSS assembles fine if the checkbox for "assemble even if the DCs are inconsistent" is checked. Since MSS has a broken DC we have to check the checkbox. But ESS fails at the repository export step while assembling.

Thank you

[Former Member]

Hi Laxmi,

As far as i know we should complete the transport cycle till production system for 3 standard dependencies.

So try this and let me know the status of the issue.

Regards

Shobhan

[Former Member]

Hi,

Have you imported other dependencies with ESS from the consolidation system, if not please import those and asseble it. Check your DCs information in CBS if any DCs are broken.

Regards

Suresh

[Former Member]

Hi Laxmi,

I want more inputs from you regarding your issue.

1. Are you sure you have created tack properly with proper DTR, CMS, CBS urls ?

2. Have you transported 3 standard dependencies across your landscape ?

3. Is this occurring only with ESS MSS pacage or with other DC's too ?

We will analyse further after getting these inputs from you.

Regards

Shobhan