cancel
Showing results for 
Search instead for 
Did you mean: 

Activation problem in NWDI

Former Member
0 Kudos

Hi all,

I have created new web dynpro DC, and i have successfully build and deploy my application on my local J2EE server.

Then i migrated my DC to NWDI , i checked in to DC and created 4 models, also i got no build errors. But when i activated the activity i got a build error, as

[wdgen] [Info] Component //WebDynpro/Component:com.abc.management.mangement.comp.ManagementComp could not be generated

[wdgen] [Error] Generation failed due to errors (3 seconds)

Error: /usr/sap/ND1/JC00/j2ee/cluster/server0/temp/CBS/47/.B/62428/t2/3C2891DB12C30854BDDE715C733BA249/default/logs/build.xml:162: [Error] Generation failed!

at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:275)

at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

at org.apache.tools.ant.Task.perform(Task.java:364)

at org.apache.tools.ant.Target.execute(Target.java:341)

at org.apache.tools.ant.Target.performTasks(Target.java:369)

at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)

at org.apache.tools.ant.Project.executeTarget(Project.java:1185)

at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:114)

at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:57)

at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)

at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)

at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)

at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:400)

at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)

at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)

at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)

at com.sap.tc.devconf.impl.DCProxyMake.make(DCProxyMake.java:260)

at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1574)

at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1556)

at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:747)

at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:513)

at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:452)

at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:324)

at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:262)

at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:217)

at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:177)

so i created a new activity, checked in and activited it(activate with all Predecessors) i am getting the same error.

Please let me know what the above error is due to?

Is there a way to resolve this issue or will i have to create everything from scratch?

Regards,

Ashwin Kulkarni.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Right click on the project ->DC ->Build,it will build the component and throw you errors.

For more inof check this forum:

Reagrds,

Lavanya.G

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Lavanya,

Thanks for your reply. The link to the thread you gave solved my problem.

Regards,

Ashwin kulkarni.

Former Member
0 Kudos

Hi Ashwin,

If there is an error while activation, please check the CBS Activation log. You will get the exact error present in the development component. I suggest you post it here as well, we may help you.

Regards,

Gaurav Bhardwaj

Former Member
0 Kudos

Hello,

can you please post further stacktrace?

I think the root cause is missing