cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Assembly Components

Former Member
0 Kudos

Hello All.

We have a WebDynpro application in DC.

When i try Assembly Components in CMS - Transport Studio to transport the App to QAS occurs the error.

Finished with errors.

In Details Finished with errorn in CBS-Assembly

Error log:

Fatal: Broken development component: No export for "project name", because no old version is present.

Someone can help me to solution this problem ?

Thanks in advance...

Best Regards.

Accepted Solutions (0)

Answers (3)

Answers (3)

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

HI,

first it'd be important to know which DC is broken by itself and why.

As per Shreyas' instructions please go to the Compartment view, look up the SC which includes the broken DCs, then try to find the one which is broken by itself (the ones which have metadata brokenness are usually only marked by broken because they are depending on a DC which is broken). Can you see a DC which seems unique regarding the error situation marked by the red/green/yellow lamps ? Try to find the DC which has green metadata but red or yellow compile status. Now click on that DC and check its build log and copy-paste it here.

Thanks and Regards,

Ervin

Former Member
0 Kudos

Hi.

Sorry for the slow return..

I do not have access to CBS .... so is very difficult to be checking the problem.

After requesting the access for the basis to view the logs in CBS and CMS.

In CBS metadata State is OK Green, but the Compile Status is Red.

Build Status is red to.

This is the log result...

wdgen] WARNING: Metadata of component EntradaSaidaVUsina is not valid! Component "//WebDynpro/Component:su.clco.le.app.EntradaSaidaVUsina", Role "ComponentController": A minimum of 1 object(s) is required
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Dados_Ztr002_Input [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Dados_Ztr002_Output [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Dados_Ztr002_Output [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode E_Motorista [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode E_Motorista [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode E_Veiculo [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode E_Veiculo [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Proc_Especial_Input [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Error]   su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Proc_Especial_Output [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    su.clco.le.app.EntradaSaidaVUsinaCustom --> ContextModelNode Zsulef_Busca_Proc_Especial_Output [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
    

Thanks for your help.

Best Regards.

Taylor.

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Taylor,

please follow Shreyas' instructions.

If you need some background information on Broken DCs, see this guide:

Understanding Broken DCs and Dirty DCs

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

Best Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

Former Member
0 Kudos

Hello.

Thanks for your response.

In CBS ....in the track DEV the application is ok. Green.

In track CONS is error, Metadata Briken.

Can your guide me how i can sync the track DEV with Track CONS ?

Thsnks.

Taylor.

shreyas_pandya
Contributor
0 Kudos

Hi Taylor,

If you open the Page No. 6 of the first link (CBS Secrets Unveiled u2013 Understanding Broken and Dirty DCs), that is provided by Ervin, you will see the same problem statement which explains Analyzing a Single DC u201Cbroken due to its MetaDatau201D.

Please go through it carefuly, It will definitely help you.

Regards,

Shreyas Pandya

shreyas_pandya
Contributor
0 Kudos

Hi Taylor,

It is very much clear from the error that Assembly has failed due to the presence of a Broken DC in Consolidation Build-space.

Can you please check the followings...

Go to Component Build Services (CBS) Web UI >> (Build spaces >>)

Open the Consolidation Buildspace...

"<SID>_<Track-ID>_C" build space.

Here Select your Track SC in the First table...

Now you'll be able to see all the DCs contained inside that Software Component.

Please let me know how many DCs you have in there, and how many are broken?

To resolve the issue you need to find out the reason why DCs are broken and bring them back into the consistent build state.

Assemby operation will succeeds only if all the DC contained inside consolidation build-space are in consistent build state (Green).

If possible, kindly share the detailed error trace of the Assembly Failure...

Regards,

Shreyas Pandya