- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- NWDI - CMS import failed
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
NWDI - CMS import failed
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 02-12-2007 8:37 PM
Hi
I am trying to import the SAP_ESS 600 SP7 componet, but it fails.
I am able to check in SAP_JEE, JTECHS, BUILDT & SAP_PCUIGP. We are on NW2004s SR2
I verified the versions and nwdi server setting they all seem to be fine.
Below is the defaultTrace log ...please advice if you feel that I'm missing out somthing.
Thanks
Mike
log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/applications.log]/>
<!PATTERN[applications.log]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!FILESET[3, 5, 10485760]/>
<!PREVIOUSFILE[applications.2.log]/>
<!NEXTFILE[applications.4.log]/>
<!LOGHEADER[END]/>
#1.5#0017A4A72BC800830000A556000031F40004292E5B650C09#1171178985512#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8# #1.5#0017A4A72BC800830000A559000031F40004292E5B65B142#1171178985543#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java### faces a problem time in sequence#2#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8#6047th# #1.5#0017A4A72BC800830000A55B000031F40004292E5B65B19A#1171178985543#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java### faces the following problem: #2#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8#java.lang.IllegalStateException: CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8 did not confirm instance activity for more than 180 sec.#
-
-
#1.5#0017A4A72BC8008300016654000031F40004292E5B96961B#1171178988746#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8# #1.5#0017A4A72BC8008300016657000031F40004292E5B9696F4#1171178988746#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java### faces a problem time in sequence#2#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8#13105th# #1.5#0017A4A72BC8008300016659000031F40004292E5B969745#1171178988746#/Applications/CBS/Administration##com.sap.tc.cbs.server.rt.impl.Pulsar######a376b2a0b9a111dbbd6c0017a4a72bc8#Thread[CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#com.sap.tc.cbs.server.rt.impl.Pulsar#Java### faces the following problem: #2#CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8#java.lang.IllegalStateException: CBS-Pulsar 12669850/34a5a2d0-b8ea-11db-c111-0017a4a72bc8 did not confirm instance activity for more than 180 sec.#
- SAP Managed Tags:
- SAP NetWeaver,
- NW Java Development Infrastructure (NWDI)
Accepted Solutions (0)
Answers (4)
Answers (4)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Pleae check note 988010
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Michael,
I have exactly the same problem, when I imported SAP ESS and MSS into my track. However other components are fine. How did you solve the problem?
This is the errror trace:
Info:Starting Step Repository-import at 2007-03-20 23:46:31.0403 +8:00
Info:Component:sap.com/SAPPCUI_GP
Info:Version :MAIN_ERP05PAT_C.20061013085939
Info:7. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP_MSS
Info:Version :MAIN_ERP05PAT_C.20061213093103
Info:6. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at java.lang.Throwable.(Throwable.java:179)
at java.lang.Exception.(Exception.java:29)
at com.sap.exception.BaseException.(BaseException.java:247)
at com.sap.cms.util.exception.CMSBaseException.(CMSBaseException.java:69)
at com.sap.cms.tcs.interfaces.exceptions.TCSException.(TCSException.java:16)
at com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException.(TCSCommunicationException.java:9)
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:393)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:335)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:578)
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.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1252)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
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:330)
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:746)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
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: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 com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Your CBS seems to be down.
Check the CBS heartbeat (ping test) using the following link:
<i>http://<hostname>:<port>/tc.CBS.Appl</i>
Regards,
Bhuwan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Chris,
The ESS import ran for several hours and it locked up the system.
The error log from the CMS Gui is as follows:
Info:Starting Step Repository-import at 2007-02-10 17:55:24.0278 -6:00
Info:Component:sap.com/SAP_ESS
Info:Version :MAIN_ERP05VAL_C.20061212075216
Info:1. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Communication error [cause: Socket output stream shutdown by peer.]:communication error: VcmFailure received: Communication error [cause: Socket output stream shutdown by peer.]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Communication error [cause: Socket output stream shutdown by peer.]
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:393)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:335)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:578)
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:1244)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
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)
Thanks for your help
Regards
-Michael
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
It would look into note 988010.
It is not completely the same error message but it is very similar. It explains what to do when an import was not completed. Reason for the note:
<i>Due to an error, the import of a Dtr object (propagation list) by the NWDI was not completed. This incomplete import is not recognized by the NWDI, and causes the repository import to terminate.
</i>
I think your error is similar. Something went wrong because the propagatable is found but the import was not complete (as stated in the error).
Regards,
Christophe
- ABAP RAP - Managed scenario - Create Supplier invoice by Action using EML and I_SUPPLIERINVOICETP in Technology Q&A
- Problem with nativescript plugin when deploying in Technology Q&A
- Instruction of implement-test-deploy flow for SAPUI5 plus CAP integrated with another services in Technology Blogs by Members
- A Comprehensive Guide to the Sustainability Control Tower (SCT) Inbound API in Technology Blogs by Members
- Copy a Tenant Database using system replication in Technology Blogs by SAP
| User | Count |
|---|---|
| 86 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.