cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot import to Test server

Former Member
0 Kudos

I am working through the Scenario 2 Tutorial and got to the end (Step 9) and I'm getting the following error. See the CMS server log below.....

I am SP16 and have done multiple re-installs of SAP J2EE and JDI (NWDI). I'm a loss and don't know where to turn.. Any help would be greatly appreciated..

**************************************

Info:Starting Step SDM-deploy at 2006-03-08 15:25:45.0156 -5:00

Info:start deployment of archives to SDM:http://obcbox:50018

Info:The following archives will be deployed (on http://obcbox:50018)

Info:C:\usr\sap\JTrans\CMS\archives\mycomp.comHELLOWORLDSCJ2E_HWTRK_C~20060308202521.sca

Info:SDM log:

Info:

Info:

Info:

Info:

Info:

Info:

Info:

Info:

Info:Mar 8, 2006 3:25:45 PM Info: -


Starting deployment -


Info:Mar 8, 2006 3:25:45 PM Info: Error handling strategy: OnErrorStop

Info:Mar 8, 2006 3:25:45 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop

Info:Mar 8, 2006 3:25:45 PM Info: Update strategy: UpdateAllVersions

Info:Mar 8, 2006 3:25:45 PM Info: Starting deployment prerequisites:

Info:Mar 8, 2006 3:25:46 PM Info: Loading selected archives...

Info:Mar 8, 2006 3:25:46 PM Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\mycomp.comHELLOWORLDSCJ2E_HWTRK_C~20060308202521.sca'

Info:Mar 8, 2006 3:25:50 PM Info: Selected archives successfully loaded.

Info:Mar 8, 2006 3:25:50 PM Error: Unresolved dependencies found for the following SDAs:

Info:

Info:1.: development component 'appl/tax'/'mycomp.com'/'J2E_HWTRK_C'/'39'

Info:dependency:

Info: name: 'appl/tax/calc'

Info: vendor: 'mycomp.com'

Info:

Info:There is no component either in SDM repository or in Deployment batch that resolves the dependency.

Info:

Info:Deployment will be aborted.

Info:Mar 8, 2006 3:25:50 PM Error: Prerequisites were aborted.

Info:Mar 8, 2006 3:25:50 PM Error: Error while creating deployment actions.

Info:end of log received from SDM

Info:RC of deployment: 12

Info:Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2006-03-08 15:25:50.0468 -5:00

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

As far as i understand many guys land up in error for 'Scenario 2'. i would suggest your can take 'Scenario 2+' or 'Scenario 3' based on your requirement.

Hope that helps.

Regards,

S.Divakar

Former Member
0 Kudos

My fault for not being clear.. I am in fact using Scenario 2+ not Scenario 2 as I previously mentioned

angel_dichev
Active Participant
0 Kudos

Are you sure that the local NWDS build is OK?

Former Member
0 Kudos

He's having the same error during local deployment:

I suggest we continue in that thread, because local deployment should succeed first. Once he's got that up and running he'll also be able to do it in the other runtime systems.

Former Member
0 Kudos

Pascal is correct. I originally started this Post then realized my problem has multi parts that may help with the solution.

I will try and fix my local build first.. Also I have adjusted my environments to only have a Development run-time system since other than my local J2EE server I only have one other server running.

My goal in all of this is to get a development environment running as a proof of concept..

Jarrod

Former Member
0 Kudos

Ok Pascal fixed my problem on my local machine..(see post ). Now I'm back on this problem.

I cannot deploy to my development server.

To give some background on what I have running.

Physically;

I have my local laptop (onn which I have a local J2EE server/MaxDB and IDE). I have one server running Win2K with J2EE (SP16)/MaxDB and JDI(SP16).

In my Landscape Configurator->Runtime Systems I have one runtime system (Development) pointing to my server J2EE.

When I activate and release from NWDS I go into CMS and see my transport under the consolidation tab. When I try and import I get the following error..

Info:Starting Step CBS-make at 2006-03-10 10:25:26.0609 -5:00 Error:CBS error on retrieving current mode: caused by:CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN) com.sap.tc.cbs.client.error.UnknownBuildSpaceException: CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN) at com.sap.tc.cbs.client.error.ErrorMapper.throwError(ErrorMapper.java:33) at com.sap.tc.cbs.client.impl.BuildSpace.getInputMode(BuildSpace.java:220) at com.sap.cms.tcs.client.CBSCommunicator.getInputMode(CBSCommunicator.java:257) at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:85) 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:179) at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376) at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216) at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585) at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101) at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583) at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559) at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1448) at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1279) at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162) at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880) at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338) 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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:CBS server trace: com.sap.tc.cbs.api.NoSuchBuildSpaceException: There is no build space with such identifier: 'J2E_HWTRK_C' at com.sap.tc.cbs.api.impl.CBSFacade.getBSFacade(CBSFacade.java:451) at com.sap.tc.cbs.receiver.CBSReceiverBean.getInputMode(CBSReceiverBean.java:287) at com.sap.tc.cbs.receiver.CBSReceiverObjectImpl0.getInputMode(CBSReceiverObjectImpl0.java:1064) at com.sap.tc.cbs.receiver.CBSReceiver_Stub.getInputMode(CBSReceiver_Stub.java:1096) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy131.getInputMode(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92) at SoapServlet.doPost(SoapServlet.java:51) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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) Fatal:Unexpected exception 'communication error: CBS exception received: CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN)' occurred. Stopping processing. Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: CBS exception received: CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN):communication error: CBS exception received: CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN) com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: CBS exception received: CBS Server Error: The build space is not known on the server( internal code: BS_UNKNOWN) at com.sap.cms.tcs.client.CBSCommunicator.getInputMode(CBSCommunicator.java:266) at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:85) 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:179) at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376) at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216) at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585) at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101) at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583) at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559) at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1448) at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1279) at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162) at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880) at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338) 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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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 2006-03-10 10:25:26.0750 -5:00

I am wondering how I should have my server configured such that I can simulate a development environment.

Jarrod

angel_dichev
Active Participant
0 Kudos

HI Jarrod,

probably there was a change in the system landscape and you have not updated your development configuration.

Can you please check that you have the current version of the development configuration imported to the CONS as well?

Also you can check that from the CBS just see whether all the DCs are imported properly from DEV to CONs and build. SAP standard DCs 161 + your own development.

Regards, Angel

Former Member
0 Kudos

Problem fixed...

Thanks for your help Angel..

I think my main problem was due to the fact that I didn;t have a consolidation runtime system. I added this and did a re-import and things worked.

I guess I got confused with the idea of having a development and consolidation runtime system running on the same server. But based ont he resutls it seems to be ok.

Thanks again,

Jarrod

Message was edited by: Jarrod Littlejohn

angel_dichev
Active Participant
0 Kudos

Thank you Jarrod

Also some more internal information.

A a matter of fact, the runtime systems are not mandatory. Non of them is, even the DEV is not!

The DEV and CONS are build in their CBS Build spaces. If you have runtime systems than the created SCA-s are going to be deployed as well, but even this one you can block with the tab "Disable automatic deploy"

Also you can have one runtime system assigned to both DEV and CONS even to TEST and so, however not good approach.

For the NWDI/CMS this doesn't matter, it's all up to you -how you are going to deploy, test and restore system states when you need to. The CMS only informs you where (in what traks) this system is used.

Regards, Angel