cancel
Showing results for 
Search instead for 
Did you mean: 

Work Bench object activation failing

former_member548204
Participant
0 Kudos
353

Dear Experts,

i did installed the new development system with existing dev system copy. All objects are good and validated in workbench and created new track for this system, when i tried to activate the object, its immediately failing with no error logs. But when i checked it in NWDI logs, its says

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

Error! The following error occurred during request processing: Activation failed due to component "sap.com/tst/testproject" variant "default". The component is BROKEN.

please provide your inouts here if anyone comeacross the similar issue.

thanks
Venkata

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member189220
Active Contributor

Hello VenkataRao,

There are (at least 2 important) point you need to consider:

1.

When using NWDI/NWDS, for transporting custom code for MII, an explicit tool for releasing of the activity is mandatory. The MII development Workbench does not provide the Release feature. Hence, even after check-in and activation of activity in the MII workbench and activation in the CBS the source code is not transported. The cons dtr ws do not contain the source code. It is required to be used

*) either CMS Admin tool

Release activity using the cmstool

*) or NWDS DTR perspective - Release . Please have a look on this document for further details:

Migrating Local Developments to a Centralized NWDI Environment (Developer’s Viewpoint)

Step 8: Check-In

Step 9: Activate

Step 10: Release

2.

Error! The following error occurred duringrequestprocessing:Activation failed due tocomponent"sap.com/tst/testproject" variant "default". The component is BROKEN.

This error message hints for using JDK, which version is NOT compatible for your development. In other words, the CBS is trying to build your custom source code with libraries, which are not supported by (or can not be included in) the java classes in your application. Please ensure you have configured the correct build variant on the NWA, NWDI-CMS and JDK on the local PC is compatible with the JVM of the target deployment RTS (in your case - the MII server). Please read carefully this neatly written blog on this matter:

Configuring JDK settings with NWDI

3.

Last but not least, please consider, the following versions are consistent:

. NWDS,

. Software Components (SCs) in the Development Track Configuration

. RunTime System.

For more details please refer to this blog:

NWDI vs. NWDI content

Regards,