Assembling ESS component fails in NWDI.

Hello Experts,
Did any one see this error before?
We have checked in all our changes and trying to assemble ESS  component. Now While assembling I finished with errors. Can any suggest waht we need to do?
Do I have to reimport SCA file. But, does the reimport wipe-off all the change which already exist in there.
NWDI 7.0
Following is the error log.
20081030103948 Info   :Starting Step Repository-export at 2008-10-30 10:39:48.0509 -5:00
20081030103948 Info   :Start export of sources
20081030103948 Info   :Component: sap.com/SAP_ESS Version :JDI_Tr713M_C.20081030153947 is processed now.
20081030103948 Info   :1. PR is of type TCSSoftwareComponent
20081030103948 Info   :Start reading sources of SC sap.com,SAP_ESS from DTR http://www.corp
20081030103948 Detail :Start creating PropagationList 'CMS_sap.com_SAP_ESS_22_9b90b2d48e6711ddcd0c001a642a9542'.
20081030105301 Detail :Created PropagationList '0e0dc992a69711ddcc2d001a642a9542'.
20081030105301 Info   :PropagationList CMS_sap.com_SAP_ESS_22_9b90b2d48e6711ddcd0c001a642a9542 added to export.
20081030105301 Info   :Include sources physically into archive.
20081030110346 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error):communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error)
     at com.sap.cms.tcs.client.Export.getContents(Export.java:45)
     at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:167)
     at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
     at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:739)
     at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
     at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
     at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:1096)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl2_0.startAssembly(LocalCmsTransportProxyLocalObjectImpl2_0.java:2302)
     at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:16703)
     at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4845)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2901)
     at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1625)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2991)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:284)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:482)
     at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:402)
     at com.sap.cms.ui.wl.AssemblyOptionsPopup.startAssembly(AssemblyOptionsPopup.java:1360)
     at com.sap.cms.ui.wl.AssemblyOptionsPopup.onActionStartAssemblyAndAttachToCTS(AssemblyOptionsPopup.java:715)
     at com.sap.cms.ui.wl.wdp.InternalAssemblyOptionsPopup.wdInvokeEventHandler(InternalAssemblyOptionsPopup.java:660)
     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:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
20081030110346 Info   :Remove software component SAP_ESS from further processing.
20081030110346 Info   :Step Repository-export ended with result 'error' at 2008-10-30 11:03:46.0265 -5:00

Boiler,
I remember having this issue and we did a restart of the NWDI server and it helped...try it..
Shikhil

Similar Messages

  • Assembly error SAP ESS Component concurrency-lock-denied

    Hi,
    we are always getting the following exception while assembling SAP-ESS Component in our NWDI:
    (Step: Repository-export)
    20101213121125 Info   :PropagationList CMS_sap.com_SAP_ESS_26_4da649762a8311dfca0e005056942f98 added to export.
    20101213121125 Info   :Include sources physically into archive.
    20101213121231 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied":communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied"
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied"
    at com.sap.cms.tcs.client.Export.getContents(Export.java:45)
         at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:167)
         at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:739)
         at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
         at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
         at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
    Any suggestions?
    Our System:  NWDI 7.11 Patch 05
    OS:  Linux (amd64) - SAP DB (7.7.07)

    Hello Golo.
    Can you please recreate the problem whilst running the diagtool?
    Note 1227928 Diagtool for troubleshooting NWDI (detailed logs)
    There might be more information to work on.
    Thanks
    Kenny

  • Error while Assembling the Component in NWDI

    HI All,
    I am trying to assemble the component in NWDI . The assemly is failing .When  i check the log file i get the following log.
    20091125100727 Info   :Starting Step Check-assembly at 2009-11-25 10:07:27.0253 +5:00
    20091125100727 Info   :Checks for software component "xxx "are performed now:
    20091125100728 Info   :list of pending activities:
    20091125100728 Info   :c7f91331bd5611debb78001d091853a3
    20091125100728 Info   :eb437877bd5911dece0a001d091853a3
    20091125100728 Fatal  :Nonempty list of ending activities, stopping export now
    20091125100728 Info   :Checks for software component "xxx "finished succesfully
    20091125100728 Info   :Step Check-assembly ended with result 'fatal error' ,stopping execution at 2009-11-25 10:07:28.0488 +5:00
    Is there anything that i have to do with setting of Patch file numbers.
    Regards,
    Divya

    HI  Pascal,
    I checked in the Consolidation workspace. there are two activities in the consolidation workspace .They are not activated. They were created by mistake i.e instead of doing changes in the  development workspace , the changes were done in consolidation workspace. Is this the cause of the error. If yes how do i revert them. Can i do it normally i mean right click and revert.
    Regards,
    Divya

  • Customizing standard ESS component using WebDynproJava.

    Hi All,
          I am a WebDynpro Java developer. I am new to ESS . My requirement is to customize the Open Enrollment (need to add a pop-up window to the existing Open enrollment flow). Our Portal version is NW 7.0 EPH!1 and NWDS version is NW 7.0.
    Please let me know what all i need to know to customize the standard ESS component and also suggest any document that shows the step by step process starting from NWDI till deploying the customized component in NWDS.

    Hi,
    there you go:
    1. once you need to know how to work with NWDI:
    http://help.sap.com/saphelp_nw04s/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/frameset.htm
    (you can also find the link here to NWDS)
    2. You need to know how to deal with ESS development, here you go, see the guide inside the following note
    #872892 - JDI/NWDI Cookbook for ESS/XSS (http://service.sap.com/sap/support/notes/872892)
    Here you'll find an attachment NWDI.zip, and that includes as PDF file which I kindly ask you to read very carefully even multiple times if necessary.
    Let me know if you need other guides, but I believe this is a plenty of material, but this should be a nice starting point.
    Best Regards,
    Ervin

  • One or more required office component failed to complete successfully for more information, consult the setup log file. while uninstallation of sharepoint 2013

    One or more required office component failed to complete successfully for more information, consult the setup log file. while uninstallation of sharepoint 2013

    go to start > run > type %temp% > here check for latest file and provide us details in that log file
    If this helped you resolve your issue, please mark it Answered

  • Error: Component failed to run due to a Object Package scheduling failure

    Hi,
    BusinessObjects XI R2 SP 5, FP 5.1
    I am trying to schedule a group of reports (crystal reports) via a package where the output destination is to an email. At the event of execution of the scheduled time for the package; the package fails with the error: Component failed to run due to a Object Package scheduling failure. (Note: When scheduled individually it is successful and it was copied to the package from its original location, so there is no mistake in parameters or ODBC connections)
    When we go to the history and within the instance, we see that some of the reports have the status as success and some are failed with the same error message. Even though some of the reports are made to fail at the event of 'NO DATA'; what I do not understand is that how come some of the other reports (which contains data and which works when trying to run manually or scheduled individually) are failing.
    I would understand something is wrong when the entire package fails which is not the case here as say of 50 reports, 5 are successful and the rest fails with the same error.

    Sorry posted on the wrong section...
    Edited by: Deepu Philip on Mar 18, 2010 5:38 PM

  • Problem in importing ESS Component.

    Hi,
        We have problem in importing ESS component from hard drive into server.
    Here is the details
    Comaponent sap.com_SAP_ESS - 600 Level 6 Update ERP05VAL.09201316
    We are importing it through CMS. its been 2 days since we initiate import. but still running.
    Please find the log details below.
    Software Component sap.com/SAP_ESS
    Version MAIN_ERP05VAL_C.20060920131656
    Label 600 Level 6 Update ERP05VAL.09201316
    System XSSTrack-Development
    Step Repository-import
    Log /local/dsk/data1/sap/trans/EPS/in/CMSsapaudev06DD0/CMS/log/XSSTrack_D@DD0/[email protected]
    The Log file does not have any info. empty.
    Please give Ur suggestions
    Cheers,
    Senthil

    Hi,
    the problem seems to be connection to the database or may be database URL is incorrect.
    The problem can be solved via the Visual Administrator or by a manual modification of the data-sources.xml file.
    Visual Administrator --> Server --> Services  -->  JDBC Connector -->Select DataSource
    Change the URL given in the Database URL field with the appropriate one & save it.
    For step by step process refer
    http://help.sap.com/saphelp_nw04/helpdata/en/5c/2f2c4142aef623e10000000a155106/frameset.htm
    Thanks
    Swarup

  • Solution Manager Basic Setting, Get SAP Component fail

    Dear All
    When I execute Solution Manager initial configuration wizard on step:
    Initial configuration part II, it comes out an error: Fetch SAP
    Component fail.
    Can anyone tell me what's the problem, thanks.
    Steps for Reconstruction    
    1) SPRO => Basic Settings => Initial Configuration Part II
    2) Err: SAP Service Marketplace error
    3) manually: Get SAP Components => Edit => Fetch SAP Components => No
    RFC Authorization
    [http://www.mountain.org.tw/sap/090322/B/000.png]
    [http://www.mountain.org.tw/sap/090322/B/010.png]
    [http://www.mountain.org.tw/sap/090322/B/020.png]

    hello,
    Check which user you are using. Use standard user with SAP_ALL authorisation in 000 client.
    This is RFC authorisation issue.
    Regards
    Anju

  • Enhancing standard ESS Component

    Hi Experts,
    I am going to make changes in standard ESS component in WD ABAP through enhancement button given on menu by creating an enhancement implementation. I want to know is it the right way to create enhancement and suppose any enhancement package is applied to the system, In that case changes done in current enhancement will remain same after the new enhancement is installed or not.
    Please provide answers to my queries.
    Thanks and Regards,
    Vaibhav Tiwari.

    thanks  vaibhav for reply....
    I have a requirement that i need to add some custom(Input ) fields in 'Create Travel Request' view of travel and Expense Page of standard ESS . now the  same field  was needed in back-end  in ECC in t-code  TRIP...this  i did  using append structure  in PTK99 and  and  modifying standard  program and screen SAPMP56T 9999 with the  guidelines given in SPRO.
       now the  same thing is to be done in in ESS which is ABAP  WD  application. WD component name is FITV_FPM, but  in this application   contains  viewContainerUIElements on LAYOUT_VIEW  which gets  populated  dynamically..I can create and  Enahancement of this application  and  put  the required  field on the  view  but   still after  doing this, how to store the these data  in back-end???  in back-end  this  data  is stored in PCL1 cluster..
    I feel SAP should have  given some facility for this in ESS like it has given in ECC...

  • ESS import failed

    Hi,
    ESS import failed with the below error
    "CBS throws exception during activation
    caused by Exception:com.sap.tc.cbs.client.error.ComminicationException : Read timed out (Service call excpetion;nested exception is:java.net.SocketTimeoutException:Read time out)"
    please guide the solution
    Thanks a ton

    H Daniel,
    Please check with the Log files and  Notes 872892, Note 1027830
    Read the link as,
    http://help.sap.com/saphelp_nw04/helpdata/en/a6/a4214174abef23e10000000a155106/frameset.htm

  • Cs3 install/repair/reinstall, install component failed-----SOLUTION!!!

    Ok, after searching the internet for solutions on how to install/reinstall/repair CS3, I found I was not satisfied with anyone's answers.
    Well, I've finally got it!
    Do what adobe tells you---run that script (CS3clean).
    However, after running the script, you will notice that the installation will still fail.  So to get around that, go into your folders and delete any folder that says Adobe.  Check your hidden folders too!
                   C:\Users\<your username>\AppData
                             check in local, roaming, and locallow
    There are adobe folders in I think all those locations.  Go to Add/Remove Programs, too and delete anything adobe (I took no chances because installing takes forever, and it's frustrating to see the "component failed to install" message).
    Also as a precaution, I turned off my firewall.
    That did it for me!!!  Good luck, and I hope this helps.

    Ok, after searching the internet for solutions on how to install/reinstall/repair CS3, I found I was not satisfied with anyone's answers.
    Well, I've finally got it!
    Do what adobe tells you---run that script (CS3clean).
    However, after running the script, you will notice that the installation will still fail.  So to get around that, go into your folders and delete any folder that says Adobe.  Check your hidden folders too!
                   C:\Users\<your username>\AppData
                             check in local, roaming, and locallow
    There are adobe folders in I think all those locations.  Go to Add/Remove Programs, too and delete anything adobe (I took no chances because installing takes forever, and it's frustrating to see the "component failed to install" message).
    Also as a precaution, I turned off my firewall.
    That did it for me!!!  Good luck, and I hope this helps.

  • I have a problem with Transport the personalization of standard ess compone

    I have a problem with Transport the personalization of standard ess component.
    My problem is in several components, such as:
    portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/
    com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/
    com.sap.pct.erp.ess.area_personal_information/persinfo_es/com.sap.pct.erp.ess.13.pdata
    I have personalized this page (into rol, not directly in the page), with Ctrl+Right button.
    Now i transport the rol, from Development to Quality environment, but i don't see the changes in Quality.
    My system is NW 7.01 SP7, Can be that the problem?
    Any idea to solve this problem?

    First please see note 1234273 which details how best to personalize
    for all users.
    http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed3ce7f8593eebe10000000
    a1553f7/frameset.htm
    Here you can read:
    "If an iView is transported to another portal all these properties are
    also transported. This is needed to make sure that role-specific changes
    could be transported together with the role. End user personalization
    data is NOT transported in this way as end user personalization is only
    local to the current portal."
    Could you please ensure that personalization was done by an admin user?
    I'm afraid that if it was done by an end user, personalization isn´t
    transported as it's explained in the documentation provided.
    Could you please confirm whether you are using exactly the same language
    to access to both systems, development and quality? Maybe you are using
    language en(us) in one system and en(gb) in the other one. Please take
    into account that personalization is language specific.
    From the web dynpro end, the WebDynpro personalization is stored
    NOT in the PCD prior to 710 release. And as such it cannot be included
    in a portal role transport. This feature is available with NW 7.10 SP2
    or later (from webdynpro point stand). The best option is to
    go with NW 7.30 as this is the first NetWeaver release with EP since
    NW 7.02.

  • How to modify ESS/MSS iviews without NWDI

    Hi Everybody,
    The last couple of day's I have been searching the forums to find an answer to the above mentioned question. Is there a way to modify the ess/mss iviews without NWDI?
    I have tried allmost anything I could think off... Unzip the files and import the files manualy into nwds etc...
    After while I saw a posting that SCA files could be imported in the latest version of NWDS, I was able to import the SCA files of SAP into NWDS 7.1, but I am not able to create a project out of them. Probably this will also lead to issues when uploading the newly build sca files into portal 7.0.
    Can anyone help me?
    Thanks in advance.
    Kind regards,
    Xander

    Hi Xander,
    Some time ago I had the same question as you and as you I tried several things to load the SCA file to NWDS but after several tests it was loaded but without the screens.
    I was able to create the project but it was missing many things when I tried to compile the project,  the reason for this is that the ESS Package has a dependency in other SC as specified in the SAP Note 872892 - JDI/NWDI Cookbook for ESS/XSS (NWDI.zip File).
    When you have all the dependencies (SCA files) it is a bout 700 MB which is a lot to load locally and figuring out exactly what you need  will take a long time so at the end I could not use any trick to avoid the use NWDI as I only had to do 1 change to 1 DC ess/ca/padata so installing NWDI was an overhead for that only change, but at the end I have to do it.
    I found the same posting as you and it seems NWDI 7.1 has the feature to do exactly what we needed.
    But if you want to modify just the iviews as you are mentioning in your post you can do this straight in EP Content after copying your own content from the SAP standard content to do your modifications.
    Best regards,
    Juan Jose

  • CMS import  for SAP ESS component(SP 15) fails with fatal error.

    Hi,
    We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
    20090610145206 Info   :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
    20090610145206 Info   :Component:sap.com/SAP_ESS
    20090610145206 Info   :Version  :MAIN_ERP05PAT_C.20090427083436
    20090610145206 Info   :1. propagation request is of type TCSSoftwareComponent
    20090610145206 Info   :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
    20090610145232 Fatal  :VcmFailure received
    20090610145232 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Fatal  :caused by 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 com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Info   :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
    The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked  with only the last sentence changed to:
    Step Repository-check ended with result 'fatal error'
    Can anyone help me on this.... ?
    Thanks,
    Sonali.
    Edited by: Sonali M S on Jun 10, 2009 1:16 PM

    Hi Bala,
    The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
    Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
    The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
    Can there be any other reason for this?
    Thanks,
    Sonali.

  • ESS603 build fails - new ESS component

    Hi all,
    We are upgrading our ECC system (to EHP4) and the Portal (to EHP1) and now have new ESS components that need to be built in a track in NWDI.The version of ESS is 603 SP04 and its dependencies are V7.01:
    SAP_ESS 603 SP04
    EP_BUILDT03P_1
    SAPJEE03
    SAPBUILDT03
    SAPJTECHS03
    SAPPPCUIGP04
    All the above build fine in Development except SAP_ESS. The failure is:
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090529101345 Fatal  :caused by 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 com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
    Along with in the default trace file:
    #1#java.lang.OutOfMemoryError
    #1#java.lang.OutOfMemoryError
    NOTE: that other builds (MSS, PCUI tracks) are fine. The only one thats failing is the new ESS 603 track.
    Also NWDI was upgraded to EHP1 - enhancement Pack 1 - which is NW7.01. and we have been running on our NWDI system for 3 years now and have many tracks supporting production portals.
    Any insights ?
    Thanks, Neeta

    HI Snehal,
    The JDK version is 1.4.2_20b.
    The Java heap for the server was increased from 2048m to 4096m, restarted the build and now it failes on the CBS import with, in the defaulttrace file, so the good news is that it went further than before but still fails:
    WDI_CMSADM#c7423fd04ead11dea8a900144fec02e0#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/CMS/TCS#Plain###CBS throws exception during activation: Exc=com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
            java.net.SocketTimeoutException: Read timed out)#
    #1.#00144FEC02E000710000001B000013C100046B4B76AB7030#1243871764508#com.sap.cms.tcs.core.TCSLog#sap.com/tcSLCMS~PCS#com.sap.cms.tcs.core.TCSLog#NWDI_CMSADM#43#SAP J2EE Engine JTA Transaction : [1f6843ffffff9e0004b]#sappnwdi_NWD_526926750#NWDI_CMSADM#c7423fd04ead11dea8a900144fec02e0#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/CMS/TCS#Plain###more details on this error:  Exc=java.rmi.RemoteException: Service call exception; nested exception is:
            java.net.SocketTimeoutException: Read timed out#
    Regards, Neeta

Maybe you are looking for