on 04-12-2006 5:29 PM
Hello All,
I'm running into problem running ESS Web Dynpro application via SAP Portal.
Current set-up is:
-SAP NetWeaver Enterprise Portal 6 SP9
-WAS Java 6.40 SP9
The SLD is configured and I've maintained the JCo connection mentioned in documentation. I've tested the connections for both meta data and the data itself. The connection work fine. The portal has been configured includes creating system in landscape etc. The problem is when I try and run the Web Dynpro in portal I get the following error:
Any ideas anyone?
********************************************************
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
-
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC sap.com/pcui_gp~xssutils:
SapDictionaryGenerationCore: 6.4015.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:25:03[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:09:40[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:00:16[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4015.00.0000.20051027104208.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:50:49[UTC], changelist=373971, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4015.00.0000.20051027104208.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:50:49[UTC], changelist=373971, host=PWDFM026)
SapGenerationFrameworkCore: 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-08:19:59:29[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4015.00.0000.20051027104504.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:34:33[UTC], changelist=373977, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:03:41[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:00:24[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4015.00.0000.20051027104504.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:35:04[UTC], changelist=373977, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4015.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:25:15[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/pcui_gp~xssfpm:
SapDictionaryGenerationCore: 6.4015.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:25:03[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:09:40[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:00:16[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4015.00.0000.20051027104208.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:50:49[UTC], changelist=373971, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4015.00.0000.20051027104208.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:50:49[UTC], changelist=373971, host=PWDFM026)
SapGenerationFrameworkCore: 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-08:19:59:29[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4015.00.0000.20051027104504.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:34:33[UTC], changelist=373977, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:03:41[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-08:20:00:24[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4015.00.0000.20051027104504.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:35:04[UTC], changelist=373977, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4015.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-11-06:21:25:15[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
-
Error stacktrace:
java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/api/IWDEventId
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructors(Class.java:865)
at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:68)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:38)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:775)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:329)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:352)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
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.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
You try to run applications built with SP14/15 on an engine with SP9. This will not work.
Armin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The general rule is that you cannot run a Web Dynpro application build with a NWDS that has a newer version than the Web AS.
That's because the newer NWDS may generate code that uses runtime features not supported by the older Web AS.
In your example, there is a new interface IWDEventId that is not known to the SP9 Web AS.
Armin
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.