Activating Web Dynpro DC fails

Hi Experts,
I try to activate my activities. But they fail with an error message. In the error message there is printed that the component and the startup plug is missing. But that's not true. They exist and when i deploy the application to a portal directly the application works. What could be wrong?
Here the build log:
DC Model check:
 All used DCs are available locally
 validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
 validating dependency to public part "default" of DC "sap.com/tc/cmi"
 validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
 validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
 validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
 validating dependency to public part "default" of DC "sap.com/tc/logging"
 validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
 validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
 validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
 validating dependency to public part "default" of DC "sap.com/com.sap.exception"
 validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
 DC model check OK
Start build plugin:
 using build plugin: sap.com/tc/bi/bp/webDynpro
 starting build plugin from : F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 9 (645_VAL_REL, built on 2006-08-26 18:15:25 CEST)
 development component: dc2test (com.chiron.test)
 software component: NWDIDEMO (nwdi)
 location: DI1_DEMO_D
 type: Web Dynpro
 build variant: default
 source location: http://cwte0066:50000/dtr/ws/DEMO/nwdi_NWDIDEMO/dev/active/
 plugin start time: 2007-11-13 12:54:28 GMT+01:00 (CET)
 Java VM: Java HotSpot(TM) 64-Bit Server VM, 1.4.2_12-b03 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Source folder META-INF exists but is empty.
Source folder src/mimes exists but is empty.
Source folder src/configuration exists but is empty.Plugin initialized in 1.219 seconds
Preparing data context..
No 'default' JDK defined, will use running VM.
Data context prepared in 0.078 seconds
Executing macro file..
Using macro file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
Creating output file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\gen\default\logs\build.xml
Macro file executed in 0.969 seconds
Starting Ant..
Using build file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\gen\default\logs\build.xml
Using build target: build
Generation folder: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60
Using Ant version: 1.6.2
compile:
 [echo] Starting dictionary generator
 [ddgen]
 [ddgen] [Info] Property deployment is true: Deployment information is provided!
 [ddgen] [Info] Property sourcepath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\src\packages
 [ddgen] [Info] Property targetpath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_ddic
 [ddgen] [Info] Property archivename: com.chiron.test~dc2test
 [ddgen] [Info] Property vendor: com.chiron.test
 [ddgen] [Info] Property dcname: dc2test
 [ddgen] [Info] Property projectlanguage: de
 [ddgen] [Info] Property language: Available languages are automatically determined!
 [ddgen] [Info] Property addpaths ...
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] jrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] cmiapi.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproadmin.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynprobasesrvc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproclientserver.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpromodelimpl.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpromodel_dynamicrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpropdfobject.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproportal.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproprogmodel.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_designtime_coupling.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_designtime_coupling_api.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_repository.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_repository_pmr.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproservices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] exception.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] aii_util_misc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] aii_proxy_rt.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] logging.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] logging.perf.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapDictionaryTypeServices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapDictionaryTypesRuntime.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] Initialize generation templates from configuration jar:file:/F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
 [ddgen] [Info] Generating dbtables/sdmDeployDd.xml
 [ddgen] [Info] Generation finished (4 seconds)
 [ddgen]
 [timer] Dictionary generator finished in 4.625 seconds
 [mkdir] Created dir: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_ddic\datatypes
 [echo] Starting WebDynpro generator
 [wdgen]
 [wdgen] [Info] Property deployment is true: Deployment information is provided!
 [wdgen] [Info] Property sourcepath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\src\packages
 [wdgen] [Info] Property targetpath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_wdp
 [wdgen] [Info] Property archivename: com.chiron.test~dc2test
 [wdgen] [Info] Property vendor: com.chiron.test
 [wdgen] [Info] Property dcname: dc2test
 [wdgen] [Info] Property projectlanguage: de
 [wdgen] [Info] Property language: Available languages are automatically determined!
 [wdgen] [Info] Property addpaths ...
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] jrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] cmiapi.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproadmin.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynprobasesrvc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproclientserver.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpromodelimpl.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpromodel_dynamicrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpropdfobject.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproportal.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproprogmodel.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_designtime_coupling.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_designtime_coupling_api.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_repository.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_repository_pmr.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproservices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] exception.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] aii_util_misc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] aii_proxy_rt.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] logging.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] logging.perf.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapDictionaryTypeServices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapDictionaryTypesRuntime.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] Initialize generation templates from configuration jar:file:/F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
 [wdgen] [Error] com.sap.chiron.DITestApp2 --> Application DITestApp2: Component is missing
 [wdgen] [Error] com.sap.chiron.DITestApp2 --> Application DITestApp2: Startup plug is missing
 [wdgen] [Info] Catching throwable null [wdgen] [Info] com.sap.webdynpro.generation.ant.GenerationAntTaskError
 [wdgen] at com.sap.webdynpro.generation.ant.GenerationAnt.showCheckResult(GenerationAnt.java:157)
 [wdgen] at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2047)
 [wdgen] at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1554)
 [wdgen] at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:215)
 [wdgen] at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [wdgen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [wdgen] at java.lang.reflect.Method.invoke(Method.java:324)
 [wdgen] at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
 [wdgen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 [wdgen] at org.apache.tools.ant.Task.perform(Task.java:364)
 [wdgen] at org.apache.tools.ant.Target.execute(Target.java:341)
 [wdgen] at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [wdgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
 [wdgen] at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:111)
 [wdgen] at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:62)
 [wdgen] at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:222)
 [wdgen] at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:199)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [wdgen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [wdgen] at java.lang.reflect.Method.invoke(Method.java:324)
 [wdgen] at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
 [wdgen] at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
 [wdgen] at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
 [wdgen] at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
 [wdgen] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
 [wdgen] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
 [wdgen] ERROR: Unknown exception during generation null (com.sap.webdynpro.generation.ant.GenerationAntTaskError)
 [wdgen] ERROR: Generation failed due to errors (0 seconds)
Ant runtime 6.234 seconds
Ant build finished with ERRORS
[Error] Generation failed!
Error: Build stopped due to an error: [Error] Generation failed!
Any help is appreciated!
Regards Manuel

Hi Manuel,
that red flash is visible on a WebDynpro application in a WD specific view, right? I'm not a WebDynpro expert but I would assume that it indicates an issue with the application - probably the same thing that is reported by the central build.
Do you get the same error message in a local DC build in your NWDS?
(BTW: The "folder ... exists but is empty" is usually not relevant. The folders mentioned in the log may be empty as they are only used for special purposes. If they are defined in the DC Metadata CBS will create empty folders in the filesystem and the build plugin simply checks this. If the folders do exists in your local NWDS and contain files then there's something wrong, otherwise it should be safe to ignore the message.)
From your description I would assume that something is really wrong with your WebDynpro application, maybe you accidentally deleted the component? (Maybe the WD forum is better suited for such questions?)
Regards,
Marc

Similar Messages

Web Dynpro Java : Failed to get deployable object part info for component

Currently we have a web dynpro java project which connects to the ABAP backend with Web Services. Everything seems fine, and when we transport to the production server via NWDI, we have the following error. Everytime we try to access the application , the error is occurred.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sie.attachmentcomp.AttachmentComp
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:784)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:934)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
 at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
 at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
It is working properly in our development , and testing environment. Only production has this error. And one weird thing is that this particular error occurred only sometimes to some user. For example; I could not access to the application with this error yesterday but my friend can access. Today, I can access in the morning but my friend cannot. For another friend , Yesterday he can access by using IE but not by Firefox. But today Firefox is fine but not with IE. It seems crazy.
For more information, in our J2EE engine for the production server, we have 3 server nodes (clusters). And we are not sure it is the source of the problem. Is there any solution , and any way to know from the application that we are on which server?
We also go and check from the Content Administrator in Web Dynpro Console. Under our project name, in the list of Components, sometimes we can see AttachmentComp but sometimes not.
Please help us as our project is about to go-live next week.
Thanks,
Yu

Hi Meenge,
Please check below document for finding root cause for "Failed to start deployable object part info for <development component> and application <application name>"
http://help.sap.com/saphelp_nwce711core/helpdata/en/44/7716e1633a12d1e10000000a422035/frameset.htm
OR http://help.sap.com/saphelp_nw04/helpdata/EN/f4/1a1041a0f6f16fe10000000a1550b0/frameset.htm
Hope it helps
Regards
Arun

Restart dialog instances after activating web dynpro abap services (SICF)

Has anyone encountered a problem where you have to restart the ABAP dialog instances after activating a web dynpro abap service in SICF?
We're implementing some of the HR Admin, ESS, and MSS ABAP Web Dynpro applications. What is happening is that when we access these web dynpro abap applications the browser would go into an infinite loop. This happens only when we have an abap central instance and one or more abap dialog instances. It doesn't happen when we have just an abap central instance. The way we fixed it is by restarting just the dialog instances (the central instance was left running), but this isn't an acceptable solution for the production environment. Is there something else we have to do after activating the web dynpro abap service in SICF? We tried clearing the cache, but that doesn't work.
The landscape where this is happening is as follows:
1. SAP Portal is being used to present the ABAP web dynpro app. Portal is NW 7.0 SP15
2. There is a web dispatcher for both the SAP Portal
3. There is a web dispatcher for the ECC ABAP system. ECC ABAP system is on NW Basis 7.0 SP14.
Thanks.
Regards,
Mel Calucin
SAP Portal Architect

I actually found the same note 30 minutes ago. I gaveyou full credit though.
Thanks!

Web Dynpro iView fail to execute on portal side

Hi Gurus
I have Created Web Dynpro Application in Backend ( ECC ).
If i tested them from SICF transaction or SE80 transaction they are working fine.
Now on Portal side, I hav created Web Dynpro iView for Those ICF Services (Web Dynpro Apllications).
But most of time they Fails to execute from Portal side.
Symptoms :
On Browser Status Bar It keep on refreshing that iView address.
and Nothing comes on O/P side.
What culde be the Problem ?
How To resolve !!
Thanks & Regards
PK

This regularly happens to us with new WDA applications - seems to be a "bug".
Deactivate the service in SICF and reactivate it, then try your iView again.
If that doesn't work, deactivate the whole WebDynpro node in SICF and reactivate it (including all relevant sub nodes & services).
Pretty sure that will fix it.

Absolute URL IMAGE UI control in Web Dynpro ABAP fails

I would like to display a .jpg from the Internet, either using a URL or an RFC Destination as the source.
The "Web Dynpro ABAP Development in Detail" manual says that this can be done using only the Source attribute of the IMAGE UI control (see page 114) - that is,
   create an RFC Destination G-HTTP entry for the URL,
   type in that RFC Destination as $NAME$
   append any further extension of the URL as "/path in lower letters"
I can enter an RFC Destination (ex., $UBERORBS$) which points directly to a single image file via its host/path and it is displayed in SE80's Layout Preview, but nothing displays at runtime.
If I try to extend an RFC Destination's path to point to that image file (ex., $UBERORBS_BASE$/uberorbs_44pence.jpg), the image is also displayed in the Layout Preview, but not at runtime.
Is this a bug? or something wrong with our implementation? We are at SAP_BASIS 700 level 0006.
(Also, if the Source entry is not exactly correct, SE80 aborts following the entry with STRING_OFFSET_NEGATIVE.)

Here's another piece of information.
I am able to use the test app WDR_TEST_UI_ELEMENTS to display at runtime the $UBERORBS$ RFC Destination-absolute URL image.
So, does this mean that there is a critical setting within my Web Dynpro component which must be set properly to permit this?

MSS web dynpro personalization fails

We have upgraded to NW04s SP10 (standalone protal) and ERP2005 ECC 6.0. When we use the web dynpro personalization (preview iview, ctrl+right mouse click) we are able to change labels, fields, etc. and we can see the change when we choose apply/ok. If we then close the preview and preview it again the change is gone. Help! I have also opened a customer message with SAP.

Hi Daniel,
Did you get this issue sorted out.
If so could you please tell me how to replicate the changes done through ctrl+right click(UI Personalisation using Portal).
Regards,
Sreenath

Error when Creating Web Dynpro Model in CAF-Service

Hi All,
I reaaly need help. AFter updating to SPS 9, it was necessary to redeploy my Entity Service. That contains to "Create a Web Dynpro Model" in the Service Explorer,
to get an interface of the Service in my Web Dynpro Application.
Before I update to SPS 9, the Application works fine.
But now, when I want to "Create a Web Dynpro Model" in the NWDS I get the following Error-Message (its not a useful Error-Message):
Error cannot create Web Dynpro Model:
Creation of Web Dynpro model failed. Reason: null 
Thanks for helping me
Steve

Hi Aliaksei,
the problem in the thread is the same I got.
When I use only 7 letters for the operation name, the creation work. When I use more then 7 letters the creation doesnt work.
But its hard to find a methodname with only 7 letters.
In SPS 8 I didnt have problems with the length of method names. Why is it so?
The workspace log:
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.577
!MESSAGE Oct 10, 2006 3:12:45 PM com.sap.ip.mmr.foundation.AssociationsOfObject [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.592
!MESSAGE Oct 10, 2006 3:12:45 PM com.sap.ip.mmr.foundation.AssociationsOfObject [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO:
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO:
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)
!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)
Thanks
Steve

Web Dynpro component activation failed

I tried to activate a web dynpro component and the activation failed. Have listed error messages from the request log and activation log. Do let me know what could be the issue. The application deployed successfully on my local J2EE.
Request log details are as follows:
===== Processing =====
BUILD DCs
     "hubbell.com/appl/ptl.wd.regtool" in variant "default"
          .. FAILURE: The build failed due to compilation errors. See build log for details. [result code: 202]
===== Processing ===== finished at 2005-11-29 00:09:48.813 GMT and took 18 s 899 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
     "hubbell.com/appl/ptl.wd.regtool" in variant "default"   FAILED
===== Post-Processing ===== finished at 2005-11-29 00:09:48.823 GMT and took 3 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.
Activation log details are as follows:
wdgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/EDP/JC00/j2ee/cluster/server0/temp/CBS/79/.B/3223/DCs/sap.com/tc/bi/wd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
    [wdgen] [Error]   com.hubbell.ptl.rgstr.app.Registration -->
   Application Registration: Component is missing
    [wdgen] [Error]   com.hubbell.ptl.rgstr.app.Registration -->
   Application Registration: Startup plug is missing
    [wdgen] [Error]   Generation failed due to errors (0 seconds)
Build with ERRORS
file:/usr/sap/EDP/JC00/j2ee/cluster/server0/temp/CBS/79/.B/3223/DCs/hubbell.com/appl/ptl.wd.regtool/_comp/gen/default/logs/build.xml:49: [Error]   Generation failed!

There's obviously something missing in your WD DC: "Startup plug is missing". Your code has been checked-in to the inactive workspace. What you can do now is synchronize your DC with the server. You should get the same error then in your local NWDS and solve it.

System Connection Test was not fully tested but all web dynpro java app and Transaction iviews working fine.Any problem for this Kind of activity Lets give some idea.

System Connection Tests
You can test the connectivity to the backend application represented by the current system object. Choose the relevant tests.
Note: The test is based on the properties currently defined in the system object. It does not check if the system properties are correct.
System Connection Tests
Test Name
Description
Status
SAP Web AS Connection
Tests the connection to an SAP Web Application Server
ITS Connection
Tests the connection to an SAP ITS server
Connection Test for Connectors
Tests the connection to a backend system using an associated connector
Test
Clear Results
Results
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name
5. The host name ssprdxi.stylespasapnet.com was resolved successfully.
6. The Web AS ping service was pinged successfully.
7. An HTTP/S connection to was obtained successfully.
ITS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name ()
6. The host name ssprdxi.stylespasapnet.com was resolved successfully.
7. An HTTP/S connection to was obtained successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
regards
Antony

Hi Stefan,
This correct see SAP Note [947081|https://service.sap.com/sap/support/notes/947081]
If the locale for the Web Dynpro iView is changed in the portal (through portal personalization), this is not reflected in the running login session. The user needs to logoff and login again, in order to see the locale change in the Web Dynpro iView.
Regards,
Leo

Patch NW04s SPS09 Container Web Dynpro is not active

Hello SDN,
I am trying to patch my NW04s SPS08 Portal to SPS09.
I get the following error message. I am not able to start the web dynpro container.
Has anyone of you an idea whats going on?
Thanks.
Best Regards,
Olaf Reiss
Sep 14, 2006 3:39:20 PM Info: SDA to be deployed: D:\usr\sap\S05\JC51\SDM\root\origin\sap.com\tc\kmc\kmc.people.shared\wd_picker\SAP AG\1\7.0009.20060804134857.0000\sap.comtckmckmc.people.sharedwd_picker.ear
Sep 14, 2006 3:39:20 PM Info: Software type of SDA: J2EE
Sep 14, 2006 3:39:21 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 14, 2006 3:39:29 PM Info: Begin of log messages of the target system:
06/09/14 15:39:23 - ***********************************************************
06/09/14 15:39:26 - Start updating EAR file...
06/09/14 15:39:26 - start-up mode is lazy
06/09/14 15:39:27 - EAR file updated successfully for 751ms.
06/09/14 15:39:27 - Start updating...
06/09/14 15:39:28 - EAR file uploaded to server for 391ms.
06/09/14 15:39:29 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/tckmckmc.people.shared~wd_picker..
                     Reason: Container webdynpro is not active at the moment and it is not possible to update sap.com/tckmckmc.people.shared~wd_picker.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container webdynpro is not active at the moment and it is not possible to update sap.com/tckmckmc.people.shared~wd_picker.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container webdynpro is not active at the moment and it is not possible to update sap.com/tckmckmc.people.shared~wd_picker.
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:483)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
                          ... 10 more
                     For detailed information see the log file of the Deploy Service.
06/09/14 15:39:29 - ***********************************************************
Sep 14, 2006 3:39:29 PM Info: End of log messages of the target system.
Sep 14, 2006 3:39:29 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 14, 2006 3:39:29 PM Error: Aborted: development component 'tc/kmc/kmc.people.shared/wd_picker'/'sap.com'/'SAP AG'/'7.0009.20060804134857.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tckmckmc.people.shared~wd_picker..
Reason: Container webdynpro is not active at the moment and it is not possible to update sap.com/tckmckmc.people.shared~wd_picker.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container webdynpro is not active at the moment and it is not possible to update sap.com/tckmckmc.people.shared~wd_picker.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Sep 14, 2006 3:39:29 PM Info: Starting to save the repository
Sep 14, 2006 3:39:32 PM Info: Finished saving the repository
Sep 14, 2006 3:39:32 PM Info: Starting: Update: Selected software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060806101400''/'1' updates currently deployed software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.8.0.20060601154400''/'0'.
Sep 14, 2006 3:39:32 PM Error: Aborted: software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060806101400''/'1':
Failed deployment of SDAs:
development component 'tc/kmc/kmc.people.shared/wd_picker'/'sap.com'/'SAP AG'/'7.0009.20060804134857.0000'/'1' : aborted
Please, look at error logs above for more information!
Sep 14, 2006 3:39:32 PM Info: Starting to save the repository
Sep 14, 2006 3:39:34 PM Info: Finished saving the repository
Sep 14, 2006 3:39:34 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 14, 2006 3:39:34 PM Error: -
At least one of the Deployments failed -

Hello Prakash
I have same problem as above
I'm patching to SPS10 and problem with "BI-WDALV" occurs.
Dec 13, 2006 11:23:31... Info: End of log messages of the target system.
Dec 13, 2006 11:23:31... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 13, 2006 11:23:31... Error: Aborted: development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'963367'/'0',
grouped by software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.10.0.20061025062313''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/bialvcommon..
Reason: Container webdynpro is not active at the moment and it is not possible to update sap.com/bialvcommon.; nested
exception is:
        com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container webdynpro is not active at the mo
ment and it is not possible to update sap.com/bialvcommon.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionT
ypes).REMEXC)
Dec 13, 2006 11:23:31... Info: Starting to save the repository
Dec 13, 2006 11:23:34... Info: Finished saving the repository
Dec 13, 2006 11:23:34... Info: Starting: Update: Selected software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'100
0.7.00.10.0.20061025062313''/'0' updates currently deployed software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1
000.7.00.9.0.20060811133149''/'0'.
Dec 13, 2006 11:23:34... Error: Aborted: software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.10.0.20061
025062313''/'0':
Failed deployment of SDAs:
development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'963367'/'0' : aborted
Please, look at error logs above for more information!
Dec 13, 2006 11:23:34... Info: Starting to save the repository
Dec 13, 2006 11:23:36... Info: Finished saving the repository
Dec 13, 2006 11:23:36... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment proce
ss.
Dec 13, 2006 11:23:36... Error: -
At least one of the Deployments failed -
how can I manually deploy that file?
thanks alot
Best regards,
Olzhas Suleimnoev

ADT: Web Dynpro view/window error "Failed to create the part's controls"

Hi, all
Most of the things in my ADT work fine (e.g. programs, structures, domains), even the Web Dynpro Componentcontroller can be edited.
However, with Web Dynpro view and window I get this error message: "Failed to create the part's controls".
In SAP GUI everything works fine.
Why could this happen and what can I do?
My system details:
32-bit Windows 7
Eclipse Luna Release (4.4.0)
ADT from https://tools.hana.ondemand.com/kepler, according to these instructions: SAP Development Tools for Eclipse.
SAP GUI 7.30, patch level 9.
SAP_ALL authorizations
Java: SE, version 7 update 60
Activated services (SICF): wdy_aie_vd_preview, toolsdocu, docu
The Java error log in Eclipse is quite long. It starts with:
java.lang.IllegalStateException: java.lang.IllegalArgumentException: No enum constant com.sap.adt.wda.controller.semanticfs.common.ControllerFileServices.ControllerObjectTypeEnum.WDYNWZ
    at com.sap.adt.tools.core.ui.editors.AdtFormEditor.addPages(AdtFormEditor.java:222)
    at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138)
    at com.sap.adt.tools.core.ui.editors.AdtFormEditor.createPages(AdtFormEditor.java:1251)
    at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:362)
    at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140)
    at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
    at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321)
    at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
As it is not popular to post long logs unnecessarily, I will skip the rest of it for the moment - let me know if it could help and I will post it.
Thanks for help!
KR,
Igor

Hi Ponraj,
note applied without any problem.
I'm still facing some difficulties accessing a WD component, maybe you could suggest me how to solve/proceed:
in Eclipse Luna, I can access now a WD but "Layout" tab doesn't work - HTTP 403 Forbidden - Service cannot be reached. I guess it's a missing configuration, could you help me out on this?
EDIT: This one is solved; I just missed to activate a service in SICF (WDY_AIE_VD_PREVIEW).
That Eclipse module however seems not to be very stable; I tried to open a standard SRM WD view (wd component /SAPSRM/WDC_DO_SOCO_GAF_1, view V_AO_SOCO_GAF_1) and that resulted in the message:
500 SAP Internal Server Error
ERROR: Conversion of type C LENGTH 255 to type TABLE OF DEEP_STRUCTURE not supported. (termination: RABAX_STATE)"
is there a way, from the Methods tab, to access directly to a particular method's implementation? The only way I found is going manually under the IMPLEMENTATION tab and CTRL+F with the method's name.
is there any way to access to a particular enhancement made on the WD? Using SapGUI, there's a special "vortex" button to switch on a specific enhancement, but under Eclipse I can't find the alternative command.
I know we're getting a bit OT with respect to the topic, anyway if there's a guide that could help clarifying my doubts please, share that documentation
BR,
M.

SDM failed when deploying a Web Dynpro application

SDM failed when deploying a Web Dynpro application - I get the following error message:
Sep 19, 2006 2:25:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : eix-blade-011
SDM port : 50118
URL to deploy : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp43621sap.comwelcome.ear
Deployment exception : Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011
Inner exception was :
Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011

Amr Azim,
You must have logged in thru a dedicated connection to any server through say VPN before deploying.This way the sdm uses the same login as that of already establised connection.
So 'sign of' all connections to any servers before deploying and redeploy your application.Here you will be prompted to supply the sdm password and deployment shall proceed.

No NWDI activity asked while modifying the Web Dynpro java code

Hi,
We have 2 team in our project, one offshore team and one onsite team. We have NWDI also in our landscape.
I have created 1 project in my local NWDS from DTR using create project option from NWDI track , when i do any modification in that web dynpro code once it appears in my local NWDS, its asking for the activity, all this is fine.
But when my offshore team send me this project from offshore (offshore team also working on this project), i go to my local machine under C:\Documents and Settings\user\.dtc\0\DCs\xyz.org\.. (workspace, where all the project folders are created in my local machine ) and replaces the web dynpro project (which i created using create project option from NWDI track ) with the project which offshore teams gave me that is I copy paste the project folder I received from offshore team.
I closed the NWDS and reopened NWDS, i did repair and reload also, but now when i try to do any code modification in that project its not asking any activity at all. So i want to know the reason why its not asking activity at all while modifying the code.
if now i do any code changes, and since no activity is asked, it wont be transported to QA and Prd system.
Can anyone have any suggestion on this..

Hi GLM,
I think you might be right that some files are in read as well as write mode. I went to my local machine and checked the project folder C:\Documents and Settings\user\.dtc\0\DCs\xyz.org\testproject\_comp\.dcdef file , its not in read only mode, that is read only flag was not checked.
I again checked the mode of .dcdef file in other web dynpro projects which are asking for the activity in all those projects mode of .dcdef was read only that is read only flad was checked in .dcdef file. ( I am not sure is .dcdef file only giving this problem that si because of this file not in read only mode I am not asked for the activity)
So could you plzz tell me how to make in read only. when ever i click the read only check box of .dcdef file and reload the project in my NWDS. that read only check box is getting removed. how to do this..
regarding your query, landscape in offshore team and onsite team are different, client has not provided nay access to its landscape to ofshore team so offshore team can not check in / check out the code written by me and same applies to me I can not check in / check out the code written by offshore team , only option is offshore team do some changes in the code and send the project folder via email and I have to deploy in client landsacpe and do further modification.

Failed to create deployable object '********' since it is not a Web Dynpro object - Migration from 7.0 to 7.4

I have installed NWDS 7.30 EHP1 SP 14 PAT000   with JVM 6 SAP AG
to   migrate wedynpro development components from 7.0 to
NW7.4 WAS SAP AG 1.6.0_85 on Windows Server 2008 R2 6.1 SP09 PAT000
In track imported below SCAs of version 7.31 SP14 .
Could able to migrate and build in NWDS, getting deployment errors.
Followed
http://scn.sap.com/docs/DOC-55584
and
http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content
COMP_BUILDT
ECM-CORE
ENGFACADE
ENGINEAPI
ESCONF_BUILDT
FRAMEWORK
MOIN_BUILDT
SAP_BUILDT
WD-RUNTIME
Deployment Errors:-
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
    at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
    at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
    at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
    at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] Operation [update] of [sdu id: [XXXXXXX.com_home~chgemail]
sdu file path: [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
] failed
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)
    at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
    at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
    ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [update] of [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear] failed
    at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:489)
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
    ... 11 more
Caused by: com.sap.engine.services.servlets_jsp.webcontainer_api.exceptions.WebContainerExtensionDeploymentException: Error during deployment of application {0}
    at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:52)
    at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeployInternal(ExtensionHandler.java:169)
    at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeploy(ExtensionHandler.java:129)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.deploy(WebContainerProvider.java:334)
    at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:360)
    at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:327)
    at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:446)
    at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:582)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
    ... 12 more
Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.DeploymentException: Failed to deploy application 'XXXXXXX.com/home~chgemail'.
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:324)
    at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.notifyOnDeploy(DeployableObjectInternal.java:122)
    at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:49)
    ... 27 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:79)
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObjectFactory$1.getDeployableObject(AbstractDeployableObjectFactory.java:87)
    at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObject(WDDeployableObject.java:43)
    at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.calculateVMOsOfDeployableObject(RepositoryContainerHook.java:264)
    at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:181)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:297)
    ... 29 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.
    at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:228)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:77)
    ... 34 more
Deployment Items status: [
----- Sorted Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
----- Deployment Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
         -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
        Time statistics( ms ):
            1.Check version:XXXXXXX.com_home~chgemail : 4
            2.validate : -1
                2.1.Resolve dependencies : 3
                2.2.deployment : 7055
                    2.2.1.Notify:Event triggered : 203
                    2.2.2.Bulk deployment : 6839
                        2.2.2.1.Stop : 73
                        2.2.2.2.Perform delivery : 6765
                            2.2.2.2.1.Application Deployer : 6615
                    2.2.3.Notify:Event performed : 9
                2.3.Post process : 10
                    2.3.1.Starting : 9
]      [Error: com.sap.engine.services.tc~bl~deploy~api Thread[Worker-444,5,main]]
Deployment Items status: [
----- Sorted Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
----- Deployment Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
         -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
        Time statistics( ms ):
            1.Check version:XXXXXXX.com_home~chgemail : 4
            2.validate : -1
                2.1.Resolve dependencies : 3
                2.2.deployment : 7055
                    2.2.1.Notify:Event triggered : 203
                    2.2.2.Bulk deployment : 6839
                        2.2.2.1.Stop : 73
                        2.2.2.2.Perform delivery : 6765
                            2.2.2.2.1.Application Deployer : 6615
                    2.2.3.Notify:Event performed : 9
                2.3.Post process : 10
                    2.3.1.Starting : 9
]      [Error: com.sap.engine.services.tc~bl~deploy~api Thread[Worker-444,5,main]]
[#6]: Deployment Items status: [
----- Sorted Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
----- Deployment Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
         -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
        Time statistics( ms ):
            1.Check version:XXXXXXX.com_home~chgemail : 4
            2.validate : -1
                2.1.Resolve dependencies : 3
                2.2.deployment : 7055
                    2.2.1.Notify:Event triggered : 203
                    2.2.2.Bulk deployment : 6839
                        2.2.2.1.Stop : 73
                        2.2.2.2.Perform delivery : 6765
                            2.2.2.2.1.Application Deployer : 6615
                    2.2.3.Notify:Event performed : 9
                2.3.Post process : 10
                    2.3.1.Starting : 9
]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog Thread[Worker-444,5,main]]
[#6]: Deployment Items status: [
----- Sorted Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
----- Deployment Items -----
    1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
        Deploy status is 'Aborted'
        Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
         -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
        SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
        Time statistics( ms ):
            1.Check version:XXXXXXX.com_home~chgemail : 4
            2.validate : -1
                2.1.Resolve dependencies : 3
                2.2.deployment : 7055
                    2.2.1.Notify:Event triggered : 203
                    2.2.2.Bulk deployment : 6839
                        2.2.2.1.Stop : 73
                        2.2.2.2.Perform delivery : 6765
                            2.2.2.2.1.Application Deployer : 6615
                    2.2.3.Notify:Event performed : 9
                2.3.Post process : 10
                    2.3.1.Starting : 9
]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog Thread[Worker-444,5,main]]
Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api Thread[Worker-444,5,main]]
Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api Thread[Worker-444,5,main]]
[#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog Thread[Worker-444,5,main]]
[#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog Thread[Worker-444,5,main]]

C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear
can you find this ear in your local drive?

Web Dynpro-layout preview-Error-IE cannot display-service in SICF activated

Hello,
By starting a view in web dynpro framework, i have the error in tab layout "page cannot be displayed" from IE.
Before i make the change in the DNS and system32/../etc, the layout was displayed, but the web dynpro application cannot be started.
Now after those configurations and activation of services in SICF, i can start the web application only with firefox and not internet exploer, and, that internet explorer is preconfigured for the layout preview, i recieve all times the eror "cannot display" when i start a view in the layout tab.
1. How can i change settings so that view can be displayed in layout after i actived the (hope the suitables i.e. view designer) services in SICF - Default_host...
2. Is it possible to change IE to firefox as main browser for layout tab.
Note: For virtual domain i
1. add dns "domain.com" in the DNS
2. add in system32/etc/host file to "127.0.0.1 localhost", "10.10.0.10 sysserv.domain.com"
3. and trough tr. rz10 in the instance profil input the icm/.... ....domain.com
Through this three steps i could get the web dynpro application started,
but from the other side, the layout preview do not display the view again
and just send error the message: "THIS PROGRAM CANNOT DISPLAY THE WEBPAGE"
Many thanks for helping
arnaud
Edited by: Arnaud on Jul 15, 2010 4:36 PM
Edited by: Arnaud on Jul 15, 2010 8:31 PM

Hi,
The string is not correctly formed ( a quote and a concatenation ) :
Your url :
v_url:=nvl(v_rep_port,'http://'||v_rep_HOST ||':'||v_rep_port||')||'/reports/rwservlet/getjobid'||substr(v_rep,instr(v_rep,'_',-1)+1)||'?'||'server='||v_rep_svr;
The Correction :
v_url:=nvl(v_rep_port,'http://'||v_rep_HOST ||':'||v_rep_port)||'/reports/rwservlet/getjobid'||substr(v_rep,instr(v_rep,'_',-1)+1)||'?'||'server='||v_rep_svr;
Hope it helps
Mohamed Dadi

Activating Web Dynpro DC fails

Similar Messages

Maybe you are looking for