Unable to activate coz of pre-failed activity

[Former Member]

Hi Friends,

I have 2 activites, lets say first one is ABC and second one is XYZ.

I have created ABC activity first, and then i tried to activate it. Due to some missing jar, it failed.

Now i tried to fix that in that process i need to create second activitey XYZ. Now, when i try to activate XYZ, i am seeing ABC activity too for activation being it called as Predecessor.

Now, when i tried to activate with only option of 'activate with all predecessors', it is failing coz of ABC problem even when i fixed it in the next activity XYZ.

Could anyone pls let me know how to delete the activity which is already checked-in and failed at activation.

If i can delete the ABC activity then i can activate the XYZ activity.

Pls let me know..

Thanks,

Raghavendra Pothula

[Former Member]

Hi,

I am also facing same problem.

the activation log is as follows:

Build number assigned: 343

Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2008-01-24 10:01:11.267 GMT

ACTIVATION request in Build Space "D71_NEXTGEN_D" at Node ID: 717,085,850

[id: 409; parentID: 0; type: 4]

[options: FORCE ACTIVATE PREDECESSORS, IGNORE COMPONENT INTERSECTION]

Waiting for access: 16 ms

===== Pre-Processing ===== started at 2008-01-24 10:01:11.283 GMT

List of requested for activation activities:

'bhc.com_NG_SALES_1' compartment

model 3

[ISN 177][created by DVADITHYA at 2008-01-24 03:40:22.0][OID b95e96d3ca5f11dcc1ef001a64255dd4]

There is 1 activity in compartment bhc.com_NG_SALES_1

1 activity will be processed by this request

Analyze dependencies to predecessor activities... started at 2008-01-24 10:01:11.283 GMT

Analyzing predecessors in compartment "bhc.com_NG_SALES_1"

4 not activated predecessors are detected

The following activities are being added to request:

"model binding" [seq. no 175][created by DVADITHYA at 1/24/08 3:27 AM][ID 4dd92d3dca5d11dc93d6001a64255dd4]

"model 2" [seq. no 176][created by DVADITHYA at 1/24/08 3:35 AM][ID a9a14fc6ca5e11dc9d96001a64255dd4]

"model binding supp cat 24 jan 08" [seq. no 174][created by DVADITHYA at 1/24/08 3:20 AM][ID b5ae4010ca5c11dca88a001a64255dd4]

"Add Supp Cat to DTR" [seq. no 173][created by DVADITHYA at 1/24/08 3:14 AM][ID b97aae3eca5811dcb625001a64255dd4]

Analyze dependencies to predecessor activities... finished at 2008-01-24 10:01:11.377 GMT and took 94 ms

Analyze versions... started at 2008-01-24 10:01:11.377 GMT

List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2008-01-24 10:01:11.408 GMT and took 31 ms

Synchronize metadata for [bhc.com/nextgen/sales/soldtolookup] started at 2008-01-24 10:01:11.408 GMT

Verification of DL [ws/NEXTGEN/bhc.com_NG_SALES/dev/active/] finished at 2008-01-24 10:01:11.424 GMT and took 0 ms

Verification of cache (level 2: Comparison of attributes) finished at 2008-01-24 10:01:11.455 GMT and took 31 ms

Synchronize metadata for [bhc.com/nextgen/sales/soldtolookup] finished at 2008-01-24 10:01:11.455 GMT and took 47 ms

< CHANGE > 'bhc.com/nextgen/sales/soldtolookup' DC

Analyze versions... finished at 2008-01-24 10:01:11.455 GMT and took 78 ms

Analyze activities... started at 2008-01-24 10:01:11.455 GMT

Loading component definitions

1 component to be build in compartment "bhc.com_NG_SALES_1"

Analyze activities... finished at 2008-01-24 10:01:11.486 GMT and took 31 ms

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

Analyze request DC BV... started at 2008-01-24 10:01:11.486 GMT

'bhc.com/nextgen/sales/soldtolookup' variant 'default'

Analyze request DC BV... finished at 2008-01-24 10:01:11.564 GMT and took 78 ms

Prepare build environment in the file system... started at 2008-01-24 10:01:11.564 GMT

Synchronize development configuration... started at 2008-01-24 10:01:11.564 GMT

Synchronize development configuration... finished at 2008-01-24 10:01:11.580 GMT and took 16 ms

Synchronize sources for [bhc.com/nextgen/sales/soldtolookup] started at 2008-01-24 10:01:11.580 GMT

Verification of DL [ws/NEXTGEN/bhc.com_NG_SALES/dev/active/] finished at 2008-01-24 10:01:11.627 GMT and took 16 ms

Verification of cache (level 2: Comparison of attributes) finished at 2008-01-24 10:01:11.736 GMT and took 109 ms

Synchronize sources for [bhc.com/nextgen/sales/soldtolookup] finished at 2008-01-24 10:01:12.033 GMT and took 453 ms

Synchronize used libraries... started at 2008-01-24 10:01:12.642 GMT

PP 'default' of DC 'sap.com/tc/cmi' [DCID=68] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/tc/ddic/ddicruntime' [DCID=72] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/tc/ddic/metamodel/content' [DCID=73] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/tc/wd/webdynpro' [DCID=269] (in SC 'sap.com_SAP-JEE_1' [SCID=277]) ... OK

PP 'default' of DC 'sap.com/tc/logging' [DCID=257] (in SC 'sap.com_SAP-JEE_1' [SCID=277]) ... OK

PP 'default' of DC 'sap.com/tc/wdp/metamodel/content' [DCID=89] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/com.sap.aii.proxy.framework' [DCID=4] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/com.sap.aii.util.misc' [DCID=5] (in SC 'sap.com_SAP_JTECHS_1' [SCID=280]) ... OK

PP 'default' of DC 'sap.com/com.sap.exception' [DCID=196] (in SC 'sap.com_SAP-JEE_1' [SCID=277]) ... OK

PP 'default' of DC 'sap.com/com.sap.mw.jco' [DCID=199] (in SC 'sap.com_SAP-JEE_1' [SCID=277]) ... OK

Synchronize used libraries... finished at 2008-01-24 10:01:13.799 GMT and took 1 s 157 ms

Prepare build environment in the file system... finished at 2008-01-24 10:01:13.799 GMT and took 2 s 235 ms

===== Pre-Processing ===== finished at 2008-01-24 10:01:13.799 GMT and took 2 s 516 ms

===== Processing ===== started at 2008-01-24 10:01:13.799 GMT

BUILD DCs

'bhc.com/nextgen/sales/soldtolookup' in variant 'default'

.. FAILURE: The build failed due to compilation errors. See build log for details. [result code: 202]

===== Processing ===== finished at 2008-01-24 10:01:23.736 GMT and took 9 s 937 ms

===== Post-Processing =====

Waiting for access: 16 ms

===== Post-Processing ===== started at 2008-01-24 10:01:23.752 GMT

Check whether build was successful for all required variants...

"bhc.com/nextgen/sales/soldtolookup" in variant "default" FAILED

===== Post-Processing ===== finished at 2008-01-24 10:01:23.752 GMT and took 0 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 build problems. See build logs for details.

REQUEST PROCESSING finished at 2008-01-24 10:01:23.752 GMT and took 12 s 485 ms

Thanks,

Kanchan

[Former Member]

What's the exact error in the Activation log?

[Former Member]

Hi

This behaviour is strange. I would assume it pick the latest version of the file for build purpose. Try force- checking (clicking on Advanced). Recreate the project on another machine which doesnt have this project and see if you are getting a clean project from the DTR by performing a successful build using NDS. If not correct the error and check in the correction

Regards

Pran