cancel
Showing results for 
Search instead for 
Did you mean: 

CBS activation error

Former Member
0 Kudos

Hi All,

We are currently having an issue in one of our NWDI tracks. The broken DCs in dev buildspace have been fixed. However, in cons buildspace, the broken DCs exist. When I am trying to activate an activity, it shows the following error in the logs.

Should I try to Activate even if the build fails ?

        Analyze request DC BV... started at 2012-08-01 09:55:09.793 GMT

                'sap.com/crm/home/crm/ext' variant 'default'

                'sap.com/crm/home/crm/ext' variant 'default' cannot be built. ACTIVATION will fail.

                INVALID dependency is declared

                DC 'sap.com/crm/home/crm/ext' in SC 'sap.com_SAP-CRMWEB_1' USES Non-existing DC 'sap.com/activation' [public-part: ?] AS Build-Time Dependency  [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

        Analyze request DC BV... finished at 2012-08-01 09:55:09.871 GMT and took 78 ms

    ===== Pre-Processing =====  finished at 2012-08-01 09:55:09.871 GMT and took 4 s 656 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 "sap.com/crm/home/crm/ext" variant "default". The component is BROKEN.

Thanks,

Nikhil

Accepted Solutions (0)

Answers (1)

Answers (1)

dao_ha
Active Contributor
0 Kudos

Hi Nikhil,

How did you 'fix' the broken DCs in the Dev buildspace? Please refer to the following doc and see if you need to 'Initialize' the compartment

http://scn.sap.com/docs/DOC-1177

Hope it helps.

Dao

Former Member
0 Kudos

Hi Dao,

In the dev buildspace, I had to do a check-in and import of the SCs in CMS. By doing this, the broken DCs in dev buildspace were resolved. However, these broken DCs are still being shown in consolidation build space. There are a few activities which are being shown as pending. When I try to do "Activate even if a build fails", it gives the below error.

I have already initialized the compartment.

           Update DC metadata... started at 2012-08-01 13:32:25.095 GMT

                INVALID DEPENDENCIES: The following dependencies are marked as invalid:

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/tc/bi/bp/javaLib' DC, does not exist [public-part: saplib] AS Build Plugin Dependency

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

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Build-Time Dependency

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

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Deploy-Time Dependency

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

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Run-Time Dependency

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

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'uk.gov.tfl/csip/qasjars' DC of 'sap.com_SAP-CRMWEB_1' compartment [public-part: lib_api] AS Build-Time Dependency

[validity: OK]

                'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'uk.gov.tfl/csip/qasjars' DC of 'sap.com_SAP-CRMWEB_1' compartment [public-part: lib_package] AS Build-Time Dependency

[validity: OK]

                'sap.com/crm/home/crm/ext' DC is CHANGED

            Update DC metadata... finished at 2012-08-01 13:32:25.377 GMT and took 282 ms

            "sap.com/crm/home/crm/ext" in "default" variant was not built and has no build results to store.

            "sap.com/crm/home/crm/ext": store meta-data

            "sap.com/crm/home/crm/ext" in "default" variant  is PROCESSED

        STORE activation build results... finished at 2012-08-01 13:32:25.736 GMT and took 641 ms

        Change request state from PROCESSING to SUCCEEDED

       

        Analyze effect of applied changes to buildspace state... started at 2012-08-01 13:32:25.736 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/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Build-Time Dependency

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

            'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Run-Time Dependency

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

            'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/com.sap.km.trex.client' DC, does not exist [public-part: default] AS Deploy-Time Dependency

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

            'sap.com/crm/home/crm/ext' DC of 'sap.com_SAP-CRMWEB_1' compartment USES 'sap.com/tc/bi/bp/javaLib' DC, does not exist [public-part: saplib] AS Build Plugin Dependency

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

           

            Handle Cycles... started at 2012-08-01 13:32:26.049 GMT

                No new cycles detected.

            Handle Cycles... finished at 2012-08-01 13:32:27.189 GMT and took 1 s 140 ms

           

            Determine components that have become DIRTY due to the results of this request started at 2012-08-01 13:32:27.408 GMT

                No such components have been found.

            Determine components that have become DIRTY due to the results of this request finished at 2012-08-01 13:32:27.408 GMT and took 0 ms

        Analyze effect of applied changes to buildspace state... finished at 2012-08-01 13:32:27.408 GMT and took 1 s 672 ms

        Integrate activities into active workspace(s)...

       

        Integration of activities in compartment "sap.com_SAP-CRMWEB_1" started at 2012-08-01 13:32:27.408 GMT

        Integration of 1 activities in compartment "sap.com_SAP-CRMWEB_1" finished at 2012-08-01 13:32:27.517 GMT and took 109 ms

        An incomplete integration in compartment "sap.com_SAP-CRMWEB_1" of buildspace "DIP_CRMICSP_C" has resulted because of errors during request processing!

Request 6744 has been created to re-initialize the compartment

    ===== Post-Processing =====  finished at 2012-08-01 13:32:27.549 GMT and took 2 s 469 ms

    Change request state from SUCCEEDED to FAILED

    Error! The following problem(s) occurred  during request processing:

    Error! Communication error when performing integrations. Integration failed with unexpected CONFLICT status [com.sap.dtr.client.lib.protocol.entities.ErrorEntity@49207a77]. Request FAILED.

REQUEST PROCESSING finished at 2012-08-01 13:32:27.549 GMT and took 13 s 907 ms

Thanks,

Nikhil

dao_ha
Active Contributor
0 Kudos

Hi Nikhil,

After checking in & importing the SCs into development, did you also import them into Consolidation (in CMS)? That should do it (since the import did fix the broken DCs in Dev). I would not 'force' the activation.

Regards,

Dao