cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Importing .sca files fails

Go to solution
Former Member

on ‎03-31-2006 6:50 AM

0 Kudos

Hi,

I posted this message in NWDS Administrator also. I'm trying to configure NWDI - checking in and importing required SCs.

In the CMS -transport Studio, the three checked in software components(SAP JEE, JTECHS, BUILDT) do not get imported.

The CBSmake.log file has this entry:

Info:Starting Step CBS-make at 2006-03-30 21:24:14.0208 +5:00

Error:Cannot switch to input mode PRIVILEGED, because another import is running into the same buildspace J2E_SS_D

Error:or the buildspace was manually switched to PRIVILEGED by the CBS administrator.

Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-03-30 22:06:46.0608 +5:00

How to resolve this issue?

Thanks

Sumathi

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎03-31-2006 7:00 AM
0 Kudos

Hi Sumathi

Can you switch the mode to OPEN , restart the engine and try again.

Regards

Pran

Show replies
Show replies
Former Member
‎03-31-2006 7:06 AM
0 Kudos

Hi Pran,

How to switch the mode to OPEN? I'm doing this the first time, so please tell me step by step.

Thanks Again

Sumathi

Former Member
‎03-31-2006 7:29 AM
0 Kudos

1. Go to the CBS WebUI

2. Select the buildspace with Input set to PRIVILEGED by clicking the box to the left of the buildspace.

3. Click the Edit button in the topright corner

4. Switch the Input Mode to OPEN

5. Save.

Former Member
‎03-31-2006 10:29 AM
0 Kudos

Hi Pascal,

In CBS WebGUI, there were 2 available buildspaces, one with trackID C (OPEN) and another with TrackID D (PRIVILEGED). I changed J2E SS D input mode to OPEN.

Restarted the server and clicked Import for the three sca files again. Immediately, J2E SS D input mode changed to PRIVILEGED.

I have done this twice now and the status is 'Import Running' for the past 90 minutes.

In log details Repository Import log has the following:

Info:Starting Step Repository-import at 2006-03-31 14:42:13.0843 +5:00

Info:Component:sap.com/SAP_JTECHS

Info:Version :NIGHTLYBUILD.20060209051500

Info:3. PR is of type TCSSoftwareComponent

Info:Component:sap.com/SAP_BUILDT

Info:Version :NIGHTLYBUILD.20060209051100

Info:2. PR is of type TCSSoftwareComponent

Info:Component:sap.com/SAP-JEE

Info:Version :NIGHTLYBUILD.20060209051900

Info:1. PR is of type TCSSoftwareComponent

Info:Step Repository-import ended with result 'not needed' at 2006-03-31 14:42:13.0890 +5:00

-

What does Repository import ended with result NOT NEEDED mean?

There is no entry in the CBS make log.

How to resolve this issue now?

Thanks

Sumathi

Former Member
‎03-31-2006 10:36 AM
0 Kudos

The CBS switches a buildspace to PRIVILEGED when it's building the compartments. If you have something running (like an import) then you should not change the input mode!

When the CBS is done, it will (should) change the input made back to OPEN.

Which SP level of NWDI are you running by the way?

Former Member
‎03-31-2006 10:55 AM
0 Kudos

Hi Pascal,

Am using SP 16.

Initially once i restarted the server and imported the sca files again, CBS switched the buildspace to PRIVILEGED. Have not changed the input mode back to OPEN.

And the status is 'Import Running' for a long time now.

How do I get the sca files imported now?

Thanks Again

Sumathi

Former Member
‎03-31-2006 1:21 PM
0 Kudos

Hi Sumathi

Is your OS where the JDI is hosted IBM AIX ?

Regards

Pran

Answers (1)

Answers (1)

Former Member
‎03-31-2006 3:36 PM
0 Kudos

Hi,

Imported failed for the three .scas and the entry in CBS-make.log is:

Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty

Fatal:There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.

Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.

com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.

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

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

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

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-31 18:43:19.0707 +5:00

Any suggestions to resolve this would greatly help.

Thanks

Sumathi

Show replies
Show replies
Former Member
‎12-12-2006 2:00 PM
0 Kudos

Hi Sumathi,

check the CBS Service Properties, the Value <i>idleStart</i> have to be <b>false</b>.

regards,

dave

Former Member
‎11-06-2007 1:49 PM
0 Kudos

Sumathi .

Did you get any solution to it

Thanks

Rahul

Ask a Question