Activation fail, broken DCs

Hi, guru:
we have a track call MRP, and Buildspace are:
- MRP_C
- MRP_D
anyone can tell me what is MRP_C for. is that for consolidation? I checked landscape configurator, runtime systems, and consolidation system is not ticked.
we have problem with activation. and I found our DC under (MRP_C) is broken.
We developed in MRP_D, however, MRP_C has broken DC, and I have no idea. is this will cause activation fail?
If I checked the request log, and I found that a lot of invalid independecies.
INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid:
     DC: optus.com.au/optusaugecko of compartment optus.com.au_MAINT_REQ_PROCESSING_1 USES  UNKNOWN DC: sap.com/tc/bi/bp/webDynpro [public-part: webDynpro] AS Build Plugin Dependency
          [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
     DC: optus.com.au/optusaugecko of compartment optus.com.au_MAINT_REQ_PROCESSING_1 USES  UNKNOWN DC: sap.com/tc/cmi [public-part: default] AS Build-Time Dependency
          [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
     DC: optus.com.au/optusaugecko of compartment optus.com.au_MAINT_REQ_PROCESSING_1 USES  UNKNOWN DC: sap.com/tc/ddic/ddicruntime [public-part: default] AS Build-Time Dependency
          [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
     DC: optus.com.au/optusaugecko of compartment optus.com.au_MAINT_REQ_PROCESSING_1 USES  UNKNOWN DC: sap.com/tc/ddic/metamodel/content [public-part: default] AS Build-Time Dependency
So how can I fix it?
Cheers,
Eric

Hi, Guru:
I am reading your comments:
If the DCs were build successfully in *_D development track, it means that the transport of all the required DCs to *_C track was missed, so kindly ask your basis administrator to do the needful.
I checked the landscape configurator, tab "runtime systems", and find consolidation box is not checked.
Shall I check the box and set up a consolidation system? (is it the root cause for the problem you said that transports of all the required DCs to *_C track was missed?)
If so, shall I configure consolidation system same as development system, I mean using same hose, SDM, and port?
Cheers,
Eric

Similar Messages

  • ESS MSS CBS Failed - Broken DCs */cfg

    Hi,
          I am at the last stage of the import process for ESS MSS and its dependent SCs into our NWDI environment. All the imports are successful however, when I check the status of all the DCs under ESS and MSS components I see that all the ones DCs that end with /cfg are BROKEN in the Compilation state.
         There seems to be some issue that is causing all the */cfg DCs to fail. My attempt to 'Build' this compartment proved unsuccessful.
         I guess, my question is..
          What are these */CFG DCs used for and what could be causing this issue?
    Thanks,
    Winston

    Hi Winston
    Please refer to below docs for more details :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0bb614d-2848-2a10-52a7-b5000043b475
    /people/martin.pospischil/blog/2009/07/08/troubleshooting-nwdi
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Regards
    Arun Jaiswal

  • 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

  • Activation Failed

    I have a library project and an External Library project, both which build successfully.  In fact the application that uses these runs successfully on one server.  These projects were built on an NWDI Track and there is an activity for each (Create Library and Create External Library).  Both activities are checked in and available in the activation view. 
    I first tried to activate the External Library as it has no predecessors.  The build was successful but the activation failed.  I thought maybe I needed to activate them at the same time so I tried to activate the Create Library - it has one predecessor (Create External Library) - I selected Activate with all Predecessors.  Still Fails.
    This is what the activation log says:
    REQUEST PROCESSING started at 2009-03-03 14:44:05.770 GMT
        ACTIVATION request in Build Space "JP1_EPPHASE1_D" at Node ID: 3,431,550
         [id: 270; parentID: 0; type: 4]
         [options: FORCE ACTIVATE PREDECESSORS, IGNORE COMPONENT INTERSECTION]
        Waiting for access: 4 ms
        ===== Pre-Processing =====  started at 2009-03-03 14:44:05.774 GMT
            List of requested for activation activities:
                'mc.com_TRACK_1' compartment
                    Edit XML Library
                        [ISN 217][created by M100236 at 2009-03-03 09:43:48.0][OID f2562c82b03211ddc1689ad54e639164]
                There is 1 activity in compartment mc.com_TRACK_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2009-03-03 14:44:05.783 GMT
                Analyzing predecessors in compartment "mc.com_TRACK_1"
                    2 not activated predecessors are detected
                    The following activities are being added to request:
                    "Create XML External Library"   [seq. no 145][created by M100236 at 11/11/08 2:05 PM][ID bdae3201b01311ddac1e9ad54e639164]
                    "Create XML Library"   [seq. no 146][created by M100236 at 11/11/08 3:21 PM][ID 5cedb8ccb02311dd9f7d9ad54e639164]
                    The following DC is to be added to compartment mc.com_TRACK_1:
                    "mc.com/xml_eLib"
            Analyze dependencies to predecessor activities... finished at 2009-03-03 14:44:05.811 GMT and took 28 ms
            Analyze versions... started at 2009-03-03 14:44:05.811 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2009-03-03 14:44:05.914 GMT and took 103 ms
                Resource "/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_eLib.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_eLib.dcref'. URL does not point to DCs root directory.
                Resource "/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_lib.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_lib.dcref'. URL does not point to DCs root directory.
                < IGNORE > 'mc.com/xml_eLib' DC
                Synchronize metadata for [mc.com/xml_elib] started at 2009-03-03 14:44:05.980 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 14:44:05.997 GMT and took 7 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 14:44:06.009 GMT and took 12 ms
                Synchronize metadata for [mc.com/xml_elib] finished at 2009-03-03 14:44:06.009 GMT and took 29 ms
                < CREATE > 'mc.com/xml_elib' DC
                Synchronize metadata for [mc.com/xml_lib] started at 2009-03-03 14:44:06.033 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 14:44:06.047 GMT and took 6 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 14:44:06.059 GMT and took 12 ms
                Synchronize metadata for [mc.com/xml_lib] finished at 2009-03-03 14:44:06.059 GMT and took 26 ms
                < CREATE > 'mc.com/xml_lib' DC
            Analyze versions... finished at 2009-03-03 14:44:06.059 GMT and took 248 ms
            Analyze activities... started at 2009-03-03 14:44:06.059 GMT
                Loading component definitions
                DC Metadata inconsistency detected: Registered DC vendor/name "mc.com/xml_elib" does not correspond to "mc.com/xml_eLib" declared in the DC definition
                Removing component "mc.com/xml_eLib" from request 270. A component with this name has not yet been created or activated.
                2 components to be build in compartment "mc.com_TRACK_1"
            Analyze activities... finished at 2009-03-03 14:44:06.077 GMT and took 18 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2009-03-03 14:44:06.083 GMT
                    'mc.com/xml_elib' variant 'default'
                    'mc.com/xml_lib' variant 'default'
                    'mc.com/xml_lib' variant 'default' cannot be built. ACTIVATION will fail.
                    INVALID dependency is declared
                    DC 'mc.com/xml_lib' in SC 'mc.com_TRACK_1' USES Non-existing DC 'mc.com/xml_eLib' [public-part: XMLAssembly] AS Build-Time Dependency  [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
            Analyze request DC BV... finished at 2009-03-03 14:44:06.118 GMT and took 35 ms
        ===== Pre-Processing =====  finished at 2009-03-03 14:44:06.120 GMT and took 346 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 "mc.com/xml_lib" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2009-03-03 14:44:06.129 GMT and took 359 ms
    So I can understand there is a problem - but the activities are checked in and I cannot modify them so I am unsure how to fix this issue.  I thought maybe create a new activity and just checkin the project from scratch but that isn't an option as these are always seen as predecessors.  I really need to get these activated and released to the next server so any tips are appriciated.

    I did a sync on the Track and am now receiving a different error:
    REQUEST PROCESSING started at 2009-03-03 15:11:59.292 GMT
        ACTIVATION request in Build Space "JP1_EPPHASE1_D" at Node ID: 3,431,550
         [id: 273; parentID: 0; type: 4]
         [options: FORCE ACTIVATE PREDECESSORS, IGNORE COMPONENT INTERSECTION]
        Waiting for access: 16 ms
        ===== Pre-Processing =====  started at 2009-03-03 15:11:59.308 GMT
            List of requested for activation activities:
                'mc.com_TRACK_1' compartment
                    Create XML Library
                        [ISN 146][created by M100236 at 2008-11-11 15:21:14.0][OID 5cedb8ccb02311dd9f7d9ad54e639164]
                There is 1 activity in compartment mc.com_TRACK_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2009-03-03 15:11:59.312 GMT
                Analyzing predecessors in compartment "mc.com_TRACK_1"
                    1 not activated predecessor is  detected
                    The following activities are being added to request:
                    "Create XML External Library"   [seq. no 145][created by M100236 at 11/11/08 2:05 PM][ID bdae3201b01311ddac1e9ad54e639164]
                    The following 2 DCs are to be added to compartment mc.com_TRACK_1:
                    "mc.com/xml_elib"
                    "mc.com/xml_eLib"
            Analyze dependencies to predecessor activities... finished at 2009-03-03 15:11:59.339 GMT and took 27 ms
            Analyze versions... started at 2009-03-03 15:11:59.339 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2009-03-03 15:11:59.436 GMT and took 97 ms
                Resource "/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_eLib.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_eLib.dcref'. URL does not point to DCs root directory.
                Resource "/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_lib.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/mc.com/MC/_comp/TopLevelDCs/mc.com xml_lib.dcref'. URL does not point to DCs root directory.
                < IGNORE > 'mc.com/xml_eLib' DC
                Synchronize metadata for [mc.com/xml_elib] started at 2009-03-03 15:11:59.483 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 15:11:59.497 GMT and took 7 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 15:11:59.516 GMT and took 19 ms
                Synchronize metadata for [mc.com/xml_elib] finished at 2009-03-03 15:11:59.516 GMT and took 33 ms
                < CREATE > 'mc.com/xml_elib' DC
                Synchronize metadata for [mc.com/xml_lib] started at 2009-03-03 15:11:59.541 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 15:11:59.557 GMT and took 9 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 15:11:59.576 GMT and took 19 ms
                Synchronize metadata for [mc.com/xml_lib] finished at 2009-03-03 15:11:59.576 GMT and took 35 ms
                < CREATE > 'mc.com/xml_lib' DC
            Analyze versions... finished at 2009-03-03 15:11:59.576 GMT and took 237 ms
            Analyze activities... started at 2009-03-03 15:11:59.577 GMT
                Loading component definitions
                DC Metadata inconsistency detected: Registered DC vendor/name "mc.com/xml_elib" does not correspond to "mc.com/xml_eLib" declared in the DC definition
                Removing component "mc.com/xml_eLib" from request 273. A component with this name has not yet been created or activated.
                2 components to be build in compartment "mc.com_TRACK_1"
            Analyze activities... finished at 2009-03-03 15:11:59.587 GMT and took 10 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2009-03-03 15:11:59.593 GMT
                    'mc.com/xml_elib' variant 'default'
                    'mc.com/xml_lib' variant 'default'
            Analyze request DC BV... finished at 2009-03-03 15:11:59.643 GMT and took 50 ms
            Prepare build environment in the file system... started at 2009-03-03 15:11:59.643 GMT
                Synchronize development configuration... started at 2009-03-03 15:11:59.644 GMT
                Synchronize development configuration... finished at 2009-03-03 15:11:59.646 GMT and took 2 ms
                Synchronize sources for [mc.com/xml_elib] started at 2009-03-03 15:11:59.649 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 15:11:59.667 GMT and took 8 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 15:11:59.696 GMT and took 29 ms
                Synchronize sources for [mc.com/xml_elib] finished at 2009-03-03 15:11:59.696 GMT and took 47 ms
                Synchronize sources for [mc.com/xml_lib] started at 2009-03-03 15:11:59.722 GMT
                    Verification of DL [ws/EPPHASE1/mc.com_MC/dev/active/] finished at 2009-03-03 15:11:59.737 GMT and took 7 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2009-03-03 15:11:59.777 GMT and took 40 ms
                Synchronize sources for [mc.com/xml_lib] finished at 2009-03-03 15:11:59.778 GMT and took 56 ms
                Synchronize used libraries... started at 2009-03-03 15:11:59.793 GMT
                Synchronize used libraries... finished at 2009-03-03 15:12:00.665 GMT and took 872 ms
            Prepare build environment in the file system... finished at 2009-03-03 15:12:00.665 GMT and took 1 s 22 ms
        ===== Pre-Processing =====  finished at 2009-03-03 15:12:00.665 GMT and took 1 s 357 ms
        Waiting for access: 3 ms
        ===== Processing =====  started at 2009-03-03 15:12:00.669 GMT
            BUILD DCs
                'mc.com/xml_elib' in variant 'default'
                        'XML_Assembly' PP has been changed. Dependent DCs will be re-built.
                        'XML_Component' PP has been changed. Dependent DCs will be re-built.
                    The build was SUCCESSFUL. Archives have been created.
                'mc.com/xml_lib' in variant 'default'
                        'defLib' PP has been changed. Dependent DCs will be re-built.
                    The build was SUCCESSFUL. Archives have been created.
        ===== Processing =====  finished at 2009-03-03 15:12:11.953 GMT and took 11 s 284 ms
        ===== Post-Processing =====
        Waiting for access: 7 ms
        ===== Post-Processing =====  started at 2009-03-03 15:12:11.960 GMT
            Check whether build was successful for all required variants...
                "mc.com/xml_elib" in variant "default"   OK
                "mc.com/xml_lib" in variant "default"   OK
            STORE activation build results... started at 2009-03-03 15:12:11.961 GMT
                Update DC metadata... started at 2009-03-03 15:12:11.961 GMT
                    'mc.com/xml_elib' DC is CREATED
                    'mc.com/xml_lib' DC is CREATED
                Update DC metadata... finished at 2009-03-03 15:12:12.040 GMT and took 79 ms
                STORE build results... started at 2009-03-03 15:12:12.040 GMT
                ===== Post-Processing =====  finished at 2009-03-03 15:12:12.041 GMT and took 81 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:I/O error:Failed to persist the assembly
    Assembly: [binary ID: [B@35193519]
         [bsID: 27, scID: 101, dcID: 304, bvID: 101, ppName: "XML_Assembly"archive type: "PP Archive", build number: 259]
         temporary location in: /usr/sap/JP1/DVEBMGS00/j2ee/cluster/server0/temp/CBS/1b/.B/259/DCs/mc.com/xml_elib/tmp of the PPBV
    Build Variant "default" of Compartment "mc.com_TRACK_1"
         [bvID: 101, scID: 101, required for activation: true] OF Build variant default of
    Development Component
         "mc.com/xml_elib" in compartment "mc.com_TRACK_1" attached to request 273
         [scID: 101, dcID: 304, parent dcID: 0, current state: OK, action: CREATED]
         Build Number: (last successful: 259, last known 259)
         Original Cause: PPA not found! Expected location:
    /usr/sap/JP1/DVEBMGS00/j2ee/cluster/server0/temp/CBS/1b/.B/259/DCs/mc.com/xml_elib/_comp/gen/default/public/XML_Assembly.ppa
            REQUEST PROCESSING finished at 2009-03-03 15:12:12.084 GMT and took 12 s 792 ms

  • Help: NWDI 7.2 CBS build problem - initialize compartment-broken DCs

    Hi all.
    I am facing a problem with CBS build due to broken DCs - invalid dependencies. I have read all the articles and notse related to this issue, but cannot not solve is. Has anyone faced this issue or know a solution?
    The problem:
    In one SC I have a DC A, which used to have public part PP_A.
    In another SC I have a DC B, which used to depend on public part PP_A of DC A.
    As part of implementation, the PP_A in DC A was deleted and replaced by new public parts. The changes are checked in and activated in NWDI successfully.
    Next, the DC B was corrected, its reference to PP_A was deleted and replaced with appropriate replacements.
    I checked in the activity correcting the DC B. Activation fails, because CBS complains that DC B has invalid dependency. I assume that the CBS cache still holds the old sources.
    I took the compartment where DC B is located and triggered a CBS Reinitialize compartment (which should discard the cached sources and load a fresh copy). The CBS Reinitialize compartment request fails too! The log shows the same message as the build log: invalid dependency.
    It seems that during reinitialize, CBS checks the validity of the DCs in the compartment BEFORE it does clean its cache and refreshes from DTR.
    In DTR, I can see the sources of DC A and DC B checked in correctly in the inactive branch, the .dcdef in DC B contains correct references to new public parts of DC A.
    Does anyone know how to force CBS to refresh its sources from DTR where correct sources are checked in?
    Thanks.
    Edited by: Rastislav Cesnek on Dec 20, 2011 3:25 PM

    Right.
    Its not the CONS, it's the active from DEV which is used. I sort of don't understand the NWDI concept then, maybe SAP could learn a little from Hudson, CruiseControl you name it.
    Apparently, as I found out after some trial and error, the checks done before the build AND before the initialize compartment run on sources from ACTIVE branch. So the check-ed in fixed sources of the DC B are ignored by CBS. It then complains about the invalid dependencies all the time.
    Finally, although it looks very scary, I activated the soure code changes of the dependent components (I hade a lot of them, not just one) with the "Activate even if the build fails". Then the initialize compartment did not complain about BROKEN components because of dependencies, because the check of metadata succeeded and the components were rebuilt.
    Thanks for hints.

  • All my activation failed !

    Hi,
    I have creted a track with all dependencies and everything is ok.
    In my NWDS, I created a DC and checked in my activity. All was ok. But for the activation process, it failed. I tried plenty of stuff (create a new DC, ...), and all activations still was failed.
    In the CBS request log : "No request log available.".
    In the Build log : "No build log available. The DC has not been built in this request."
    Build status : RED
    I decided to force the activation even if build failed and it was worst, Now I got a Broken DC. I went to the following link : <a href="http://help.sap.com/saphelp_nw70/helpdata/en/0b/eb18ff7c7ed647ae51cfcc5d69e5d9/frameset.htm">Fixing Broken Development Components</a> But no real information was there only this sentence : <i>If there are DCs broken by itself find out why these DCs are broken and fix them.</i> but How to fix it ??
    Thanks for your interrest
    Kind regards

    Hi,
    Firstly you should not go for force activation as it leads to broken DCs. ie... Force activation means the DC will get activated even if the build fails and that leads to broken DCs.
    Usually I go for force activation incases where I do not need the DCs ie...sometimes when I delete DCs my activation would fail and I would go for force activation as I do not need that DC any more. 
    Force activation will also lead to the integration of broken DCs  in DTR.
    You might get some hint in the request log. Kindly check the request log and post more details.
    Akshatha

  • ESS 177 broken DCs, MSS 20 broken DCs

    Hi,
    We have done many times of activation, build, released and transportation for ESS customozation.
    After Activation failed: CBS Server Error is solved, we encountered the broken DCs problem in the CBS.
    ESS  :                              Total DCs=177 ,                          Broken DCs=177
    MSS   :                             Total DCs=20  ,                           Broken DCs=20
    SAP-JEE :                         Total DCs=0   ,                           Broken DCs=0
    SAPPCUI_GP :                  Total DCs=0   ,                           Broken DCs=0
    SAP_BUILDT   :                  Total DCs=0   ,                           Broken DCs=0
    SAP_JTECHS  :                   Total DCs=0  ,                           Broken DCs=0
    When i viewed the Build Log of each DC, the error is as below:
    USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED / USED BUILD PLUGIN IS UNKNOWN OR UNDEFINED.
    1. It seems that SAP-JEE, SAPPCUI_GP, SAP_BUILDT and SAP_JTECHS has 0 Total DCs. Is it normal or something wrong?
    2. How do i solve this problem?
    Any help would be much appreciated. Thanks.
    - julius

    1. This is wrong.
    2. Re-import them into your track, starting from the Development stage.

  • Activation of the activity fails u0096 no source files in the active workspace

    Dear All,
    I’m working on a NWDI installation since last month. The NWDI server (NW2004s) has been installed and configured with the following parameters:
    Some Details:
    -     Java Stack on SPS 12
    -     No complete Developer Workplace, we only use the Studio (SPS 12)
    -     OS: WIN 2003
    -     DB: Oracle 10g
    -     SDK: 2 SDK, Standard Edition x64 1.4.2_15
    Installation Usages Types: DI, AS Java, EP Core, EP (EP for the Visual Composer)
    Performed configuration steps:
    -     adaptation of VM parameter in the Visual Admin
    -     patched the NWDI Server and the Studio from SPS 9 to support package stack 12 + available single patches
    -     run the template installer => NWA with type “DI Allinone – run all post installation Steps for DI, CBS, CMS, DTR”
    -     Oracle Parameters changed, User and Authorizations created and assigned (UME, J2EE Security roles, DTR => ACL List), SLD (Creation of a new Landscape), Configuration of the CBS with the VA
    -     Configuration of the Studio (SAP J2EE Engine (fill in the NWDI engine), Proxy Settings, Development Configuration Pool)
    Development Steps for an example:
    -     Creation of a new software product (SLD)
    -     Namespace reservation on SLD => Application Context Root, Development Component Name
    -     Created a Domain and a Track on CMS
    -     Attached all Software components to the track (my own dc, SAP-JEE, SAP_Buildt, SAP_JTechs)
    -     Check-In the Software Components on Transport studio => CMS
    -     Moved the development configuration into Studio
    -     Created a ear- and a web-project => Display a JSP File (It’s the same example like in the SAP Course TADM10)
    -     Check-in the activity under “Open activities” => Activate
    My problem appears during the check-in phase in the studio. I was able to check-In the source files in to the inactive Workspace on the DTR, but the activation of the activity fails. (I thought that the build process runs automatically after the activation - also the movement from the source files from the inactive to the active workspace?).
    I received no error message, but I can’t find any source files in active workspace. The activity seems to be pending. I locate the request in the CBS, the request state is “failed” regarding the request type “activate”.
    At the moment there is no separate runtime system assigned to the NWDI System.
    Questions:
    1.     Have I forgotten an important configuration step?
    2.     Can I use the NWDI Server also as a runtime environment (DEV System)?
    Please let me know if somebody has an idea.
    Thanks.
    Christoph

    Hello Michael,
    thanks a lot for your answer.
    I found the following error messages in the <b>request log</b>:
    <i>Calculate all combinations of components and variants to be built...
         "xxxtest.com/math/calc/webdc01" variant "default"
              "xxxtest.com/math/calc/webdc01" variant "default" cannot be built. Activation will fail.
              INVALID dependency is declared to public part: default.
              [DC 247 variant "default"][SC 65 "xxxtest.com_TASCHENRECHNER_1"] using [PP default of DC 6 at Build-Time Dependency]
         "xxxtest.com/math/calc/eardc03" variant "default"
              "xxxtest.com/math/calc/eardc03" variant "default" cannot be built. Activation will fail.
              The required Build Plugin "sap.com/tc/bi/bp/enterpriseApplication/enterpriseApplication" IS UNKNOWN. None of the compatments contains a suitable plugin for this component.
              [DC 248 variant "default"][SC 65 "sanofitest.com_TASCHENRECHNER_1"] using [BP sap.com/tc/bi/bp/enterpriseApplication/enterpriseApplication]
    Prepare build environment in the file system... started at 2007-09-04 06:13:54.316 GMT
    Prepare build environment in the file system... finished at 2007-09-04 06:13:54.316 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2007-09-04 06:13:54.332 GMT and took 406 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 "xxxtest.com/math/calc/webdc01" variant "default". The component is BROKEN.
    ERROR! The following error occurred during request processing:Activation failed due to component "xxxtest.com/math/calc/eardc03" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2007-09-04 06:13:54.332 GMT and took 422 ms</i>
    The <b>Build Log</b> was empty.
    Thank you in advance.
    Best regards
    Christoph

  • Activation failed due to sructure generation error.-URGENT

    i tried to check in an activity but activation failed due to the foloowing error:PLEASE HELP VERY URGENT
    Development Component Build (2008-03-14 10:09:20)
      Component name: tablist
      Component vendor: worldbank.org
      SC compartment: worldbank.org_GDB_OPERATIONS_1
      Configuration: WAS_MIGATEST_D
      Location: WAS_MIGATEST_D
      Source code location: http://sapjdi01:50000/dtr/ws/MIGATEST/worldbank.org_GDB_OPERATIONS/dev/active/DCs/worldbank.org/tablist/_comp/
      DC root folder: /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/tablist/_comp/
      DC type: Web Dynpro
      Host: sapjdi01
    DC Model check:
              [dcmake] All used DCs are available locally
              [dcmake] validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/cmi"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/ddic/ddicruntime"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/ddic/metamodel/content"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/wd/webdynpro"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/logging"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/tc/wdp/metamodel/content"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/com.sap.aii.util.misc"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/com.sap.exception"
              [dcmake] validating dependency to  public part "default" of DC "sap.com/com.sap.mw.jco"
              [dcmake] validating dependency to  public part "pp_connserv" of DC "worldbank.org/connserv"
              [dcmake] DC model check OK
    Start build plugin:
              [dcmake] using build plugin: sap.com/tc/bi/bp/webDynpro
              [dcmake] starting build plugin from : /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/bi/bp/webDynpro/_comp/gen/default/public/webDynpro/
    Build Plugin 'WebDynproPlugin', Version 6.40 SP 19 (630_VAL_REL, built on 2006-10-27 02:01:51 CEST)
       development component:  tablist (worldbank.org)
          software component:  GDB_OPERATIONS (worldbank.org)
                    location:  WAS_MIGATEST_D
                        type:  Web Dynpro
               build variant:  default
             source location:  http://sapjdi01:50000/dtr/ws/MIGATEST/worldbank.org_GDB_OPERATIONS/dev/active/
           plugin start time:  2008-03-14 10:09:21 GMT+00:00
                     Java VM:  Classic VM, 1.4.2 (IBM Corporation)
    General options:
      convert *.xlf to *.properties: yes
      include sources for debugging: yes
    Source folder META-INF exists but is empty.
    Source folder src/configuration exists but is empty.
    Plugin initialized in 1.026 seconds
    Warning: Runtime dependency to connserv (worldbank.org) not allowed (incompatible runtime type).
    Preparing data context..
    No 'default' JDK defined, will use running VM.
    Data context prepared in 0.128 seconds
    Executing macro file..
      Using macro file:     /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/bi/bp/webDynpro/_comp/gen/default/public/webDynpro/macros/build.vm
      Creating output file: /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/tablist/_comp/gen/default/logs/build.xml
    Macro file executed in 3 seconds
    Starting Ant..
      Using build file:     /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/tablist/_comp/gen/default/logs/build.xml
      Using build target:   build
      Generation folder:    /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/t/013EC0ABDECC3015F13C417F5CBF217B
      Using Ant version:    1.5.4
    prepare:
         [mkdir] Created dir: /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/tablist/_comp/gen/default/deploy
    compile:
         [ddgen]
         [ddgen] [Info]    Property deployment is true: Deployment information is provided!
         [ddgen] [Info]    Property sourcepath: /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/tablist/_comp/src/packages
         [ddgen] [Info]    Property targetpath: /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/t/013EC0ABDECC3015F13C417F5CBF217B/gdd
         [ddgen] [Info]    Property archivename: worldbank.org~tablist
         [ddgen] [Info]    Property vendor: worldbank.org
         [ddgen] [Info]    Property dcname: tablist
         [ddgen] [Info]    Property language: Available languages are automatically determined!
         [ddgen] [Info]    Property addpaths ...
         [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/bi/extmm/_comp/gen/default/public/def/lib/model
         [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/bi/extmm/_comp/gen/default/public/def/lib/model
         [ddgen] [Info]       worldbank.orgconnservpp_connserv.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/worldbank.org/connserv/_comp/gen/default/public/pp_connserv/lib/java
         [ddgen] [Info]       exception.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       SapDictionaryTypeServices.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       SapDictionaryTypesRuntime.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       jrfc.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       aii_proxy_rt.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       cmiapi.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproadmin.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynprobasesrvc.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproclientserver.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynpromodelimpl.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynpromodel_dynamicrfc.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynpropdfobject.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproprogmodel.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproruntime_designtime_coupling.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproruntime_designtime_coupling_api.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproruntime_repository.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproruntime_repository_pmr.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       webdynproservices.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       aii_util_misc.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       logging.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       logging.perf.jar - /usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/WAS/DVEBMGS00/j2ee/cluster/server0/temp/CBS/199/.B/48895/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Origin.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/PackagePointer.java
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Inves_Id.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Ccy_Code.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Subm_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Uw_Upi.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Guar_Holder.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Conver_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Doc_Num.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Sic_Cde.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Rcvr_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Notif_Sndr.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Notif_Rcvr.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Modified_By.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Symsgid.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Status_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapi_Msg.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Inves_Ty.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Reason_Dt.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Stl_Upi.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Balmnr.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Notif_Id.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapi_Line.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Frcast_Chk.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Migeo_Upi.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Waiv_Flag.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Item_Num.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Symsgno.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Status_Categ.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Mngmt_Gr.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Reg_Num.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Stat_Chng_Dt.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Migaorg_Code.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Rcvr_Grp.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Commnt_Eventtype.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapi_Param.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Doc_Typ.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Stl_Comment.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Src_Upi.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Notif_Eventtype.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapi_Mtype.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Sndr_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapi_Fld.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Commnt_Doctype.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Cmmt_User.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Symsgv.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Sme_Share.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Description.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Balognr.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/Bapilogsys.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Amount.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Status.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Reason_Type.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Comment_Id.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Time_Stamp.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Reason.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__Miga_Source.gsimpletype
         [ddgen] [Info]    Generating datatypes/org/wb/operations/stl/types/__Miga__S_Doc_Typ.gstructure
         [ddgen] [Error]   Structure org.wb.operations.stl.types.__Miga__Appl is not generated
         [ddgen] [Error]   BuiltIn Type or Simple Type expected
         [ddgen] [Info]    Catching throwable null
         [ddgen] [Info]    com.sap.dictionary.generation.ant.GenerationAntTaskError
         [ddgen]      at com.sap.dictionary.generation.ant.GenerationAnt.showCheckResult(GenerationAnt.java:171)
         [ddgen]      at com.sap.dictionary.tools.generation.Generation.generatePersistentStructure(Generation.java:480)
         [ddgen]      at com.sap.dictionary.tools.generation.console.GenerationConsole.generate(GenerationConsole.java:168)
         [ddgen]      at com.sap.dictionary.generation.ant.GenerationAnt.main(GenerationAnt.java:47)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
         [ddgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         [ddgen]      at java.lang.reflect.Method.invoke(Method.java:391)
         [ddgen]      at com.sap.dictionary.generation.ant.DDGenAntTask.execute(DDGenAntTask.java:219)
         [ddgen]      at org.apache.tools.ant.Task.perform(Task.java:341)
         [ddgen]      at org.apache.tools.ant.Target.execute(Target.java:309)
         [ddgen]      at org.apache.tools.ant.Target.performTasks(Target.java:336)
         [ddgen]      at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
         [ddgen]      at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:115)
         [ddgen]      at com.sap.tc.buildplugin.AbstractAntBuildAction.execute(AbstractAntBuildAction.java:65)
         [ddgen]      at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:226)
         [ddgen]      at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:202)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
         [ddgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
         [ddgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         [ddgen]      at java.lang.reflect.Method.invoke(Method.java:391)
         [ddgen]      at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
         [ddgen]      at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
         [ddgen]      at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
         [ddgen]      at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
         [ddgen]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1726)
         [ddgen]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1498)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
         [ddgen]      at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
         [ddgen] ERROR: Unknown exception during generation null (com.sap.dictionary.generation.ant.GenerationAntTaskError)
         [ddgen] ERROR: Generation failed due to errors (3 seconds)
    Ant runtime 5.593 seconds
    Ant build finished with ERRORS
    [Error]   Generation failed!
    Error: Build stopped due to an error: [Error]   Generation failed!
    Build plugin finished at 2008-03-14 10:09:32 GMT+00:00
    Total build plugin runtime: 10.143 seconds
    Build finished with ERROR

    I think the "," that comes in the flat file. CHange the number fields in the file from ",". If it has 1000 separator remove them. You need not have them in the file. In your case i think the decimals are coming as ",". In that case change your user settings for decimal places and then try to load.
    Hope this helps

  • Activation failed + USR_MISSING_PRIVILEGE

    Hi Folks,
    We had some DCs working fine on our track. We made changes in one DC(by following checkout and checkin correctly).
    When we tried to activate this activity, we got activation failed message. We checked the associated activation log. There we found that error was on one import statement.
    In the meantime, one more team member created his activity on same DC and checked in(but not activate). We created one more activity in which we commented this line. When we tried to activate it, it gave us error message "CBS ERROR:The user does not have authorization for the requested operation", because now it was considering the predecessor activities too.
    Basically, there are several activities currently which are not getting activated. (some bcoz of code error on above mentioned import statement, some bcoz of USR_MISSING_PRIVILEGE error).
    We found that assigning nwdi admin role can solve atleast usr_missing_privilege so that we can activate all the predecessor activities. But, our clients are not ready to assign that role to us.
    So, is there any other way around?
    Thanks.

    Hi
    in order to activate activities of other developers you need the CBS role XDeveloper. Details can be found in the documentation: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/da/f812d366aa44ad83a30418b34dae1c/frameset.htm. For 7.1x suitable groups are created by the NWDI setup automatically (NWDI.XDevelopers), but for older releases you have to assign the roles manually.
    Regards
    Michael

  • ESS enhancement build caused broken DCs

    Hi,
    I'm doing ESSxx_D on <b>leave</b> enhancement and encountered the broken DCs after consolidation process.
    Actually, i had tried the consolidation for 2 times, but none was successful.
    In the first time, there were all 177 broken DCs for ESS_C and 1 broken DC for ESS_D after consolidation.
    The broken DC happened to other DC (ess/tra/tri in ESS_D) which i didnt touch at all (only enhanced on ess/lea in ESS_D).
    1. How could the broken DCs happened to ESS_C (which is supposed to be constant version) and ESS_D (which is not the one that i did enhancement at)?
    Then, i created a new track and redo everything again. I just copied and pasted the source codes.
    After checked-in, activated and released, the enhanced ESSxx_D deployed successfully to the development server. Everything is fine till this point.
    Next, ESSxx_D was imported in the consolidation. After imported, there is ONE broken DC in the <b>ESSxx_C's ess/lea DC</b>. Error message is as below.
    2. Isnt the <b>ESSxx_C</b> the constant version of the ESS and the enhancement will not affecting it? The ESSxx_D has no broken DC.
    3. The source codes were same for the first time and second time consolidation. What could be gone wrong?
    Any help would be much appreciated. Thanks.
    [ddgen] [Info]    Generating datatypes/com/sap/xss/hr/lea/form/adaptivemodel/types/Infty.gsimpletype
    [System.err] [Invoked from  com.sap.ide.metamodel.general.exception.LoadException.printStackTrace(LoadException.java(Compiled Code))]
    [System.err] LoadException: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 32, 30, 30(file:/usr/sap/EPD/JC00/j2ee/cluster/server0/temp/CBS/25/.B/191246/DCs/sap.com/ess/lea/_comp/src/packages/com/sap/xss/hr/lea/reqlist/adaptivemodel/types/P22J_Nabik.dtsimpletype.xlf, row:3, col:3)
    [System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
    - julius
    null

    Hi Marc/anyone,
    a) Below are my SPs, are these in the compatible version?
    1. NWDI = SP19
    2. NWDS = SP19
    <b>3. ESS track = SP14
    4. MSS track = SP14</b>
    5. WAS = SP19
    6. JEE = SP19
    7. BUILDT = SP19
    8. JTECH = SP19
    <b>9. PCUIGP = SP14</b>
    b) Below are the source codes structures for the ESS. Are all these necessary to synchronised to the DTR? Which are not?
    1. /bin
    2. /def
    3. /gen (i know this one no need to syn)
    4. /gen_dic
    5. /gen_wdp
    6. /META
    7. /Model Folder
    8. /Src
    9. ClassPath
    10. DCDEF
    11. METAMODEL
    12. PROJECT
    - julius

  • ESS MSS - Multiple Broken DCs in CBS

    Hello All,
    We are working on Netweaver Portal 2004s SP15.
    We have deployed ess, mss and pcui_gp patches of SP12.
    We have also installed the NWDI.
    We have created new track, and added ess,mss and pcui_gp software
    components to it. We have checked in and imported following components:
    sap.com_EP_BUILDT 7.00 15
    sap.com_SAP-JEE 7.00 15
    sap.com_SAP_BUILDT 7.00 15
    sap.com_SAP_ESS 600 12
    sap.com_SAP_JTECHS 7.00 15
    sap.com_SAP_MSS 600 12
    sap.com_SAPPCUI_GP 600 12
    But when we observed in CBS, there are many Broken DCs like
    pcui_gp/xssutils, pcui_gp/xsscfg, ess/no/pdata, ess/no/bank, etc.
    Because of this we are unable to build the projects in NWDS
    successfully. NWDS log says:
    General options:
      convert *.xlf to *.properties: yes
      include sources for debugging: yes
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils
    Warning: Source folder "META-INF" does not exist and will be ignored.
    Checking path lengths for sources
    Path length checks finished in 0.09 seconds
    Ant runtime 7.2 seconds
    Ant build finished with ERRORS
    [Error]   Generation failed!
    Error: Build stopped due to an error: [Error]   Generation failed!
    Build plugin finished at 2008-06-26 14:29:36 GMT05:30 (IST)+
    Total build plugin runtime: 10.265 seconds
    Build finished with ERROR
    Please help us solve this problem as soon as possible.
    Regards,
    Vinod

    Hi Alexander
    Thanks for the reply.
    We have imported the required SCAs into new track. That workd fine and these are visible in NWDS.
    The problem is with our custom made SC which contains some DCs built on java1.4. When we import this SCA, it is shown as broken in CBS. that is also fine because the CE7.1 runs on java1.5. (There may be some build errors)
    The problem is we are not able to see these broken DCs in to NWDS.
    Regards
    Arvind

  • Multiple Broken DCs - ESS MSS

    Hello All,
    We are working on Netweaver Portal 2004s SP15.
    We have deployed ess, mss and pcui_gp patches of SP12.
    We have also installed the NWDI.
    We have created new track, and added ess,mss and pcui_gp software
    components to it. We have checked in and imported following components:
    sap.com_EP_BUILDT 7.00 15
    sap.com_SAP-JEE 7.00 15
    sap.com_SAP_BUILDT 7.00 15
    sap.com_SAP_ESS 600 12
    sap.com_SAP_JTECHS 7.00 15
    sap.com_SAP_MSS 600 12
    sap.com_SAPPCUI_GP 600 12
    But when we observed in CBS, there are many Broken DCs like
    pcui_gp/xssutils, pcui_gp/xsscfg, ess/no/pdata, ess/no/bank, etc.
    Because of this we are unable to build the projects in NWDS
    successfully. NWDS log says:
    General options:
    convert *.xlf to *.properties: yes
    include sources for debugging: yes
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils
    Warning: Source folder "META-INF" does not exist and will be ignored.
    Checking path lengths for sources
    Path length checks finished in 0.09 seconds
    Ant runtime 7.2 seconds
    Ant build finished with ERRORS
    Error Generation failed!
    Error: Build stopped due to an error: Error Generation failed!
    Build plugin finished at 2008-06-26 14:29:36 GMT05:30 (IST)+
    Total build plugin runtime: 10.265 seconds
    Build finished with ERROR
    Please help us solve this problem as soon as possible.
    Regards,
    Vinod

    Hello Daniel,
    Thanks for the reply.
    Till now, I am not able to build the project succssfully. So still, I have not modified anything.
    Regarding, And as a little hint if you're on SP15 (NW), corresponding XSS package is 13!
    Is it necessary to have SP13 ?
    Regards,
    Vinod

  • Broken DCs

    I am running WAS640 SP11.  I am using development scenario 2+.  I have two buildspaces WAS_APPL_C & WAS_APPL_D.  In WAS_APPL_C, I have 5 broken DCs for example.org.  In WAS_APPL_D I have none. The same DCs for appl/tax etc. are green in WAS_APPL_D.  Can I just delete the broken DCs attached to WAS_APPL_C and how?  I get errors when trying to assemble the application.
    How would I go about recollecting all the objects, checking them in and adding them to a new activity for later transport.
    I am stuck!

    Hi Steve,
    You can try a few things to get the build to work in the cons buildspace. The simplest is to use CBS to try and fix the problem.
    First, launch CBS for the track, select the cons buildspace, go to Compartments and then select the Build the Compartment tab. At the bottom of the screen, you should see an Initialize the Compartment button. Select that and CBS should synch up with what is in DTR and build the compartment. You can check your results in the Development Components link to see if the compile state is green.
    If everything looks OK from CBS, go back to CMS and assemble the components.
    If that doesn't work, try looking for pending activities in the cons buildspace and activating them.
    -r

  • Broken Dcs in MSS

    Hi all,
    I see around 27 broken Dcs in MSS. The import is successful but the CNS build space shows 27 broken DCs.
    Would it be an issue. Becuase one of the DC cats approval is a DC that I intend to modify.
    Appreciate any inputs.
    regards
    Sam

    Hi,
    I assume you did perform a "restore system state"?
    Otherwise, the "insonsistent" should indicate that SC dependencies were changed somehow after your SLD update. If everything is broken now I'd suspect that something went wrong there and CBS now fails to build anything because of missing dependencies and would check some of the XML fragments in the CMS Landscape configurator.
    For MSS this should define these five dependencies:
    <dependencies>
    <used-compartment>sap.com_SAP_JTECHS_1</used-compartment>
    <used-compartment>sap.com_SAP-JEE_1</used-compartment>
    <used-compartment>sap.com_SAP_BUILDT_1</used-compartment>
    <used-compartment>sap.com_SAPPCUI_GP_1</used-compartment>
    <used-compartment>sap.com_EP_BUILDT_1</used-compartment>
    </dependencies>
    If that's not there then there was something wrong with the SLD import or the imported data, but I'm not an expert for that.
    Regards,
    Marc

Maybe you are looking for