Dirty DCs in NW7.11

Hi,
I have migrated my application to NW7.11.
The CBS build fails because of Dirty DCs. Here is the result in the log file:
20090512174657 Info   :Starting Step CBS-make at 2009-05-12 17:46:57.0199 +2:00
20090512174658 Info   :wait until CBS queue of buildspace MAIN_ST511SP_C is completely processed, before starting the import
20090512174658 Info   :CBS queue of buildspace MAIN_ST511SP_C is completely processed. Starting the import now.
20090512174658 Info   :=================================================================
20090512174658 Info   :buildspace = MAIN_ST511SP_C   build request id = 1602746
20090512174658 Info   :wait until CBS queue of buildspace MAIN_ST511SP_C is completely processed, before asking for build results
20090512174658 Info   :waiting for CBS queue activity
20090512174729 Info   :build process already running: waiting for another period of 30000 ms
20090512174729 Info   :waiting for CBS queue activity
20090512174759 Info   :build process already running: waiting for another period of 30000 ms
20090512174829 Info   :build process already running: waiting for another period of 30000 ms
20090512174829 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512174859 Info   :waiting for CBS queue activity
20090512174929 Info   :build process already running: waiting for another period of 30000 ms
20090512174929 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512174959 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175029 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175059 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175129 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175159 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175229 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175259 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175329 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175359 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175429 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175459 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175529 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175559 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175629 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175659 Info   :waiting for CBS queue activity
20090512175729 Info   :build process already running: waiting for another period of 30000 ms
20090512175729 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175759 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175829 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175859 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175929 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175959 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180029 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180059 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180130 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180200 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180230 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180300 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180330 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180400 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180430 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180500 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180530 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180600 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180630 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180700 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180730 Info   :CBS queue of buildspace MAIN_ST511SP_C is completely processed. Asking for build results now.
20090512180730 Fatal  :the compartment sap.com_STORE_UI_1 contains dirty DCs after the CBS build process:
20090512180730 Info   :dirty DC in compartment sap.com_STORE_UI_1 (dcname=scm/sui dcvendor=sap.com)
20090512180730 Fatal  :Dirty DCs in buildspace sap.com_STORE_UI_1 after the CBS build process
20090512180730 Info   :Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-05-12 18:07:30.0418 +2:00
The current used DCs are:
ENGFACADE
FRAMEWORK
SAP_BUILDT
WD-RUNTIME
Can you please assist?
Thank you and best regards,
Hassane.

Hi Ayyapparaj,
Actually I don't have J2EE installed on my local PC. However I just tried to build the project and I get the following errors:
[javac] ERROR: C:\Documents and Settings\i801193\workspace.jdi\2\t\97D641A4D3B4BBA42480A8F5FF379837\gen_wdp\packages\com\sap\fre\sui\StoreUserInterfaceComp.java:24: package org.apache.xalan.transformer does not exist
[javac] ERROR: C:\Documents and Settings\i801193\workspace.jdi\2\t\97D641A4D3B4BBA42480A8F5FF379837\gen_wdp\packages\com\sap\fre\sui\StoreUserInterfaceComp.java:77: package com.sun.corba.se.internal does not exist
I am wondering if there are missing dependencies in the track.
What doo you think?
Hassane.

Similar Messages

  • All DCs of ESS Mentioned as Dirty DCs in the track

    Hi,
    We are using a Track in the ESS for the Changes.
    All were working fine , we were able to check in code and activate also.
    Some changes done in the Track  and now i saw that all the DCs in the track are in the Broken state.
    In NWDS , we are getting a new configuration messdage.
    If we are using the new configuration, we are getting lots of error in the DC.
    The below is the error trace in the CBS:
    Analyze effect of applied changes to buildspace state... started at 2009-04-21 11:57:50.487 GMT
                INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/bi/bp/webDynpro' DC, does not exist [public-part: webDynpro] AS Build Plugin Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.proxy.framework' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.util.misc' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/cmi' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/ddicruntime' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wdp/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.exception' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.mw.jco' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/logging' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wd/webdynpro' DC, does not exist [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                Skip check for build time dependency cycles. DC metadata is not changed.
    Thanks,
    Anumit

    Thanks Pascal,
    Now , i am able to reimport the mentioned DCs. But when i am activating any activity then getting the below error log:
    Build number assigned: 11970
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2009-04-22 08:31:05.378 GMT
        ACTIVATION request in Build Space "EPD_XSSTRACK_D" at Node ID: 15,357,950
         [id: 10,985; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 58 ms
        ===== Pre-Processing =====  started at 2009-04-22 08:31:05.437 GMT
            List of requested for activation activities:
                'sap.com_SAP_ESS_1' compartment
                    medicalrem_remove_info_from _test
                        [ISN 53][created by J2EE_ADMIN at 2009-04-14 14:33:18.0][OID 95c9ff2928d211de878900144fa0ee66]
                There is 1 activity in compartment sap.com_SAP_ESS_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2009-04-22 08:31:05.667 GMT
                Analyzing predecessors in compartment "sap.com_SAP_ESS_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2009-04-22 08:31:05.801 GMT and took 134 ms
            Analyze versions... started at 2009-04-22 08:31:05.802 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2009-04-22 08:31:06.454 GMT and took 527 ms
                Synchronize metadata for [sap.com/medirem] started at 2009-04-22 08:31:06.510 GMT
                    Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:06.623 GMT and took 39 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:06.696 GMT and took 72 ms
                Synchronize metadata for [sap.com/medirem] finished at 2009-04-22 08:31:06.702 GMT and took 192 ms
                < CHANGE > 'sap.com/medirem' DC
            Analyze versions... finished at 2009-04-22 08:31:06.704 GMT and took 902 ms
            Analyze activities... started at 2009-04-22 08:31:06.705 GMT
                Loading component definitions
                1 component to be build in compartment "sap.com_SAP_ESS_1"
            Analyze activities... finished at 2009-04-22 08:31:06.793 GMT and took 88 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2009-04-22 08:31:06.824 GMT
                    'sap.com/medirem' variant 'default'
            Analyze request DC BV... finished at 2009-04-22 08:31:07.510 GMT and took 686 ms
            Prepare build environment in the file system... started at 2009-04-22 08:31:07.511 GMT
                Synchronize development configuration... started at 2009-04-22 08:31:07.512 GMT
                Synchronize development configuration... finished at 2009-04-22 08:31:07.517 GMT and took 5 ms
                Synchronize sources for [sap.com/medirem] started at 2009-04-22 08:31:07.563 GMT
                    Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:13.251 GMT and took 47 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:14.615 GMT and took 1 s 363 ms
                Synchronize sources for [sap.com/medirem] finished at 2009-04-22 08:31:15.273 GMT and took 7 s 710 ms
                Synchronize used libraries... started at 2009-04-22 08:31:15.584 GMT
                    DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
                    Used DC 'sap.com/tc/cmi' HAS NO PUBLIC PART 'default'.
                    [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 211 variant 'default'][SCID=76][last successful build: 11532]
                    DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
                    Used DC 'sap.com/tc/ddic/ddicruntime' HAS NO PUBLIC PART 'default'.
                    [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 217 variant 'default'][SCID=76][last successful build: 11532]
                    DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
                    Used DC 'sap.com/tc/ddic/metamodel/content' HAS NO PUBLIC PART 'default'.
                    [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 218 variant 'default'][SCID=76][last successful build: 11532]
                    DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
                    Used DC 'sap.com/tc/wd/webdynpro' HAS NO PUBLIC PART 'default'.
                    [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 85 variant 'default'][SCID=72][last successful build: 11532]
                    DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
                    Used DC 'sap.com/tc/logging' HAS NO PUBLIC PART 'default'.
                Synchronize used libraries... finished at 2009-04-22 08:31:18.845 GMT and took 3 s 261 ms
        ===== Pre-Processing =====  finished at 2009-04-22 08:31:18.878 GMT and took 13 s 441 ms
        Change request state from PROCESSING to FAILED
    Thanks,
    Anumit

  • How to remove Dirty DCs

    We are using JDI for version control. when I try to import
    a DC into consolidation cbs make failed indicating that a
    dirty dc exists. The dc compiled well in the dev build space. Because of this dirty dc all other imports are failing. Any help would be appreciated.

    Hi,
    Till JDI SP9 version there is no option for deleting DC ot workspace/workspace folders, if you are using sp11 i hope it is possible. AS you are aware that you can delete subtrees directly from NWDS,(In checkout mode). Another possiblity is command prompt of your dtrshell.bat
    excute the command >deleteworkspace -w "Folderpath" before excuting this command Make sure that " For your project/Workspace for you User enough previlages are given i mean ACL are enabled" right click on your workspace and ACL's have you given read,write, modify enabled.
    Here is a URL, it is the only place where i found little bit info about Deleting Resources From the Client Workspace
    http://help.sap.com/saphelp_nw04/helpdata/en/96/5cc5d7a3e741d3905e37d460c4d8c3/frameset.htm
    Working With the DTR -> Basic Operations in the DTR->
    1)Deleting Resources From the Repository
    2)Deleting Resources From the Client Workspce
    Hope this solves your problem!
    Regards,
    RK

  • Difference between Dirty and Broken DCs

    Hi All
    Can any one explain me difference between Dirty and Broken DCs? And also please explain me what might be solution if we see any broken or dirty DC?

    hello,
    see [here|http://help.sap.com/saphelp_nw70/helpdata/en/46/14fa07c15214dce10000000a155369/frameset.htm] - the two links under "6. (Optional) Fix the broken and dirty DCs that might appear after the build".
    Regards, Jordan

  • CMS import failure - ESS (Dirty DC)

    Hi jdi gurus,
    Please help out ...
    the MSS, pcui, buildt, jee, jtech packages have been imported successfully into development and consolidation.
    however the ess package is not being imported into development.
    with respect,
    amit
    WebAS 640, EP 6.0, SP 13 on Windows with MS SQL server, ESS 100, SP 9.
    CMS-make
    Info:Starting Step CBS-make at 2006-09-14 17:03:44.0842 +12:00
    Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before asking for build results
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms (1)
    Info:CBS server log has been written to CBS log
    Fatal:the compartment sap.com_SAP_ESS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre dcvendor=sap.com)
    Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre/trs dcvendor=sap.com)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-09-14 17:04:18.0077 +12:00
    CBS Log :-
      CBS Request Log - [  295/EPD_ESSTrack_D  ]
      devep SAP Component Build Server   
    Build number assigned: 305
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
         [id: 295; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         sap.com/ess/tra/tre/trs
         sap.com/ess/mx/addr
         sap.com/ess/fr/addr
         sap.com/ess/tra/trp
         sap.com/ess/de/fam
         sap.com/ess/br/addr
         sap.com/ess/tra
         sap.com/ess/au
         sap.com/ess/tra/tre
         sap.com/ess/it/pdata
         sap.com/ess/hk/fam
         sap.com/ess/us/pdata
         sap.com/ess/tw/fam
         sap.com/ess/sg/addr
         sap.com/ess/de/pdata
         sap.com/ess/ca/addr
         sap.com/ess/kr/bank
         sap.com/ess/be/fam
         sap.com/ess/us
         sap.com/ess/kr/fam
         sap.com/ess/ar/addr
         sap.com/ess/hk/addr
         sap.com/ess/ph/pdata
         sap.com/ess/wtcor
         sap.com/ess/us/addr
         sap.com/ess/at/addr
         sap.com/ess/mx/pdata
         sap.com/ess/wiw
         sap.com/ess/ca/empeq
         sap.com/ess/th/bank
         sap.com/ess/dk/fam
         sap.com/ess/tw/bank
         sap.com/ess/th/pdata
         sap.com/ess/grt/srv
         sap.com/ess/be/bank
         sap.com/ess/mx/fam
         sap.com/ess/es/fam
         sap.com/ess/at/pdata
         sap.com/ess/ie/fam
         sap.com/ess/ch/fam
         sap.com/ess/id/addr
         sap.com/ess/xx
         sap.com/ess/ca/pdata
         sap.com/ess/nz/pdata
         sap.com/ess/de/dcomp
         sap.com/ess/gb/pdata
         sap.com/ess/au/addr
         sap.com/ess/th/fam
         sap.com/ess/cn/bank
         sap.com/ess/ve/bank
         sap.com/ess/nl/fam
         sap.com/ess/es/bank
         sap.com/ess/sg/perid
         sap.com/ess/skl
         sap.com/ess/cat
         sap.com/ess/nl/addr
         sap.com/ess/fr/pdata
         sap.com/ess/se/pdata
         sap.com/ess/au/bank
         sap.com/ess/ben
         sap.com/ess/lea
         sap.com/ess/it/addr
         sap.com/ess/ie/bank
         sap.com/ess/au/pdata
         sap.com/ess/th/pid
         sap.com/ess/be/pdata
         sap.com/ess/id/bank
         sap.com/ess/de/addr
         sap.com/ess/nz/bank
         sap.com/ess/tra/tri
         sap.com/ess/jp/addr
         sap.com/ess/au/rep
         sap.com/ess/us/w4
         sap.com/ess/us/bank
         sap.com/ess/rep
         sap.com/ess/nz/addr
         sap.com/ess/za/pdata
         sap.com/ess/tra/trr
         sap.com/ess/cn/addr
         sap.com/ess/de
         sap.com/ess/be/addr
         sap.com/ess/tw/pdata
         sap.com/ess/my/addr
         sap.com/ess/hk/perid
         sap.com/ess/cod
         sap.com/ess/th/addr
         sap.com/ess/gb/fam
         sap.com/ess/au/tax
         sap.com/ess/us/fam
         sap.com/ess/ch/pdata
         sap.com/ess/ca/bank
         sap.com/ess/ie/addr
         sap.com/ess/ca/fam
         sap.com/ess/za/fam
         sap.com/ess/se/bank
         sap.com/ess/jp/bank
         sap.com/ess/fr/fam
         sap.com/ess/ve/fam
         sap.com/ess/ve/pdata
         sap.com/ess/sg/fam
         sap.com/ess/ph/bank
         sap.com/ess/sg/bank
         sap.com/ess/au/fam
         sap.com/ess/sg/pdata
         sap.com/ess/sg
         sap.com/ess/ve/addr
         sap.com/ess/com
         sap.com/ess/ar/pdata
         sap.com/ess/gb/addr
         sap.com/ess/nl/pdata
         sap.com/ess/kr/addr
         sap.com/ess/tw/pid
         sap.com/ess/no/pdata
         sap.com/ess/cn/fam
         sap.com/ess/hk/bank
         sap.com/ess/es/pdata
         sap.com/ess/pt/bank
         sap.com/ess/se/fam
         sap.com/ess/id/fam
         sap.com/ess/dk/pdata
         sap.com/ess/jp/pdata
         sap.com/ess/no/fam
         sap.com/ess/at/bank
         sap.com/ess/it/fam
         sap.com/ess/per
         sap.com/ess/br/fam
         sap.com/ess/ie/pdata
         sap.com/ess/pt/pdata
         sap.com/ess/gb/bank
         sap.com/ess/hk/pdata
         sap.com/ess/my/pdata
         sap.com/ess/jp/fam
         sap.com/ess/za/bank
         sap.com/ess/tw/addr
         sap.com/ess/mx/bank
         sap.com/ess/ar/bank
         sap.com/ess/cn/pdata
         sap.com/ess/pt/addr
         sap.com/ess/at/fam
         sap.com/ess/rem
         sap.com/ess/my/bank
         sap.com/ess/it/bank
         sap.com/ess/br/pdata
         sap.com/ess/nl/bank
         sap.com/ess/ch/addr
         sap.com/temp/testit0188
         sap.com/temp/testit0185
         sap.com/temp/testit0006_au
         sap.com/temp/pers_data_sg
         sap.com/temp/essmenu
         sap.com/temp/ESS_Homepage
         sap.com/temp/bentest
         sap.com/temp/address_sg
         sap.com/ess/id/pdata
         sap.com/ess/de/bank
         sap.com/ess/tim
         sap.com/ess/my/fam
         sap.com/ess/se/addr
         sap.com/ess/kr/pdata
         sap.com/ess/ar/fam
         sap.com/ess/no/bank
         sap.com/ess/pt/fam
         sap.com/ess/nz/fam
         sap.com/ess/no/addr
         sap.com/ess/tra/trp/trt
         sap.com/ess/dk/bank
         sap.com/ess/ph/fam
         sap.com/ess/ch/bank
         sap.com/ess/es/addr
         sap.com/ess/id/pid
         sap.com/ess/org
         sap.com/ess/dk/addr
         sap.com/ess/ph/addr
         sap.com/ess/my/pid
         sap.com/ess/za/addr
         sap.com/ess/fr/bank
         sap.com/ess/br/bank
         sap.com/ess/tri
         sap.com/ess/trt
         sap.com/ess/tev
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Analyse activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
         Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment sap.com_SAP_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms
    Message was edited by: Amit Chawathe

    Hi Marc,
    Thank you for your time and attention to the problem at hand. It is most appreciated.
    The CBS log life of the request in question is pasted below.Please let me know if there is any more information you would require.
    with respect,
    amit
      CBS Request Log - [  295/EPD_ESSTrack_D  ]
      devep SAP Component Build Server   
    Build number assigned: 305
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
         [id: 295; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         sap.com/ess/tra/tre/trs
         sap.com/ess/mx/addr
         sap.com/ess/fr/addr
         sap.com/ess/tra/trp
         sap.com/ess/de/fam
         sap.com/ess/br/addr
         sap.com/ess/tra
         sap.com/ess/au
         sap.com/ess/tra/tre
         sap.com/ess/it/pdata
         sap.com/ess/hk/fam
         sap.com/ess/us/pdata
         sap.com/ess/tw/fam
         sap.com/ess/sg/addr
         sap.com/ess/de/pdata
         sap.com/ess/ca/addr
         sap.com/ess/kr/bank
         sap.com/ess/be/fam
         sap.com/ess/us
         sap.com/ess/kr/fam
         sap.com/ess/ar/addr
         sap.com/ess/hk/addr
         sap.com/ess/ph/pdata
         sap.com/ess/wtcor
         sap.com/ess/us/addr
         sap.com/ess/at/addr
         sap.com/ess/mx/pdata
         sap.com/ess/wiw
         sap.com/ess/ca/empeq
         sap.com/ess/th/bank
         sap.com/ess/dk/fam
         sap.com/ess/tw/bank
         sap.com/ess/th/pdata
         sap.com/ess/grt/srv
         sap.com/ess/be/bank
         sap.com/ess/mx/fam
         sap.com/ess/es/fam
         sap.com/ess/at/pdata
         sap.com/ess/ie/fam
         sap.com/ess/ch/fam
         sap.com/ess/id/addr
         sap.com/ess/xx
         sap.com/ess/ca/pdata
         sap.com/ess/nz/pdata
         sap.com/ess/de/dcomp
         sap.com/ess/gb/pdata
         sap.com/ess/au/addr
         sap.com/ess/th/fam
         sap.com/ess/cn/bank
         sap.com/ess/ve/bank
         sap.com/ess/nl/fam
         sap.com/ess/es/bank
         sap.com/ess/sg/perid
         sap.com/ess/skl
         sap.com/ess/cat
         sap.com/ess/nl/addr
         sap.com/ess/fr/pdata
         sap.com/ess/se/pdata
         sap.com/ess/au/bank
         sap.com/ess/ben
         sap.com/ess/lea
         sap.com/ess/it/addr
         sap.com/ess/ie/bank
         sap.com/ess/au/pdata
         sap.com/ess/th/pid
         sap.com/ess/be/pdata
         sap.com/ess/id/bank
         sap.com/ess/de/addr
         sap.com/ess/nz/bank
         sap.com/ess/tra/tri
         sap.com/ess/jp/addr
         sap.com/ess/au/rep
         sap.com/ess/us/w4
         sap.com/ess/us/bank
         sap.com/ess/rep
         sap.com/ess/nz/addr
         sap.com/ess/za/pdata
         sap.com/ess/tra/trr
         sap.com/ess/cn/addr
         sap.com/ess/de
         sap.com/ess/be/addr
         sap.com/ess/tw/pdata
         sap.com/ess/my/addr
         sap.com/ess/hk/perid
         sap.com/ess/cod
         sap.com/ess/th/addr
         sap.com/ess/gb/fam
         sap.com/ess/au/tax
         sap.com/ess/us/fam
         sap.com/ess/ch/pdata
         sap.com/ess/ca/bank
         sap.com/ess/ie/addr
         sap.com/ess/ca/fam
         sap.com/ess/za/fam
         sap.com/ess/se/bank
         sap.com/ess/jp/bank
         sap.com/ess/fr/fam
         sap.com/ess/ve/fam
         sap.com/ess/ve/pdata
         sap.com/ess/sg/fam
         sap.com/ess/ph/bank
         sap.com/ess/sg/bank
         sap.com/ess/au/fam
         sap.com/ess/sg/pdata
         sap.com/ess/sg
         sap.com/ess/ve/addr
         sap.com/ess/com
         sap.com/ess/ar/pdata
         sap.com/ess/gb/addr
         sap.com/ess/nl/pdata
         sap.com/ess/kr/addr
         sap.com/ess/tw/pid
         sap.com/ess/no/pdata
         sap.com/ess/cn/fam
         sap.com/ess/hk/bank
         sap.com/ess/es/pdata
         sap.com/ess/pt/bank
         sap.com/ess/se/fam
         sap.com/ess/id/fam
         sap.com/ess/dk/pdata
         sap.com/ess/jp/pdata
         sap.com/ess/no/fam
         sap.com/ess/at/bank
         sap.com/ess/it/fam
         sap.com/ess/per
         sap.com/ess/br/fam
         sap.com/ess/ie/pdata
         sap.com/ess/pt/pdata
         sap.com/ess/gb/bank
         sap.com/ess/hk/pdata
         sap.com/ess/my/pdata
         sap.com/ess/jp/fam
         sap.com/ess/za/bank
         sap.com/ess/tw/addr
         sap.com/ess/mx/bank
         sap.com/ess/ar/bank
         sap.com/ess/cn/pdata
         sap.com/ess/pt/addr
         sap.com/ess/at/fam
         sap.com/ess/rem
         sap.com/ess/my/bank
         sap.com/ess/it/bank
         sap.com/ess/br/pdata
         sap.com/ess/nl/bank
         sap.com/ess/ch/addr
         sap.com/temp/testit0188
         sap.com/temp/testit0185
         sap.com/temp/testit0006_au
         sap.com/temp/pers_data_sg
         sap.com/temp/essmenu
         sap.com/temp/ESS_Homepage
         sap.com/temp/bentest
         sap.com/temp/address_sg
         sap.com/ess/id/pdata
         sap.com/ess/de/bank
         sap.com/ess/tim
         sap.com/ess/my/fam
         sap.com/ess/se/addr
         sap.com/ess/kr/pdata
         sap.com/ess/ar/fam
         sap.com/ess/no/bank
         sap.com/ess/pt/fam
         sap.com/ess/nz/fam
         sap.com/ess/no/addr
         sap.com/ess/tra/trp/trt
         sap.com/ess/dk/bank
         sap.com/ess/ph/fam
         sap.com/ess/ch/bank
         sap.com/ess/es/addr
         sap.com/ess/id/pid
         sap.com/ess/org
         sap.com/ess/dk/addr
         sap.com/ess/ph/addr
         sap.com/ess/my/pid
         sap.com/ess/za/addr
         sap.com/ess/fr/bank
         sap.com/ess/br/bank
         sap.com/ess/tri
         sap.com/ess/trt
         sap.com/ess/tev
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Analyse activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
         Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment sap.com_SAP_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms

  • DCs are broken in consolidation only

    Hi All
    I have a Software component which is imported from an old NWDI
    I the new NWDI I have a track consist of this SC + the 3 standard SCs (JEE, JTECHS and BUILDT)
    I have checked-in all the components into the transport studio. And transported them all the way to assembly.
    The SCs are all building perfectly in development.
    l have  also checked out all DCs in NWDS, all DCs are compiling as they should here also.
    But, when I try to assemble the components on the server I get error messages. (The Check-assembly.log file)
    Info:Starting Step Check-assembly at 2011-02-21 15:56:24.0882 +1:00
    Info:Checks for software component mycorp.com,COMMON are performed now:
    Fatal:Contact CBS administrator: Nonempty list of broken DCs -stopping export now
    Error:list of broken DCs:
    Info:Step Check-assembly ended with result 'fatal error' ,stopping execution at 2011-02-21 15:11:32.0190 +1:00
    If I look into CBS BuldSpaces Information, I have this these information regarding the DCs
    TRACK_C:  Total DCs: 17, Broken DCs: 17, Dirty DCs 0
    TRACK_D:  Total DCs: 189, Broken DCs: 0, Dirty DCs 0
    To me it looks like the SC from SAP is somehow not available for assembly, but when I read the log statement, It only mentions the DCs from my own SC.
    The three SCs is available on the test tab, so I know that they have been assembled succesfully.
    Best Regards
    Søren Madsen

    Hi Søren,
    it is indeed then very strange how comes that the DCs haven't been imported in the first place (I mean the "Total DCs" column that displays 0 for the CONSolidation buildspace). You said that the import into the consolidation was succesful ("import finished" for each SCs on Consolifation tab of the "Transport Studio of CMS") .
    Can you please confirm the followings?
    1 a Restore System State in CONS, and a new import of all the SCs brings no solution, but still 0 is displayed in CBS webui, however CMS states that import finished succesfully in case of each SC imports.
    2 deleting the CONS buildspace, (you can do it in the main "Buildspace" view of CBS webui), resaving the track (this will recreate _C) and proceeding as described in point 1 brings no solution. Please delete only _C.
    3 As you know an import stands of "a) DTR Repository import, b) CBS-Make and c) Deployment". If you go to the "History" of the Consolidation tab (in CMS), you list the imports took place in the past, and you click on a finished import, and press the "Details..." button, you can confirm that all of these 3 steps were really succesful as per the logs and traces. Do the same for each SC.
    You also stated that after you faced this phenomenon, you tried a restore system state in DEV, and tried a new import and it was succesful. Can you please check the History, and via that all the Log Details (as mentioned above) of all the imported SCs ? Were the imports really succesful ? Can you try again a Restore System State in DEV and a reimport after you resave the track ? Are the SC still not displayed on the CONS tab after a succesful import on the Development tab ?
    I hope this helps.
    Thank you!
    Best Regards,
    Ervin

  • Broken DCs & activation view

    Hi,
    I have created new WDJ DC project in MSS Component e.g mss/transfer using the same track.
    My Project is working fine without any issues, no build errors or no activation errors.
    Now i'm trying to release this project but i not able to do that.
    After check-in my request is long time waiting under the Activation View, it is not moving to the Transport view at all.
    I viewed the Component Build Service(CBS), status is like below.
    Buildspaces
    TRACK_D = Total Dcs : 205, Broken Dcs : 205, Dirty Dcs : 0, Active : YES, input : Open, Request Processing: ON
    & TRACK_C is same but Broken Dcs is 179 .
    Requests
    Request ID :   2,840
    Request State: FAILED
    Request Type: ACTIVATE
    so what to do next?
    Regards
    Ali

    HI,
    1) There might be some Dependent DCs  for the DC you have created and they might  not be deployed .
    IDentify them any deploy them from NWDS. in DC perspective, you can right click on the dependent DCs and deploy.
    2) The other reason can be may be you have not checked in some of the activities in which the Dependent DCs were modified.
    so if there are any, check  in them and try to activate again .
    Regards,
    Satya.
    Edited by: Satya on Aug 20, 2009 2:59 PM

  • Used DCs issue

    Hello,
    I have a issue with adding used DCs.
    I have one external library DC...say "extlib"
    This has all the jar files required.
    I have one Portal standalone DC...say "portaldc1"
    This portal dc has java classes in the src.API package. These classes require the jars in extlib.
    I have one web dynpro DC....say "webdc1"
    This webdc1 uses classes in portaldc1 and also require extlib.
    What kind of public parts do I have to create and add as used DCs.
    I also want to make sure that, when I make changes to any classes in "portaldc1", I just build and redeploy "portaldc1"...I do not want to build and redeploy "webdc1" each time I change portaldc1.
    Is this achievable?
    Any help is greatly appreciated.
    Thanks
    MLS

    Hi Laxmi,
    I am considering that you are using a NWDI environment. Otherwise it is not possible to used DC unless if you are doing a local development. In case of a local development it does not matter if you dont rebuild the using DC as the locally (in NWDS) you will know if the DC is broken.
    But if the development is under NWDI control, then NWDI-CBS will display the using DC has dirty in the build space. They will be rebuild by NWDI.
    Please refer to the following link on broken and dirty dcs:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Regards,
    Kartikaye

  • JTECH import fails with error Dirty DC

    Hi guys,
    We are on NW2004 s SP 7. I am trying to import JTECH7P and the import is failing with error dirty Dcs.
    Can anyone tell me where the error is? Is it due to incompatible to JTECH patch with my NWDI and EP system.
    Can some one give me matrix of which SP and patch for source codes JTECH ESS MSS BUILD JEE are required for NW2004s J2EE SP 7.
    Can some one point me to a note similar to 761266. I think 761266 this note does not have NW2004s related etails
    appreciate any help.
    regards
    Sam

    Ufuk Altinkaynak schrieb:
    > Dave Parkes schrieb:
    >> Stored in an external storage area, or under the post office ?
    >>
    >
    > Hello Dave,
    >
    > when using post office storage error is C06A, when using an external
    > storage, the error is C06B.
    >
    > If you have any hints/ solution or can say something about the charge,
    > that would be a huge help
    >
    Updated Information,
    Just to be sure about the C06B error, i created an new Library with
    external storage, than i draged and droped an *.txt file into documents
    (no the funny part) imported without any erors into the default library
    (that one with post office storage, that had before C06A errors)
    No i can use the library (with postoffice storage) without any erros.
    The only change on that system, was to create an additional library with
    external storage
    As every good side has a bad side, this bad side is, that i cannot
    import any documents into the library with external storage, the error i
    receive is C06B
    I have no clue why creating an additional librarry has fixed the first
    error, but hopefully this makes sence for someone, and hopefully anyone
    can help on the second error / Problem:
    C06B Error while importing into a library with external storrage
    regards
    Ufuk Altinkaynak

  • Cbs build portal application dc fail.  Build Plugin IS NOT DEFINED for this

    hi all
    I use NW7.0 ehp1,have portal and a nwdi.
    I create a track at nwdi . and develop a portal application .
    local build is ok . but when i check in .run a activitce.  dc is broken.
    log is -
    CBS Request Log - [  300/DEP_PESKM_D  ]
    Build number assigned: 314
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2010-11-05 02:17:38.921 GMT
        ACTIVATION request in Build Space "DEP_PESKM_D" at Node ID: 13,975,650
         [id: 300; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 79 ms
        ===== Pre-Processing =====  started at 2010-11-05 02:17:39.000 GMT
            List of requested for activation activities:
                'deep.com_PESKM_1' compartment
                    tet
                        [ISN 111][created by YANLIANG at 2010-11-05 10:17:31.0][OID 6b2f604ae87c11df94ff000000d54062]
                There is 1 activity in compartment deep.com_PESKM_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2010-11-05 02:17:39.031 GMT
                Analyzing predecessors in compartment "deep.com_PESKM_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2010-11-05 02:17:39.046 GMT and took 15 ms
            Analyze versions... started at 2010-11-05 02:17:39.046 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-11-05 02:17:41.812 GMT and took 2 s 766 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] started at 2010-11-05 02:17:41.812 GMT
                    Verification of DL [ws/PESKM/deep.com_PESKM/dev/active/] finished at 2010-11-05 02:17:41.906 GMT and took 0 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-11-05 02:17:41.937 GMT and took 31 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] finished at 2010-11-05 02:17:41.937 GMT and took 125 ms
                < CHANGE > 'deep.com.cn/dc_logo_par' DC
            Analyze versions... finished at 2010-11-05 02:17:41.937 GMT and took 2 s 891 ms
            Analyze activities... started at 2010-11-05 02:17:41.937 GMT
                Loading component definitions
                1 component to be build in compartment "deep.com_PESKM_1"
            Analyze activities... finished at 2010-11-05 02:17:42.000 GMT and took 63 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2010-11-05 02:17:42.109 GMT
                    'deep.com.cn/dc_logo_par' variant 'default'
                    'deep.com.cn/dc_logo_par' variant 'default' cannot be built. ACTIVATION will fail.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2010-11-05 02:17:42.140 GMT and took 31 ms
        ===== Pre-Processing =====  finished at 2010-11-05 02:17:42.187 GMT and took 3 s 187 ms
        Change request state from PROCESSING to FAILED
        Error! The following problem(s) occurred  during request processing:
        Error! The following error occurred during request processing:Activation failed due to component "deep.com.cn/dc_logo_par" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2010-11-05 02:17:42.187 GMT and took 3 s 266 ms
    No build logs available for the request.
    Edited by: yan liang on Nov 5, 2010 3:12 AM

    Hi Yan,
    please check the NWDI troubleshooting guide:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030
    --> Understanding Broken and Dirty DCs
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Did you import the dependent build plugins for the track in question?
    (tab "development" in the /devinf --> CMS webui --> Transport studio)
    See also the sap note: #1080927 - Creating CMS Tracks for Common Application Types (http://service.sap.com/sap/support/notes/1080927)
    Best Regards,
    Ervin

  • Import failed in Con System

    Hello everybody,
    I did some development using the NWDS (JDI installed). After i have checked in my application / activated it and released it it was shown in the import queue at the Consolidation Tab of the CMS application. So far everything worked great, no error what so ever. So i continued to import the application into the Cons system. But it failed. The logs at the detail view says the error occured during the CBS-make step.
    Here is the log:
    Info:Starting Step CBS-make at 2006-03-25 11:29:47.0966 +1:00
    Info:wait until CBS queue of buildspace ABS_ESS_C is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:wait until CBS queue of buildspace ABS_ESS_C is completely processed, before asking for build results
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms (1)
    Info:CBS server log has been written to CBS log
    Fatal:the compartment abs-team.de_ABS_ESS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment abs-team.de_ABS_ESS_1 (dcname=ess/example2 dcvendor=abs-team.de)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-03-25 11:30:18.0778 +1:00
    The CBS server log mentioned above says the following
    Build number assigned: 15596
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "ABS_ESS_C" at Node ID: 7,411,650
         [id: 6,706; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-03-25 10:29:54.169 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         abs-team.de/ess/example2
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-03-25 10:29:54.200 GMT
    Analyse dependencies to predecessor activities... finished at 2006-03-25 10:29:54.200 GMT and took 0 ms
    Analyse activities... started at 2006-03-25 10:29:54.200 GMT
    Analyse activities... finished at 2006-03-25 10:29:54.200 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-03-25 10:29:54.216 GMT
         Synchronize development configuration... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-03-25 10:29:54.216 GMT and took 32 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-03-25 10:29:54.231 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment abs-team.de_ABS_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-03-25 10:29:55.028 GMT and took 797 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-03-25 10:29:55.028 GMT and took 812 ms
    REQUEST PROCESSING finished at 2006-03-25 10:29:55.028 GMT and took 859 ms
    I tried to build the application using the CBS. So i went to the respective cons build space and the DC shows with compile state yellow (middle icon). I clicked on the DC and build it. The buidling process failed, with the following request log:
    Build number assigned: 15696
    Change request state from QUEUED to PROCESSING
    BUILD request in Build Space "ABS_ESS_C" at Node ID: 7,411,650
         [id: 6,747; parentID: 0; type: 2]
    REQUEST PROCESSING started at 2006-03-25 11:04:39.622 GMT
    ===== Pre-Processing =====
    Calculate all combinations of components and variants to be built...
         "abs-team.de/ess/example2" variant "default"
    Prepare build environment in the file system... started at 2006-03-25 11:04:39.872 GMT
         Synchronize development configuration... finished at 2006-03-25 11:04:39.872 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-03-25 11:04:40.294 GMT and took 422 ms
         Synchronize sources...
    Prepare build environment in the file system... finished at 2006-03-25 11:04:40.512 GMT and took 640 ms
    ===== Pre-Processing =====  finished at 2006-03-25 11:04:40.512 GMT and took 890 ms
    Change request state from PROCESSING to FAILED
    ERROR! The following problem(s) occurred  during request processing:
    ERROR! The following error occurred  during request processing:Failed to synchronize D:usrsapER4DVEBMGS00j2eeclusterserver0tempCBS3e.CACHE296DCsabs-team.deessexample2_comp/src/packages
    REQUEST PROCESSING finished at 2006-03-25 11:04:40.512 GMT and took 890 ms
    Anyone has an idea what could be the problem, as this error occurs with every application i developed so far. Everything worked great until i have to import it to the cons system.
    p.s.: importing the standard SAP ESS SCs into the Cons system did work great, just with my very own applications i get this problem
    best regards,
    Markus

    Hello Kiran,
    yes i have made sure that these 3 required SCs are added.
    everything is working from loading the Development Configuration into the NWDS, to checking in the changes, to activate them and to release them. Just when it comes to import them into the CONV Workspace, i get the error.
    When i click on Import at the CMS i get this first error at the default trace (right after i initiated the import, first entry made!)
    SQL statement is 'SELECT 'VSE'.'OBJECTID','VO'.'OBJECTTYPE' 'INTERNALTYP
    E','VSE'.'DEACTIVATED','R'.'RESOURCEID','R'.'RESOURCETYPE'
    ,'R'.'OBJNAME','R'.'PATHURI','R'.'PATHID','R'.'FULLPATHID'
    ,'R'.'DISPLAYNAME','R'.'CREATORNAME','R'.'CREATIONTIME','V
    SE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'.'CONTENTTYPE','R
    '.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','R'.'ISMASTERLANGU
    AGE','R'.'SOURCEURI','V'.'ISDELETED','R'.'DOCUMENTTYPE','R
    '.'FORMATVERSION','R'.'DOCTYPESTATUS','R'.'CONTENTSTOREID'
    ,'R'.'FULLCONTSTOREID','R'.'CONTENTMD5','R'.'TOUCHEDPROPER
    TY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM','CS'.'CONTENTBL
    OB','VSE'.'ACTIVATIONSEQNO' FROM 'PVC_VSETELEMENT' 'VSE'
    INNER JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7
    DESC,9,3'.","Error","/System/Database/sql/jdbc/direct","co
    m.sap.sql.jdbc.direct.DirectPreparedStatement","sap.com/tc
    ~dtr~enterpriseapp","SAPEngine_Application_Thread[impl:3]
    _26","7411650:D:usrsapER4DVEBMGS00
    j2eeclusterserver0
    logdefaultTrace.trc","000C297D05810064000002B90000035C00
    040FE39A4D1378","com.sap.sql.jdbc.direct.DirectPreparedSta
    tement","-2009,I2009,[-2009]: Join columns too
    long,erp04.abs-
    team.de:ER4:SAPER4DB,SELECT 'VSE'.'OBJECTID','VO'.'OBJECTT
    YPE' 'INTERNALTYPE','VSE'.'DEACTIVATED','R'.'RESOURCEID','
    R'.'RESOURCETYPE','R'.'OBJNAME','R'.'PATHURI','R'.'PATHID'
    ,'R'.'FULLPATHID','R'.'DISPLAYNAME','R'.'CREATORNAME','R'.
    'CREATIONTIME','VSE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'
    .'CONTENTTYPE','R'.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','
    R'.'ISMASTERLANGUAGE','R'.'SOURCEURI','V'.'ISDELETED','R'.
    'DOCUMENTTYPE','R'.'FORMATVERSION','R'.'DOCTYPESTATUS','R'
    .'CONTENTSTOREID','R'.'FULLCONTSTOREID','R'.'CONTENTMD5','
    R'.'TOUCHEDPROPERTY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM
    ','CS'.'CONTENTBLOB','VSE'.'ACTIVATIONSEQNO'
    FROM 'PVC_VSETELEMENT' 'VSE' INNER
    JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7 DESC,9,3,","-2009,I2009,[-2009]: Join
    columns too long,erp04.abs-
    team.de:ER4:SAPER4DB,SELECT 'VSE'.'OBJECTID','VO'.'OBJECTT
    YPE' 'INTERNALTYPE','VSE'.'DEACTIVATED','R'.'RESOURCEID','
    R'.'RESOURCETYPE','R'.'OBJNAME','R'.'PATHURI','R'.'PATHID'
    ,'R'.'FULLPATHID','R'.'DISPLAYNAME','R'.'CREATORNAME','R'.
    'CREATIONTIME','VSE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'
    .'CONTENTTYPE','R'.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','
    R'.'ISMASTERLANGUAGE','R'.'SOURCEURI','V'.'ISDELETED','R'.
    'DOCUMENTTYPE','R'.'FORMATVERSION','R'.'DOCTYPESTATUS','R'
    .'CONTENTSTOREID','R'.'FULLCONTSTOREID','R'.'CONTENTMD5','
    R'.'TOUCHEDPROPERTY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM
    ','CS'.'CONTENTBLOB','VSE'.'ACTIVATIONSEQNO'
    FROM 'PVC_VSETELEMENT' 'VSE' INNER
    JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7
    DESC,9,3,","erp04.abs45team.de_ER4_7411650","0e1778e0bcb61
    1daab59000c297d0581","CMS_USER","0","0","com.sap.sql_0003"
    ,"1","/System/Database/sql/jdbc/direct","","461","com.sap.
    sql.jdbc.direct.DirectPreparedStatement","SAPEngine_Applic
    ation_Thread[impl:3]_26","","CMS_USER",
    regards,
    Markus

  • How to Resolve the Broken Dc's on CBS.

    Hello all,
    I am facing few broken Dc's in CBS. I tried to resolve the broken DC's by the following procedures, but was not able to completely resolve the broken DC's on CBS. few procedures are
    1. No built and Deploy errors in NWDI
    2.Had released all the activities from transport, no more activity's are in pending state in TSK.
    But I am facing broken DC's in compile state, Metadata and Used Dc's. Can any of you suggest me how to resolve the broken DC's on CBS.
    Thanks you all,
    Anil

    Hi Anil,
    first of all please notice that I've moved this thread to the NWDI forum.
    See the guide:
    Understanding Broken DCs and Dirty DCs
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    You find some other useful documents in the top-most thread of this page in NWDI forum (SAP NetWeaver Development Infrastructure (NWDI))
    Direct link to the thread:
    Most important NWDI related guides and documents
    The specified item was not found.
    Best Regards,
    Ervin

  • Conflict for a XI track in NWDI on the assembly tab

    Dear friends,
    I have defined a XI track in NWDI/CMS. But on Assembly tab I get a conflict error. The log message is:
    Info:Starting Step Check-assembly at 2008-01-21 17:42:04.0367 +0:00
    Info:Checks for software component A_TEST are performed now:
    Info:Checks for software component A_TEST finished succesfully
    Info:Checks for software component I_FGT are performed now:
    Info:Checks for software component I_HGFfinished succesfully
    Info:Checks for software component HGF are performed now:
    Info:Checks for software component A_HGF finished succesfully
    Info:Checks for software component O2C are performed now:
    Info:7XI conflicts
    Info:Step Check-assembly ended with result 'error' ,stopping execution at 2008-01-21 17:42:07.0394 +0:00
    Can you help where to look and what to do?
    Kind regards,
    Kamran

    Hi
    The following logs exist for the assembly step:
    &#9679;      Check-assembly: Checks whether the prerequisites for a successful assembly exist. The following individual checks are performed:
    &#9675;       Are there open build requests in the buildspace?
    &#9675;       Are there open conflicts in the workspace?
    &#9675;       Are there any broken DCs in the build compartment?
    &#9675;       Are there any “dirty DCs” in the build compartment?
    &#9675;       Are there any problem DCs in the build compartment?
    &#9675;       Are there any pending activities that are not yet completely activated?
    For detailed monitoring of a central build, use the Web UI of the Component Build Service (CBS).
    http://help.sap.com/saphelp_nw04s/helpdata/en/ab/40833c87ac4d0cb5c4c44da8259386/frameset.htm
    If the track deletion in CMS should fail for some reason, CBS administrators can delete a buildspace manually.
           1.      Start the CBS Web UI.
           2.      Navigate to the Buildspaces view.
           3.      Select a buildspace to delete.
           4.      Choose Delete.
    Let me know if this could help you
    thanks
    Swarup

  • Used DC issue

    Hello,
    I have a issue with adding used DCs.
    I have one external library DC...say "extlib"
    This has all the jar files required.
    I have one Portal standalone DC...say "portaldc1"
    This portal dc has java classes in the src.API package. These classes require the jars in extlib.
    I have one web dynpro DC....say "webdc1"
    This webdc1 uses classes in portaldc1 and also require extlib.
    What kind of public parts do I have to create and add as used DCs.
    I also want to make sure that, when I make changes to any classes in "portaldc1", I just build and redeploy "portaldc1"...I do not want to build and redeploy "webdc1" each time I change portaldc1.
    Is this achievable?
    Any help is greatly appreciated.
    Thanks
    MLS

    Hi Laxmi,
    If all the DCs that will access the library also access the "portaldc1", then expose the libraries through "portaldc1". But, how you structure your DC will be upto your requirement and design.
    To your second question, if you build a DC, lets call it DC1, being used by other DCs and check it in. CBS automatically marks all the DCs using DC1 as dirty. This is to ensure that are inconsistency in the source repository and all the dependencies changes do not affect the using DCs. Then based on the settings CBS will build the dirty DCs. In case the dependencies have changed like a used methos is removed or a method signature is changed etc then a DC using this depenency will become Broken.
    Broken DCs are a way of the CBS to inform the users that something is wrong and needs to be fixed.
    Regards,
    Kartikaye

  • Error in JDI Configuration

    Hi All,
    i am getting an error in JDI configuration in the step importing MSS.sca file in CMS transport studio/development.
    error description as follows
    Fatal:the compartment sap.com_SAP_MSS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ecm dcvendor=sap.com)
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec dcvendor=sap.com)
    Info:the compartment sap.com_SAP_MSS_1 contains broken DCs after the CBS build process:
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/budget dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/equ dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ewa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/finutils dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/lpa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mas dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mol dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mov dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pcr dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/per dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pla dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtp dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/cand dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/req dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rpt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/tmv dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=temp/testforisrlpd dcvendor=sap.com)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2007-02-26 04:52:23.0586 +1:00
    please help me.
    thanks in advance.
    Srinivas.

    Hi ...
    Maintain one more characterictic like Zprice and in Addl data give table as SDCOM and field as VKOND and no values, this is characteristics for variant price and include it in the class which u have created earlier.
    goto CT04 and goto values .... there select one value eg RED and then goto object dependency and give code as
    $self.Zprice = 'A1'
    and for all values give it like that..
    Now goto VK11 and give VA00 .....
    then enter varaitn as A1 and give price
    give A2 and give price
    like all variants 'A1' etc etc etc which u maintained in object dependency ....
    now u can create profile in Cu41 and then run sales order
    so what ever u select ...red, blue green etc in order for eg color characterictics .. u have maintained for each value in characteristics .. object dependency .... as $self.Zprice = 'A1', so A1 price maintained in VK11 so if u select Red ... then price from A1 comes ..
    same procedure u follow for all values in other characterictics .. with only one characteristics Zprice ... i.e $self.Zprice = 'B1' etc .. and maintain values for B1 etc in Vk11 in Va00.
    Reward if useful
    Krishna

Maybe you are looking for