.dcref" is not relevant for DC build and will be ignored

[govardan_raj]

Hi experts ,

On activating an activity im getting the below error please suggest a soluction

Build number assigned: 139
Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2014-10-27 06:05:12.164 GMT
    ACTIVATION request in Build Space "EPD_WDJADEV_D" at Node ID: 9,271,950
[id: 143; parentID: 0; type: 4]
[options: NO OPTIONS]

    Waiting for access: 145 ms
   
    ===== Pre-Processing =====  started at 2014-10-27 06:05:12.310 GMT
        List of requested for activation activities:
            ''****.com_MYCOMPONENTS_1'' compartment
                ****util__21.10.2014
                    [ISN 29][created by TP00010174 at 2014-10-21 15:01:54.0][OID 3ae8efe458e211e4c4910000008d7a8f]
            There is 1 activity in compartment ****.com_MYCOMPONENTS_1
            1 activity will be processed by this request
       
        Analyze dependencies to predecessor activities... started at 2014-10-27 06:05:12.491 GMT
            Analyzing predecessors in compartment "****.com_MYCOMPONENTS_1"
                No dependencies to predecessor activities found.
        Analyze dependencies to predecessor activities... finished at 2014-10-27 06:05:12.560 GMT and took 69 ms
       
        Analyze versions... started at 2014-10-27 06:05:12.561 GMT
            List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2014-10-27 06:05:12.633 GMT and took 28 ms
            Resource "/SCs/****.com/MYCOMPONENTS/_comp/TopLevelDCs/**** prt_dev ****util.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/****.com/MYCOMPONENTS/_comp/TopLevelDCs/**** prt_dev ****util.dcref'. URL does not point to DCs root directory.
           
            Synchronize metadata for [****/prt_dev/****util] started at 2014-10-27 06:05:12.763 GMT
                Verification of DL [ws/WDJADEV/****.com_MYCOMPONENTS/dev/active/] finished at 2014-10-27 06:05:13.676 GMT and took 313 ms
                Verification of cache (level 2: Comparison of attributes) finished at 2014-10-27 06:05:13.894 GMT and took 218 ms
            Synchronize metadata for [****/prt_dev/****util] finished at 2014-10-27 06:05:14.008 GMT and took 1 s 245 ms
            < CREATE > ''****/prt_dev/****util'' DC
        Analyze versions... finished at 2014-10-27 06:05:14.018 GMT and took 1 s 457 ms
       
        Analyze activities... started at 2014-10-27 06:05:14.018 GMT
            Loading component definitions
            1 component to be build in compartment "****.com_MYCOMPONENTS_1"
        Analyze activities... finished at 2014-10-27 06:05:15.447 GMT and took 1 s 429 ms
        Calculate all combinations of components and variants to be built...
       
        Analyze request DC BV... started at 2014-10-27 06:05:15.496 GMT
                ''****/prt_dev/****util'' variant ''default''
                ''****/prt_dev/****util'' variant ''default'' cannot be built. ACTIVATION will fail.
                INVALID dependency is declared
                DC '****/prt_dev/****util' in SC '****.com_MYCOMPONENTS_1' USES Non-existing DC '****/prt_dev/****msjar' [public-part: ?] AS Deploy-Time Dependency  [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
        Analyze request DC BV... finished at 2014-10-27 06:05:15.627 GMT and took 131 ms
    ===== Pre-Processing =====  finished at 2014-10-27 06:05:15.637 GMT and took 3 s 327 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 "****/prt_dev/****util" variant "default". The component is BROKEN.
REQUEST PROCESSING finished at 2014-10-27 06:05:15.639 GMT and took 3 s 475 ms

No build logs available for the request

Regards

Govardan Raj S

[junwu]

maybe you have to talk a little about how you move the code to nwdi from local,

[former_member310779]

Hi Govardan,

Is this the first time you are activating the activity in the WD dc? if not then from the activities, remove the .dcref (revert the dcref alone) file and activate the activity.As the .dcref only hold the meta data, and i presume you must not have changed to the DC(like dependent jar's) itself from the previous code change.

Regards,

iqbal

[ErvinSzolke]

Hi,

dcref is a 0 byte file in DTR (in SCs --> TopLevelDCs) that is only required for NWDS to recognize this DC exists. If you remove it then NWDS won't display that DC as if it did not even exist in the first place.

I think the problem is rather simply about broken DCs.

"Error! The following error occurred during request processing: Activation failed due to component "****/prt_dev/****util" variant "default". The component is BROKEN."

If you see this one in the trace:

"[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]"

Then it is usually about missing SC dependency imports.

Review this guide:

(NWDI)(CBS) the CBS-make log and-or CBS Web UI report broken DCs - Technology Troubleshooting Guide ...

Regards,

Ervin