cancel
Showing results for 
Search instead for 
Did you mean: 

Import running for over a week

Former Member
0 Kudos

hi friends

I need to customize XSS business packages using NWDS. I installed JDI and created tracks in CMS. I was able to check in all the required files but when i am trying to import those files, i am not able to import ESS and MSS files. all other files have been imported successfully but for these two files, it is showing import running for over a week now. Has anyone faced a similar situation before? kindly respond if u have the solution.

with thanks

amit

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Guys,

We had the same problems with the ESS imports

failing and running for weeks.

The following article helps.

Thnaks ,

Manab

Former Member
0 Kudos

Hi

I am using SP18 with NWDI, so i think i will not be able to apply the note in my case.

Marc, I checked the details as per ur suggestions and they all seem to be correct. I have imported the other files i.e. SAPpcui_gp,SAP_JTECHS,SAP_JEE.sca, etc. successfully.

As per timeout, I want to tell u that in the meantime, i have restarted the server itself several times. but every time I open the CMS again, it shows me import running. I don't have an idea, how to stop this import so that I can retry or look for problems. The other thing is that log file is also showing empty. there are no details whatsoever of the import process. can u help?

Do u have any idea how can i check the present status or for timeout, if any?

With thanks

amit

Former Member
0 Kudos

Hi Amit,

if you restart CMS the imports will in fact be stuck...

There should be a button "Reset" or "Unlock" that you can use to reset the status. Then you should be able to select a single import and click on the "Detail" button which hopefully shows some more info. Otherwise I'd just check the requests in CBS.

Regarding timeouts: there are some timeouts hardcoded in CMS plus some HTTP-timouts that you can configure for the engine. You can't do anything about the hardcoded values, that just means that CMS reports something as "failed" even if it didn't finish in time and is still working. The HTTP timeouts are part of the postinstallation guide if I remember correctly.

Regards,

Marc

Former Member
0 Kudos

Hi,

Try increasing value for the property 'MaxRequestContentLength' in Visual Admn.(Dispatcher->Services->HTTP Provider->Properties) and choose update.

Restart the service after changing the property.

Regards

Srinivasan T

Former Member
0 Kudos

Hi,

I am able to import the ESS file in CMS but I am getting problem in CBS.

In my case ESS import took 22hours and I got communication error and we restarted the server and I click on the import button, in this time, the import is finished on CMS and I am getting problem in CBS.

This is the error message, I am getting,

Please give me some ideas, what to do.

Thanks,

Balu

Info:Starting Step CBS-make at 2006-09-13 11:23:14.0020 -7:00

Info:wait until CBS queue of buildspace DI1_XSSSP6_D is completely processed, before starting the import

Info:waiting for CBS queue activity

Error:CBS error on activation:

caused by:CBS Server Error: CBS failed to communicate with some other server( internal code: COMMUNICATION_ERROR)

com.sap.tc.cbs.client.error.CBSServerSideCommunicationException: CBS Server Error: CBS failed to communicate with some other server( internal code: COMMUNICATION_ERROR)

at com.sap.tc.cbs.client.error.ErrorMapper.throwError(ErrorMapper.java:309)

at com.sap.tc.cbs.client.impl.BuildSpace.activate(BuildSpace.java:789)

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

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

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

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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)

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

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

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)

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.CommunicationException: HTTP protocol error [reason: Parsing of the response body failed [reason: com.sap.engine.lib.xml.parser.ParserException:

Former Member
0 Kudos

Hi,

Try applying SAP Note 858084 if you are running on NWDI 640 with SP 11 or 12.

Regards

Srinivasan T

Former Member
0 Kudos

Hi Amit,

I suspect that some timeout was reached (or CMS restarted) some time ago and just shows that the import is running. One week is way too long.

Can you check the details for the import? Is CBS doing something? Are there DCs for ESS/MSS in the appropriate CBS buildspaces? Are the sources imported into DTR, i.e. are they visible in DTR webUI?

Regards,

Marc