Activation is failing

[Former Member]

Hi all,

We have setup a JDI server wherein we have created track for ESS using the JDI Cookbook. Everything was working fine & we were able to modify the code and check in our activities.But lately all of our activities have started failing. Whenever we do any modification, build the DC, & try to activate the activity, a request id is generated but after some we get a error log & the activation fails.

Can anyone help me on this. Why are the activities failing.It was working fine earlier but almost 5-8 activations on diff DC's has failed with the same error messages although they are building fine in Developer Studio.

Following is the error log:

Request Log - [ 1701/RIQ_ESSTrack_D ]

SAP Component Build Server

Build number assigned: 1718

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "RIQ_ESSTrack_D" at Node ID: 2,141,150

[id: 1,701; parentID: 0; type: 4]

[options: FORCE ACTIVATE PREDECESSORS, IGNORE COMPONENT INTERSECTION]

REQUEST PROCESSING started at 2005-12-11 22:58:11.725 GMT

===== Pre-Processing =====

List of activities to be activated:

1 activity in compartment "sap.com_SAP_ESS_1"

CCT31660_ess_tra_tre_ NN_1

[seq. no 12][created by ADMINISTRATOR at 2005-12-11 12:01:31.0][ID df1a1ea9554b11da88c600508bdfdc5e]

Analyse dependencies to predecessor activities... started at 2005-12-11 22:58:12.959 GMT

Analysing compartment "sap.com_SAP_ESS_1"

No dependencies to predecessor activities found.

Analyse dependencies to predecessor activities... finished at 2005-12-11 22:58:12.975 GMT and took 16 ms

Analyse activities... started at 2005-12-11 22:58:12.975 GMT

Synchronizing component "sap.com/ess/tra/tre" from repository... finished at 2005-12-11 22:59:11.178 GMT and took 54 s 406 ms

1 component to be build in compartment "sap.com_SAP_ESS_1"

Analyse activities... finished at 2005-12-11 22:59:11.381 GMT and took 58 s 406 ms

Calculate all combinations of components and variants to be built...

"sap.com/ess/tra/tre" variant "default"

Prepare build environment in the file system... started at 2005-12-11 22:59:12.053 GMT

Synchronize development configuration... finished at 2005-12-11 22:59:12.085 GMT and took 16 ms

Synchronize component definitions... finished at 2005-12-11 22:59:12.178 GMT and took 93 ms

Synchronize sources...

Synchronize sources... finished at 2005-12-11 23:02:15.992 GMT and took 3 m 3 s 814 ms

Synchronize used libraries...

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/col/api" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 31 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/cmi" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 30 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/ddic/ddicruntime" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 34 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/ddic/metamodel/content" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 35 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/wd/webdynpro" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 148 variant "default"][SC 167][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/logging" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 142 variant "default"][SC 167][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/wdp/metamodel/content" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 38 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.aii.proxy.framework" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 1 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.aii.util.misc" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 2 variant "default"][SC 171][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.exception" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 92 variant "default"][SC 167][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.mw.jco" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 95 variant "default"][SC 167][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/pcui_gp/xssfpm" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 158 variant "default"][SC 168][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/pcui_gp/xssutils" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

[DC 164 variant "default"][SC 170] using [DC 159 variant "default"][SC 168][is OK]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/col/api" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 31 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/cmi" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 30 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/ddic/ddicruntime" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 34 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/ddic/metamodel/content" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 35 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/wd/webdynpro" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 148 variant "default"][SC 167][last successfull build: 1533]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/logging" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 142 variant "default"][SC 167][last successfull build: 1533]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/tc/wdp/metamodel/content" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 38 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.aii.proxy.framework" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 1 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.aii.util.misc" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 2 variant "default"][SC 171][last successfull build: 1530]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.exception" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 92 variant "default"][SC 167][last successfull build: 1533]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/com.sap.mw.jco" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "default" of DC 95 variant "default"][SC 167][last successfull build: 1533]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/pcui_gp/xssfpm" has NO PUBLIC PART with name "FloorplanManager". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

[PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

[PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

[PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

"sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

Used component "sap.com/pcui_gp/xssutils" has NO PUBLIC PART with name "FPMUtils". Such a public part has not yet been defined or activated.

[DC 164 variant "default"][SC 170] using [PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

[PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

[PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

[PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

public part "Common" of component "sap.com/ess/tra" ... OK

[PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Common" of component "sap.com/ess/tra" ... OK

[PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Common" of component "sap.com/ess/tra" ... OK

[PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Common" of component "sap.com/ess/tra" ... OK

[PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Utils" of component "sap.com/ess/tra" ... OK

[PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Utils" of component "sap.com/ess/tra" ... OK

[PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "Utils" of component "sap.com/ess/tra" ... OK

[PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "UI" of component "sap.com/ess/tra" ... OK

[PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "UI" of component "sap.com/ess/tra" ... OK

[PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

public part "UI" of component "sap.com/ess/tra" ... OK

[PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

Synchronize used libraries... finished at 2005-12-11 23:02:17.367 GMT and took 1 s 375 ms

Prepare build environment in the file system... finished at 2005-12-11 23:02:17.383 GMT and took 3 m 5 s 330 ms

===== Pre-Processing ===== finished at 2005-12-11 23:02:17.383 GMT and took 4 m 5 s 611 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/ess/tra/tre" variant "default". The component is BROKEN.

REQUEST PROCESSING finished at 2005-12-11 23:02:17.383 GMT and took 4 m 5 s 658 ms

[htammen · Accepted solution]

Hi Gaurav,

try to rebuild your ESS compartment via CBS Web UI. Something seems to be broken.

Maybe it will be fixed if you build everything new.

Regards

Helmut

[Former Member · Accepted solution]

If that doesn't help, try reimporting the SC's that are listed in the Required Software Components part of your track and then rebuild again using the CBS Web UI.

[Former Member · Accepted solution]

Hi Helmut & Pascal,

Thanx for your reply.

In the buildspaces -> there is a tab "build the compartment" at the bottom after you select any track.

There we have "Initiate Build" & "initialize compartment" What does both of them mean and which which to perform.

Also i have a question here -> we have already been doing developement. so if i do a build is there a chance by which our changed code gets overwritten by this or we loose our changes.

Also same is my question for "<i>reimporting the SC's that are listed in the Required Software Components part of your track and then rebuild again using the CBS Web UI</i>"

I hope nothing gets broken in this case.

Also please check this tread.

It mentiones about restart. Is this really a problem (cache etc, what kind of a j2ee server this is..seems to be friend of windows family)?

We also restarted our server & everything is ok now. we are able to activate now without any error.

Does anybody know about this also.

Regards

Gaurav Gandhi

[htammen · Accepted solution]

Hi Gaurav,

1. Initiate build rebuilds the DCs of the chosen compartment. Initialize compartment does (as far as I know) additionally throw away all entries from syncdb so that really everything in the compartment is synced and then rebuild. CBS uses a syncdb to save time. Not everything has to be synced each time.

2. If you do a rebuild via CBS your sources are not changed or deleted. CBS does not change anything you developed. It just checks out the sources from DTR. This is also true for reimporting the required SCAs into your track. In this case the DCs (archives) of the corresponding compartment are deleted an then imported into the buildspace again.

This is e.g. suitable to update your track to a new SP level.

Regards

Helmut

[Former Member · Accepted solution]

Hi Helmut,

Thanx for the reply. Since right now my problem is resolved by just a restart, i will follow the steps mentioned by u next time ....& will let u know if this works.

Regards

Gaurav Gandhi