CMS Import Fails

[Former Member]

Hello ,

I am trying to transport a webdynpro change from DEV to QAT using NWDI and during the importing it in the Consolidation system I am getting Import Failed and the following error in CBS log file :

Info:Starting Step CBS-make at 2007-10-26 16:26:39.0337 -5:00

Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Build processing for buildspace: <SID>_ESSz2_C is not enabled. Cannot continue without NWDI administrator action:communication error: Build processing for buildspace: <SID>_ESSz2_C is not enabled. Cannot continue without NWDI administrator action

com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Build processing for buildspace: <SID>_ESSz2_C is not enabled. Cannot continue without NWDI administrator action

at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:335)

at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)

at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)

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.importPropagationRequests(TCSManager.java:376)

at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1150)

at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1307)

at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)

at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)

at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)

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(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 CBS-make ended with result 'fatal error' ,stopping execution at 2007-10-26 16:26:39.0399 -5:00

I wonder for the cause for this ..

Any help would be highly appreciated.

Message was edited by:

SubhashTripathi

[former_member198228 · Accepted solution]

Hello Subash,

The most likely cause is that for build space

request processing mode is set to OFF. Your can check this in

the CBS WebUI. Please Ensure that this flag is set to ON.

Provided that you have CBS admininstrator rights you can set this

property within the CBS WebUI.

http://help.sap.com/saphelp_nw70/helpdata/en/16/bf6d62cee6437389b5051fd9b14202/frameset.htm

The link above gives you instructons on how to edit CBS build space

settings.

Try it again after setting this property.

Regards

Abdul

[Former Member · Accepted solution]

Hello Abdul,

Thanks for the reply. I set it as 'ON' and was able to import it in the Consolidation system but now when I try to Assemble it ...it says :

Components with status scheduled,running,incomplete, finished with errors or failed cannot be assembled again.

Please help..

[Former Member · Accepted solution]

I got it resolved ...thanks for your help.

[Former Member · Accepted solution]

Please post your solution, so other people can benefit from this thread as well.

[Former Member]

Check that your UME roles are configured correctly and that one of the roles assigned to you has the NWDI.Administrator action assigned.