NWDS problem

Hi all,
I am having problem with my NWDS . when i try to create archive for my application it is showing error . The error is "Project is not built due to Build Errors" . But there are no errors when i build the project.

Hi Krishna,
we have sometimes the same problems.
In some reasons this can help to find the error:
Remove the project from local workspace and than create newly the project from NWDS.
Now you should see where the project has the error.
Alternatively right-click on the Project -> Rebuild Project -> you will see in the Task View Errors

Similar Messages

NWDS : Problems during startup. Check the".log" file in "metadata" of your workspace.

Hi,
NWDS version : Version 7.0.17
I am unable to open NWDS.
While opening the NWDS i see an pop-up message saying below :
I have serached in forums and tried with the following steps :
1) Deleted .metadata file in Workspace, restarted my system. (Issues still persists)
2) Checked in Task manager if any instance is running Ex : "SAPIDE.exe"
In the Log file i see that there are few plugins missing as below :
!SESSION Dec 01, 2012 11:17:11.267 ---------------------------------------------
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -feature com.sap.java.ide - data E:\Workspace C:\Program Files\Java\jdk1.6.0_26\bin\javaw.exe
-Xmx512m
-Xms128m
-XX:PermSize=32m
-XX:MaxPermSize=128m
-DallUserDir='C:\Documents and Settings\All Users\Application Data'
-cp C:\Program Files\SAP\IDE\IDE70\eclipse\SapStartup.jar com.sap.ide.eclipse.startup.Main
-os win32
-ws win32
-arch x86
-feature com.sap.java.ide
-showsplash C:\Program Files\SAP\IDE\IDE70\eclipse\SapIde.exe -showsplash 600
- data E:\Workspace -data E:\Workspace -install file:C:/Program Files/SAP/IDE/IDE70/eclipse/
!ENTRY org.eclipse.core.runtime 2 1 Dec 01, 2012 11:17:11.283
!MESSAGE Problems encountered loading the plug-in registry.
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Dec 01, 2012 11:17:11.283
!MESSAGE Plug-in "com.sap.tc.jtools.jlin.core" was disabled due to missing or disabled prerequisite plug-in "com.sap.tc.jtools.util".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Dec 01, 2012 11:17:11.283
!MESSAGE Plug-in "com.sap.tc.jtools.jlin.java" was disabled due to missing or disabled prerequisite plug-in "com.sap.tc.jtools.jlin.core".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Dec 01, 2012 11:17:11.283
!MESSAGE Unable to satisfy prerequisite constraint from "com.sap.tc.jtools.jlin.devel" to "com.sap.tc.jtools.jlin.core".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Dec 01, 2012 11:17:11.283
!MESSAGE Unable to satisfy prerequisite constraint from "com.sap.tc.jtools.jlin.ui" to "com.sap.tc.jtools.jlin.core".
!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Dec 01, 2012 11:17:19.885
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.NoClassDefFoundError: org/eclipse/ui/IStartup
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClass(DelegatingURLClassLoader.java:922)
at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java:166)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java:485)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:882)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.core.internal.plugins.PluginDescriptor.internalDoPluginActivation(PluginDescriptor.java:700)
at org.eclipse.core.internal.plugins.PluginDescriptor.doPluginActivation(PluginDescriptor.java:188)
at org.eclipse.core.internal.plugins.PluginClassLoader.activatePlugin(PluginClassLoader.java:112)
at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java:185)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java:485)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:882)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:130)
at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:167)
at org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:103)
at org.eclipse.core.internal.runtime.InternalPlatform.loaderGetRunnable(InternalPlatform.java:578)
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:597)
at org.eclipse.core.internal.boot.InternalBootLoader.getRunnable(InternalBootLoader.java:471)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:854)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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:597)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: java.lang.ClassNotFoundException: org.eclipse.ui.IStartup
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:866)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 41 more
Any suggestions will be appreciated!
Best Regards,
KC

Have you tried this: http://help.sap.com/saphelp_nw04/helpdata/en/9d/eb813f0e614a18e10000000a114084/content.htm
Pass the VM as a argument. Make sure it is 32 bit, for NWDS 7.0 a JDK 1.4 should be used. Easiest way to try it out is to open the shell:
cmd
navigate to the directory of NWDS and enter:
SapIde.exe vm "C:\path\to\java\bin\javaw.exe"

Problem during startup of NWDS - Error while opening NWDS -

Hi,
iam unable to start up NWDS.problem during startup of NWDS
Error when double click the NWDS to open.
Error in .log file of workshop[--
!SESSION -
!ENTRY org.eclipse.core.launcher 4 0 Dec 03, 2007 15:59:04.226
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
     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:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: java.lang.reflect.InvocationTargetException
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     ... 7 more
Caused by: org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
     at org.eclipse.swt.SWT.error(SWT.java:2330)
     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:101)
     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1999)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1733)
     at org.eclipse.swt.widgets.Display.release(Display.java:1782)
     at org.eclipse.swt.graphics.Device.dispose(Device.java:212)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1390)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     ... 8 more

Hi nayab,
                 Ur workspace metadata seems to be corrupted. Go to ur workspace. rename .metadata folder & open the NWDS. It will not show ur previous configuration so u have to import the Development configuration again. In case ur any activity is open, it will come back when u import the Development Configuration.
regards
Sumit

NWDS - HTTPS - NWDI

Hi,
Is it possible to connect to "Development Infrastructure" over https protocol?
I've set URL to SLD (https://<host>:50001/), "ping server" button gives no result (not a success or error message, just nothing).
I've set DTR server URL (https://<host>:50001/dtr), login attempt gives no result, it stays not connected but no error message displayed.
Is there any documentation on configuring NWDI to work with https?
May be it's a nwds problem...

I've found some docs help on this issue:
[http://help.sap.com/saphelp_nw70/helpdata/en/4c/941f407b402402e10000000a1550b0/frameset.htm]
but still no result after those actions.
I have two versions of NWDS 7.2 an 7.0, 7.2 is able to connect to NWDI, but 7.0 isn't.
In this case I need 7.0 for development...
PS. When I use "http" as start of URL on development configuration pool page in NWDS preferences, it give some error description (HTTP error: Invalid begin of response [expected: 'HTTP', found: '(']), but with "https" it stops giving any error descriptions

JAXB 2.0 in the NWDS

Hi Folks,
I would like to use JAXB 2.0 to generate classes from an XSD file .
Unfortunately I get errors when import the Java package into NWDS - NWDS does not recognise the annotations.
I am using NWDS version 2.0.20. Is this an NWDS problem or perhaps a JRE versioning problem (JRE is 1.5). Have I missed something?
Help would be much appreciated.
Thanks
Dan

I think you must got an Error “unable to marshal type because it is missing an @XmlRootElement annotation]”
please refer to the link:
http://www.vineetmanohar.com/2009/09/jaxb-code-snippets-for-beginners/

NWDS in Win 7

Hi,
I have a query about the NWDS installation and working on Win7 (32bit). I can see the note 1566977.
Is NWDS problems under win7 OS is fixed now?
Kindly help on this.
Regards,
Rambabu

Hi Ram,
check this thread too:
NWDS not showing SAP specific Eclipse extensions
(this includes a note for clarification).
Further, the Product Availibility Matrix is indeed a bit misleading (we will soon make it more obvious).
The thing is that NWDS is supported on 64bit platforms, but the JDK has to be 32bit. So only JDK is supported (no JRE) and even if your platform is 64bit, JDK has to be 32bit.
See also the note:
#1566977 - NWDS on Windows 7
(http://service.sap.com/sap/support/notes/1566977)
Hope this helps!!
Thanks & Regards
Vijay

Problem with Mappings in the new Version of NWDS

Hello all,
i have a process which created in the NWDS (Version: SAP Enhancement Package 1 for SAP NetWeaver 7.1 SP00 PAT0000) checked in the CVS.
Now i have the process checked out of the CVS in the new Version of NWDS (Version: SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.1 SP01 PAT0003).
The process contains a automated activity and on the output mapping from the webservice is now n error. The Error: "Expected 'com.sap.dictionary.string,ns=.... Found list of 'char10,ns=..." I´ve changed nothing and the input mapping and the other mappings are all right. I checked out again the same process in the "old" Version of NWDS and it works fine.
Knows somebody how i can "import" n process from an older Version of NWDS into the new Version?
Kind regards,
Bastian

Hi Bastian,
The problem you are facing is a trivial problem. You need not worry about the importing the whole development component again. Rather your mapping error can be removed by changing the context in webdynpro perspective easily.
Your error is telling that the automated activity requires a string paramenter and what it has found is a list of parameters.
What this means is in the Webdynpro context, the mapping which you have done has problems.
The webservice input requires a singleton parameter. If you look into the mapping view, you will notice a single icon for the node which you are mapping.
And what you are sending is a list (not a singletion node)
If you see from the left side from where the parameters is coming in you will notice multiple icons (stack on top of each other) representing non singleton nodes ie cardinatlity is 0...n or 1..n)
So to remove the problem just go to component controller of the view and change the context setting
Colletion cardinality of 0..1 or 1..1 and selection cardinality to 0..1 or 1..1 of the node.
Thnks

Deployment Problems of Enterprise Application in NWDS 7.1

Hello Everyone, 
 
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. SUMMARY 
~~~~~~~~~~~~~~~~~~~ 
Successfully deployed: 0 
Deployed with warnings: 0 
Failed deployments: 1 
~~~~~~~~~~~~~~~~~~~ 
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. 
 
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear 
 Name:test~sgj_ent_app_test_three 
 Vendor:sap.com 
 Location:PDI_J2EETST1_D 
 Version:20100716152020 
 Deploy status:Aborted 
 Version:HIGHER 
 
 Description: 
 1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container. 
 
Exception: 
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
 at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
 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 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 ... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
 at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
 at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
 at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PM

Hi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya

Problem in deploying the application on NWDS

Hi,
I am getting a problem "Deployment aborted" when deploying a webdynpro application in NWDS sneak preview.When I looked at the log file says
Aborted: development component 'test'/'local'/'LOKAL'/'0.2007.08.09.13.30.27'/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Deployment exception : The deployment of at least one item aborted
Please let me know what is the problem

Hi,
Please try to open configtool> secure store> admin/password/J2E and re-type password in the value field down in the bottom, and click Add.
Save and re-start cluster-data, and then deploy the app again see if it works. This may help.
Regards,
-Napadol

Problem while deploying new logon screen par file via NWDS

hi
i have a problem with deploying .par files out of the NWDS.
i want to change the look of the logon screen in our EP Portal (SAP NetWeaver 2004s).
when i just import the (working one) par file into NWDS and deploy it without ANY changes i get then an error when trying to call the portal:
instead of the logonscreen i get some IView error (like IView: N/A).
if i just copy the par file, and put it back to the pcd, everything works fine.
my problem seems to be the "compiling/deploying" via NWDS.
any suggestions?
i followed the guide:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
i followed also the BLOG:
Modifying The Logon Par(or customising the Logon Screen)
and the help:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
thanks for your help.
markus

Markus,
If you import the par file using NWDS, most likely you wouldn't import the associated jar files (I think 2 jars) that are originally part of the par file. So, when you make changes and update your custom jar, it would lack the two jars and your application would fail. Try downloading the par file using System Administration -> Support -> PCD Administration -> Browse Deployment..
Save the jar file on desktop and then import it to NWDS.
Hope this helps,
Kiran

Problem with Local DCs View in NWDS 7.0

Hi!
I' ve got a problem with Local DCs view in NWDS: None of the standard-DCs (BI_MMR, BI_UDI, CAF a.s.o.) can be expanded and show their content. I already reinstalled IDE, but without success.
Has anybody got an idea?
Thanks a lot in advance!
Regards,
Thomas

Hi,
This is due to some files missed in Local development.
Let me know Are you able to see .confdef, .syncdb and buildvariant.config files under Local Developement.
If you are not able to see, UnInstall your NWDS, Remove Local developement under .dtc folder, then Re-Install NWDS.
Hope this will help you.
Thanks & Regards
Vasundhara

Problem with Local DCs View in NWDS

Hi!
I' ve got a problem with Local DCs view in NWDS: None of the standard-DCs (BI_MMR, BI_UDI, CAF a.s.o.) can be expanded and show their content. I already reinstalled IDE, but without success.
Has anybody got an idea?
Thanks a lot in advance!
Regards,
Thomas

Your setup might be incomplete: The SAR file extraction creates very long paths on your filesystem. If you do not extract to the rootfolder of disk, chances are the paths become too long and the installation exits, without any warning.
If this is not the cause of your problem, check if the .dcdef files for the local DCs (plugin com.sap.tc.ap if I'm correct) were copied during installation.

Problems with the examples in NWDS

Hi All,
Running the Welcome example project in NWDS i have the included error.
I have problems with other examples too.
I did all the step by step tutorials.
I have NWDS 2.0.3
 J2EE 6.40 SP15
 EP 2004
I am new in NWDS and i have not still successed to run any application.
What is wrong with my systems?
I did all the configurations start J2EE /sdm etc.
Do i have to install other versions? I read that maybe i have to install the same SP 15.
Please if anybody can help me .
Thanks,
Ari
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.sal.deployment.api.WDClassLoaderException: Classloader of 'local/Welcome' is null, even though application is started.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getClassLoader(DeployableObject.java:81)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:588)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
... 18 more
Ari

Thank you for your help,
I have NWDS 2.0.3 and Web AS 6.40 SP15 and EP 04.
How can i be sure if are compatible? Maybe i have to install NWDS SP15?
I did "Rebuild" and then "Deploy new archive and run" Deploying i was asking for the sdm password , then the application opened in a new browser and we can see this message below.
The Deploy Output View is empty. There is no eny successful deploy message.
I appreciate your help.
Thanks,
Ari
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Details...]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
 java.lang.InstantiationError: com.sap.tc.webdynpro.progmodel.context.NodeInfo
 at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:41)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 ... 27 more
See full exception chain for details.
Correction Hints
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
J2EE Engine No information available
Java VM Java HotSpot(TM) Server VM, version:1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Other
Session Locale en_US
Time of Failure Fri Jan 26 14:29:31 EET 2007 (Java Time: 1169814571353)
Web Dynpro Code Generation Infos
local/Welcome
No information available
sap.com/tcwddispwda
No information available
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.sap.examples.welcome.WelcomeComponent. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:38)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:776)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
 ... 26 more
Caused by: java.lang.InstantiationError: com.sap.tc.webdynpro.progmodel.context.NodeInfo
 at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:41)
 ... 31 more

Problem in exporting data to excel in nwds 7.3

Hi All,
I was using the following code for exporting data to excel in NWDS 7.3
private IWDCachedWebResource getCachedWebResource(byte[] file, String name,
WDWebResourceType type) {
IWDCachedWebResource cachedWebResource = null;
if (file != null) {
cachedWebResource = WDWebResource.getWebResource(file, type);
cachedWebResource.setResourceName(name);
return cachedWebResource;
I was getting the error in the following line cachedWebResource = WDWebResource.getWebResource(file, type); when I clicked the quick help it ststed the getWebResource method is depricated. Kindly provide some assistance on what is the new method in its place.
Thank you
Regards,
Preet Kaur

Hi Ganesh,
Thanks that worked fine, but when we go further we are facing problem ie
byte[] excelXMLFile;
IWDCachedWebResource cachedExcelResource = null;
String fileName = dataNode.getNodeInfo().getName() + ".xls";
try {
// create Excel 2003 XML data as a byte array for the given context node,
// attributes and headers
excelXMLFile = toExcel(dataNode, columnInfos).getBytes("UTF-8");
// create a cached Web Dynpro XLS resource for the given byte array
// and filename
cachedExcelResource = getCachedWebResource(
excelXMLFile, fileName, WDWebResourceType.XLS);
// Store URL and file name of cached Excel resource in context.
if (cachedExcelResource != null) {
wdContext.currentContextElement().setExcelFileURL(
cachedExcelResource.getURL());
wdContext.currentContextElement().setExcelFileName(
cachedExcelResource.getResourceName());
// Open popup window with a link to the cached Excel file Web resource.
openExcelLinkPopup();
} else {
wdComponentAPI.getMessageManager().reportException(
"Failed to create Excel file from table!", true);
} catch (UnsupportedEncodingException e) {
wdComponentAPI.getMessageManager().reportException(
e.getLocalizedMessage(), true);
} catch (WDURLException e) {
wdComponentAPI.getMessageManager().reportException(
e.getLocalizedMessage(), true);
The above bold lines also would need to be converted to inputstream, but not sure how to correct that
We are following the below pdf for the implementation.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/edc2f3c2-0401-0010-8898-acd5b6a94353?QuickLink=index&overridelayout=true
Thank you
Regards,
Jaspreet Kaur

Problems when deploying a WD-Project of NWDS to CE by using ESWorkpl.

Hello,
I am using a CE 7.1 Server. Now I wanted to develop a Demo App. as described in the Book "Java Programming with SAP NetWeaver", published by SAP Press. I have done everything exactly as described in the book, but If i deploy and run the App I get an internal Server Error. I am using the SR of the ES Workplace. The Destinations of HU2 are set. The Stacktrace is the following:
#1.5 #000C29FCB5CB001E000001DD000013A40090E803E0D0C020#1222942876187#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#2935##n.a.##c390f1808f9811ddab7c000c29fcb5cb#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]##0#0#Warning#1#/System/Server/Services/Deploy#Plain###JLinEE validation of application local/ReadPurchaseOrder returned result Messages for application "local/ReadPurchaseOrder" reported by JLinEE checks:
WARNINGS:
References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tc~je~webservices~api, sap.com/tc~wd~wslib~api, sap.com/tc~je~webservices~lib, sap.com/tc~wd~api] (described in the META-INF/application-j2ee-engine.xml)., file: ReadPurchaseOrder.ear, severity: warning
#1.5 #000C29FCB5CB001E00000207000013A40090E803E0D0C020#1222942876875#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#2935##n.a.##c390f1808f9811ddab7c000c29fcb5cb#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]##0#0#Warning##Plain###
Warning occurred on server 4078750 during update local/ReadPurchaseOrder : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tc~je~webservices~api, sap.com/tc~wd~wslib~api, sap.com/tc~je~webservices~lib, sap.com/tc~wd~api] (described in the META-INF/application-j2ee-engine.xml)., file: ReadPurchaseOrder.ear, column 0, line 0, severity: warning#
#1.5 #000C29FCB5CB001D0000012A000013A40090E803E0C734D7#1222942879406#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc~wd~dispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#mko#2098##n.a.##db4f2870905911ddbf69000c29fcb5cb#HTTP Worker [1]##0#0#Error##Java###Exception occured during processing of Web Dynpro application {0}. See exception stacktrace for details.
[EXCEPTION]
{1}#2# local/ReadPurchaseOrder/ReadPurchaseOrderApp#java.lang.UnsupportedClassVersionError: Bad version number in .class file
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:664)
 at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:198)
 at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:306)
 at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256)
 at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:363)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:242)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:62)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:78)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:487)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1228)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:150)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
 at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:75)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:233)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:647)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:225)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
 at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 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:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
#1.5 #000C29FCB5CB001D0000012C000013A40090E803E0C734D7#1222942879406#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc~wd~dispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#mko#2098##n.a.##db4f2870905911ddbf69000c29fcb5cb#HTTP Worker [1]##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application {0}. For details, check entry {1} in trace.#3# local/ReadPurchaseOrder/ReadPurchaseOrderApp#000C29FCB5CB001D0000012A000013A40090E803E0C734D7#com.sap.tc.webdynpro.sessionmanagement#
#1.5 #000C29FCB5CB0026000000CC000013A40090E803E0C740AC#1222942880750#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc~wd~dispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#mko#2098##n.a.##db4f2870905911ddbf69000c29fcb5cb#HTTP Worker [4]##0#0#Error##Java###Exception occured during processing of Web Dynpro application {0}. See exception stacktrace for details.
[EXCEPTION]
{1}#2# local/ReadPurchaseOrder/ReadPurchaseOrderApp#com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown during destruction of root component of application ApplicationIdentificationHandle(appName=local/ReadPurchaseOrder/com.sap.demo.readpurchaseorderapp.readpurchaseorderapp.ReadPurchaseOrderApp, appId=da8d80f2906b11dd823e000c29fcb5cb, clientWindowId=da8d80f1906b11dd869c000c29fcb5cb, clientSessionId=EiETMra5JX4Gu2lcZdumWYIuXWx3fJ28HAGePD4A_SAP). The causing exception is nested. RID=db61c0e1906b11dd8410000c29fcb5cb
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.destroy(ClientApplication.java:618)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDestroy(AbstractExecutionContextDispatcher.java:168)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppDestruction.doService(DispatchHandlerForAppDestruction.java:41)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
 at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDestroy(ExecutionContextDispatcher.java:128)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:87)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.destroy(ApplicationSession.java:322)
 at com.sap.tc.webdynpro.clientserver.session.ClientWindow.destroyApplicationSession(ClientWindow.java:251)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doDestroyApplication(ClientSession.java:903)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPostprocessing(ClientSession.java:751)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:242)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
 at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 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:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.NullPointerException
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.exit(ClientComponent.java:184)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.destroy(ClientApplication.java:616)
 ... 53 more
#1.5 #000C29FCB5CB0026000000CE000013A40090E803E0C740AC#1222942880750#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc~wd~dispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#mko#2098##n.a.##db4f2870905911ddbf69000c29fcb5cb#HTTP Worker [4]##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application {0}. For details, check entry {1} in trace.#3# local/ReadPurchaseOrder/ReadPurchaseOrderApp#000C29FCB5CB0026000000CC000013A40090E803E0C740AC#com.sap.tc.webdynpro.sessionmanagement#
Now I have no idea how to solve this problem. In detail I have no idea how to get the named references: sap.com/tcjewebservicesapi, sap.com/tcwdwslibapi, sap.com/tcjewebserviceslib, sap.com/tcwd~api. Can anyone help me?

HI,
Problem is wierd.
but you can try
As there is problem for getting refernce for
sap.com/tcjewebservicesapi, sap.com/tcwdwslibapi, sap.com/tcjewebserviceslib, sap.com/tcwd~api
you can add them as sharing references or service references in your project properties->web dynpro.
Just for info, you got an exception saying
java.lang.UnsupportedClassVersionError
what is JDK version of server and your NWDS CE 7.1.?

NWDS problem

Similar Messages

Maybe you are looking for