cancel
Showing results for 
Search instead for 
Did you mean: 

cbs build portal application dc fail. Build Plugin IS NOT DEFINED for this

Former Member
0 Kudos

hi all

I use NW7.0 ehp1,have portal and a nwdi.

I create a track at nwdi . and develop a portal application .

local build is ok . but when i check in .run a activitce. dc is broken.

-


log is -


CBS Request Log - [ 300/DEP_PESKM_D ]

Build number assigned: 314

Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2010-11-05 02:17:38.921 GMT

ACTIVATION request in Build Space "DEP_PESKM_D" at Node ID: 13,975,650

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

[options: NO OPTIONS]

Waiting for access: 79 ms

===== Pre-Processing ===== started at 2010-11-05 02:17:39.000 GMT

List of requested for activation activities:

'deep.com_PESKM_1' compartment

tet

[ISN 111][created by YANLIANG at 2010-11-05 10:17:31.0][OID 6b2f604ae87c11df94ff000000d54062]

There is 1 activity in compartment deep.com_PESKM_1

1 activity will be processed by this request

Analyze dependencies to predecessor activities... started at 2010-11-05 02:17:39.031 GMT

Analyzing predecessors in compartment "deep.com_PESKM_1"

No dependencies to predecessor activities found.

Analyze dependencies to predecessor activities... finished at 2010-11-05 02:17:39.046 GMT and took 15 ms

Analyze versions... started at 2010-11-05 02:17:39.046 GMT

List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-11-05 02:17:41.812 GMT and took 2 s 766 ms

Synchronize metadata for [deep.com.cn/dc_logo_par] started at 2010-11-05 02:17:41.812 GMT

Verification of DL [ws/PESKM/deep.com_PESKM/dev/active/] finished at 2010-11-05 02:17:41.906 GMT and took 0 ms

Verification of cache (level 2: Comparison of attributes) finished at 2010-11-05 02:17:41.937 GMT and took 31 ms

Synchronize metadata for [deep.com.cn/dc_logo_par] finished at 2010-11-05 02:17:41.937 GMT and took 125 ms

< CHANGE > 'deep.com.cn/dc_logo_par' DC

Analyze versions... finished at 2010-11-05 02:17:41.937 GMT and took 2 s 891 ms

Analyze activities... started at 2010-11-05 02:17:41.937 GMT

Loading component definitions

1 component to be build in compartment "deep.com_PESKM_1"

Analyze activities... finished at 2010-11-05 02:17:42.000 GMT and took 63 ms

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

Analyze request DC BV... started at 2010-11-05 02:17:42.109 GMT

'deep.com.cn/dc_logo_par' variant 'default'

'deep.com.cn/dc_logo_par' variant 'default' cannot be built. ACTIVATION will fail.

Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.

Analyze request DC BV... finished at 2010-11-05 02:17:42.140 GMT and took 31 ms

===== Pre-Processing ===== finished at 2010-11-05 02:17:42.187 GMT and took 3 s 187 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 "deep.com.cn/dc_logo_par" variant "default". The component is BROKEN.

REQUEST PROCESSING finished at 2010-11-05 02:17:42.187 GMT and took 3 s 266 ms

No build logs available for the request.

Edited by: yan liang on Nov 5, 2010 3:12 AM

Accepted Solutions (1)

Accepted Solutions (1)

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Yan,

please check the NWDI troubleshooting guide:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030

--> Understanding Broken and Dirty DCs

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51...

Did you import the dependent build plugins for the track in question?

(tab "development" in the /devinf --> CMS webui --> Transport studio)

See also the sap note: #1080927 - Creating CMS Tracks for Common Application Types (http://service.sap.com/sap/support/notes/1080927)

Best Regards,

Ervin

Answers (0)