Running a WD-Appl. results in 500 Internal Server Error

[Former Member]

Dear all,

I installed both JAVA and ABAP stack (Sneak preview 6.40 SP15) on one box.

In the NSP I created a Web Service via SE37 using an existing RFC function module of my own. Then I released my Web Service for SOAP Runtime via WSCONFIG.

Next I checked the WSDL document and run a test via WSADMIN. On the right side I can see all retrieved data in a tree. Congratulation!

Next I created a Web Dynpro Project in the NW DevStudio that uses my Web Service:

- the model using my WSDL from above and

- context and model binding

- a view showing a table and a pushbutton .

Eerything went fine ... saveing-deploying-running ...

A html-page appears, I see my empty table and a shiny button ... I exspect that the Web Service Function Module will be triggered and the table shows me some entries, but instead, when I push the button, I get an error message: "500 Internal Server Error

Failed to process request. Please contact your system administrator. " What did go wrong? Who can help me?

[Former Member]

Can you please post the stacktrace?

Armin

[Former Member]

Hello Armin,

thank you for getting envolved ... I'm a beginner in the JAVA world. I guess you need the req_resp.trc file.

Looking forward to hear again! Bye

[Former Member]

Normally, you get the stacktrace in the 500 error page of the browser. Click the "more..." link.

If not, you have to look at the logfile of your J2EE engine.

Armin

[Former Member]

Good evening,

maybe some more info about my system:

- both stacks are running (all traffic lights are green)

- the function module sends 5 fields per line, but in the

View of my WebDynpro I included only 4, excluded field

MANDT

- Web-Browser is running with lowest security level

- here are som logfile info: Thank you Armin

I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system

server.1.log

#1.5#02004C4F4F500061000000410000042800040CFC59A74859#1140177882312#/System/Server/WebRequests#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####940e13809fad11daba2502004c4f4f50#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#

#1.5#02004C4F4F50006B000000110000042800040D00A0D24CEF#1140196256171#/System/Server/SLDService#sap.com/tc_wddispwda#com.sap.sldserv.SldApplicationService#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Warning#1#com.sap.sldserv.SldApplicationService#Plain###Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.#

#1.5#02004C4F4F50006B000000140000042800040D00A0D27772#1140196256187#/System/Server/SLDService#sap.com/tc_wddispwda#com.sap.sldserv.SldApplicationService#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Warning#1#com.sap.sldserv.SldApplicationService#Plain###Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.#

#1.5#02004C4F4F500012000000010000042800040D00A0D97B46#1140196256640#/System/Server##com.sap.engine.services.deploy######5c0478009fd811da852e02004c4f4f50#SAPEngine_System_Thread[impl:5]_50##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewsys_mngt~wd finished successfully on server 23436050#

#1.5#02004C4F4F500012000000020000042800040D00A0D97BBE#1140196256640#/System/Server##com.sap.engine.services.deploy######5c0478009fd811da852e02004c4f4f50#SAPEngine_System_Thread[impl:5]_50##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewsys_mngt~wd finished on current cluster node for 47 ms.#

#1.5#02004C4F4F500002000000010000042800040D00A21BB95A#1140196277765#/System/Server##com.sap.engine.services.deploy######689be3509fd811dabf2402004c4f4f50#SAPEngine_System_Thread[impl:5]_34##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewmonitoring~wd finished successfully on server 23436050#

#1.5#02004C4F4F500002000000020000042800040D00A21BB9D8#1140196277765#/System/Server##com.sap.engine.services.deploy######689be3509fd811dabf2402004c4f4f50#SAPEngine_System_Thread[impl:5]_34##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewmonitoring~wd finished on current cluster node for 31 ms.#

#1.5#02004C4F4F500030000000010000042800040D00A3684B2F#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmlv~client_ui finished successfully on server 23436050#

#1.5#02004C4F4F500030000000020000042800040D00A3684BA9#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmlv~client_ui finished on current cluster node for 47 ms.#

#1.5#02004C4F4F500030000000030000042800040D00A3685B75#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_lvwd finished successfully on server 23436050#

#1.5#02004C4F4F500030000000040000042800040D00A3685BEE#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_lvwd finished on current cluster node for 62 ms.#

#1.5#02004C4F4F5006BD000000000000042800040D00B2D311C2#1140196558250#/System/Server##com.sap.engine.services.deploy######0fca80a09fd911da8f4b02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewconfig~wd finished successfully on server 23436050#

#1.5#02004C4F4F5006BD000000010000042800040D00B2D3123F#1140196558250#/System/Server##com.sap.engine.services.deploy######0fca80a09fd911da8f4b02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewconfig~wd finished on current cluster node for 32 ms.#

#1.5#02004C4F4F50003F000000010000042800040D00B4256808#1140196580421#/System/Server##com.sap.engine.services.deploy######1d0187509fd911da918902004c4f4f50#SAPEngine_System_Thread[impl:5]_40##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_{log_config}wd finished successfully on server 23436050#

#1.5#02004C4F4F50003F000000020000042800040D00B4256882#1140196580421#/System/Server##com.sap.engine.services.deploy######1d0187509fd911da918902004c4f4f50#SAPEngine_System_Thread[impl:5]_40##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_{log_config}wd finished on current cluster node for 46 ms.#

#1.5#02004C4F4F500025000000010000042800040D00DEFE7F57#1140197299343#/System/Server##com.sap.engine.services.deploy######c98451f09fda11dacf5d02004c4f4f50#SAPEngine_System_Thread[impl:5]_75##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewdebug~wd finished successfully on server 23436050#

#1.5#02004C4F4F500025000000020000042800040D00DEFE7FD1#1140197299343#/System/Server##com.sap.engine.services.deploy######c98451f09fda11dacf5d02004c4f4f50#SAPEngine_System_Thread[impl:5]_75##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewdebug~wd finished on current cluster node for 15 ms.#

#1.5#02004C4F4F500029000000010000042800040D00F460D8F4#1140197658015#/System/Server##com.sap.engine.services.deploy######9f4d52f09fdb11dac04c02004c4f4f50#SAPEngine_System_Thread[impl:5]_83##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewanalysis~wd finished successfully on server 23436050#

#1.5#02004C4F4F500029000000020000042800040D00F460D978#1140197658015#/System/Server##com.sap.engine.services.deploy######9f4d52f09fdb11dac04c02004c4f4f50#SAPEngine_System_Thread[impl:5]_83##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewanalysis~wd finished on current cluster node for 47 ms.#

#1.5#02004C4F4F50003E000000030000042800040D00F5660BBF#1140197675140#/System/Server##com.sap.engine.services.deploy######a98264409fdb11daa59302004c4f4f50#OrderedChannel for service##0#0#Info#1#com.sap.engine.services.deploy#Plain### Operation startApp over application sap.com/tc_lmwebadmin_overviewperform~wd finished successfully on server 23436050# #1.5#02004C4F4F50003E000000040000042800040D00F5660C39#1140197675140#/System/Server##com.sap.engine.services.deploy######a98264409fdb11daa59302004c4f4f50#OrderedChannel for service##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewperform~wd finished on current cluster node for 62 ms.#

#1.5#02004C4F4F5000200000000B0000042800040D00F597B551#1140197678390#/System/Server##com.sap.engine.services.deploy######ab724d609fdb11dac12102004c4f4f50#SAPEngine_System_Thread[impl:5]_97##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_{session_trace}wd finished successfully on server 23436050#

#1.5#02004C4F4F5000200000000C0000042800040D00F597B5CA#1140197678390#/System/Server##com.sap.engine.services.deploy######ab724d609fdb11dac12102004c4f4f50#SAPEngine_System_Thread[impl:5]_97##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_{session_trace}wd finished on current cluster node for 47 ms.#

#1.5#02004C4F4F500041000000020000042800040D00F809240B#1140197719375#/System/Server##com.sap.engine.services.deploy######c3e01df09fdb11da90cd02004c4f4f50#SAPEngine_System_Thread[impl:5]_71##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp over application sap.com/tc_lmwebadmin_overviewconf~wd finished successfully on server 23436050#

#1.5#02004C4F4F500041000000030000042800040D00F8092486#1140197719375#/System/Server##com.sap.engine.services.deploy######c3e01df09fdb11da90cd02004c4f4f50#SAPEngine_System_Thread[impl:5]_71##0#0#Info#1#com.sap.engine.services.deploy#Plain###

Operation startApp on application sap.com/tc_lmwebadmin_overviewconf~wd finished on current cluster node for 32 ms.#

#1.5#02004C4F4F50002D0000000B0000042800040D01BC3F1359#1140201011218#/System/Server/SLDService##com.sap.sldserv.SldServerFrame.doCollect######664177909fe311da83fb02004c4f4f50#SAPEngine_System_Thread[impl:5]_57##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###SLD data collector run failed: Unable to open connection to host "localhost:50000". The host is down or unavailable..#

#1.5#02004C4F4F50002D0000000C0000042800040D01BC3F1446#1140201011218#/System/Server/SLDService##com.sap.sldserv.SldServerFrame######664177909fe311da83fb02004c4f4f50#SAPEngine_System_Thread[impl:5]_57##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###Failed to collect SLD data. Unable to open connection to host "localhost:50000". The host is down or unavailable..#

#1.5#02004C4F4F500062000000250000042800040D02694FB4F4#1140203914796#/System/Server/WebRequests#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: java.lang.NoSuchFieldError: _typeRegistry

Exception id: [02004C4F4F500062000000240000042800040D02694FB344]#

#1.5#02004C4F4F500062000000270000042800040D02694FBDA8#1140203914796#/System/Server/WebRequests#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#

I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system

userinterface.0.log

#1.5#02004C4F4F500058000000180000042800040CFC451E5B5B#1140177537984#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c6d43c009fac11daa11602004c4f4f50#SAPEngine_Application_Thread[impl:3]_20##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 9fbf1dd19faa11da982502004c4f4f50does not contain ApplicationWindow with Id Id9fbf1dd19faa11da982502004c4f4f501!#

#1.5#02004C4F4F50006C0000000C0000042800040CFC4520D522#1140177538156#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c6ee7ac09fac11da96ec02004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 5aaa43309fac11daa9e302004c4f4f50does not contain ApplicationWindow with Id Id5aaa43309fac11daa9e302004c4f4f502!#

#1.5#02004C4F4F50005B0000000D0000042800040CFC557AD42C#1140177812281#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Guest#0####6a5031909fad11da952f02004c4f4f50#ID\#(J2EE23436000)ID1437660650DB21061510417884802850End.6a5031919fad11daa4e302004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID1437660650DB21061510417884802850End#de# #1.5#02004C4F4F5000610000003C0000042800040CFC59A72A98#1140177882296#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager.handleThrowable#Guest#0####940e13809fad11daba2502004c4f4f50#ID\#(J2EE23436000)ID1437660650DB21061510417884802850End.6a5031919fad11daa4e302004c4f4f50##0#0#Error#1#/System/UserInterface#Plain###Exception(java.lang.NoSuchFieldError: _typeRegistry) during processing a Web Dynpro Application.# #1.5#02004C4F4F500070000000170000042800040CFC5E58E911#1140177961062#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c300d0609fad11daa29302004c4f4f50#SAPEngine_Application_Thread[impl:3]_17##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 6a5031919fad11daa4e302004c4f4f50does not contain ApplicationWindow with Id Id6a5031919fad11daa4e302004c4f4f503!# #1.5#02004C4F4F50006B0000000E0000042800040D009AD602EE#1140196155750#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID1860686650DB20022690890746729240End#en# #1.5#02004C4F4F50006F000000130000042800040D02653B3545#1140203846359#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Guest#0####07d53d709fea11da9a6802004c4f4f50#ID\#(J2EE23436000)ID0131720150DB21013274501523920836End.07d7ae709fea11da844902004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID0131720150DB21013274501523920836End#de#

#1.5#02004C4F4F500062000000220000042800040D02694F9F64#1140203914796#/System/UserInterface#sap.com/tc_wddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager.handleThrowable#Guest#0####30a256c09fea11dac94a02004c4f4f50#ID\#(J2EE23436000)ID0131720150DB21013274501523920836End.07d7ae709fea11da844902004c4f4f50##0#0#Error#1#/System/UserInterface#Plain###Exception(java.lang.NoSuchFieldError: _typeRegistry) during processing a Web Dynpro Application.#

I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system\httpaccess

responses.0.trc

[Feb 17, 2006 8:14:52 PM ] - 127.0.0.1 : GET /webdynpro/dispatcher/sap.com/tc_lmwebadmin_mainframewd/WebAdminApp?sap-wd-cltwndid=1fd5d2709fd811da919a02004c4f4f50&sap-wd-appwndid=Id1fd5d2709fd811da919a02004c4f4f504&sap-sessioncmd=unload HTTP/1.1 500 2117

[Feb 17, 2006 8:17:26 PM ] - 169.254.25.129 : GET /webdynpro/dispatcher/local/MyWDP/MyWDA?SAPtestId=4 HTTP/1.1 200 3221

[Feb 17, 2006 8:18:34 PM ] - 169.254.25.129 : POST /webdynpro/dispatcher/local/MyWDP/MyWDA?SAPtestId=4 HTTP/1.1 500 720

I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system\webcontainer

requests.0.trc

The error is: java.lang.NoSuchFieldError: _typeRegistry

Exception id: [02004C4F4F500062000000240000042800040D02694FB344]#

#1.5#02004C4F4F500062000000270000042800040D02694FBDA8#1140203914796#/System/Server/WebRequests#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#

[Former Member]

Can you open your logfile using the logviewer and check for any exceptions related to your application?

See http://help.sap.com/saphelp_nw04/helpdata/en/49/5b180efa5f44a980ffd73393140cf0/frameset.htm

Armin

[Former Member]

Hello Armin,

using nice tool (logviewer.bat) I searched for:

- project name MyWDP

- application MyWDA

- context ZgetMatWSD

- function module ZWDMATDATA

I found only hints for MyWDP and MyWDA

Thank you, bye

responses.0.trc

Message : #1.5#02004C4F4F50006F0000001B00000C4800040D0DE31CDB66#1140261480328#/System/HttpAccess/

Access##com.sap.engine.services.httpserver.server.Log#Guest#0####385aff80a07011daba0502004c4f4f50#

SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#com.sap.engine.services.httpserver.server.Log#

Plain###169.254.25.129 : GET /webdynpro/dispatcher/local/<b><u>MyWDP/MyWDA</u></b>?SAPtestId=0&sap-wd-

cltwndid=22e36480a07011dac8e202004c4f4f50&sap-wd-appwndid=Id22e36480a07011dac8e202004c4f4f500&sap-sessioncmd=

unload HTTP/1.1 500 2087#

Datasource : 1140263092578:I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system\httpaccess\responses.0.trc

requests.0.trc

Date , Time , Message , Severity , Category , Location , Application , User

02/18/2006 , 12:17:48:578 , Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null , Warning , /System/Server/WebRequests , com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl , sap.com/tc_wddispwda , Guest

02/18/2006 , 12:17:48:578 , Processing HTTP request to servlet [dispatcher] finished with error.

The error is: java.lang.NoSuchFieldError: _typeRegistry

Exception id: [02004C4F4F50005F0000002800000C4800040D0DE31CDB66] , Error , /System/Server/WebRequests , com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl , sap.com/tc_wddispwda , Guest

02/18/2006 , 12:17:21:953 , <b>Operation startApp on application local/MyWDP finished</b> on current cluster node for 16 ms. , Info , /System/Server , com.sap.engine.services.deploy , ,

02/18/2006 , 12:17:21:953 , <b>Operation startApp over application local/MyWDP finished successfully</b> on server 23436050 , Info , /System/Server , com.sap.engine.services.deploy , ,

Cannot send an HTTP error response [500 Application error occurred during request processing.

(details: java.lang.NoSuchFieldError: _typeRegistry)].

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:

<b>An attempt to write after the stream had been closed.null</b>

Processing HTTP request to servlet [dispatcher] finished with error.

<b>The error is: java.lang.NoSuchFieldError: _typeRegistry</b>

[Former Member]

A NoSuchField error indicates some kind of version mismatch. What is the Web Dynpro version in your NetWeaver Developer Studio and what is the version on the J2EE server?

Armin

[Former Member]

Hello Armin,

I'm not sure if this is the info you asked for:

NW developer studio --> WebDynpro Version 2.0

J2EE --> sap.com tc/wd/webdynpro 6.40 (6.4015.00.0000.20051004171353.0000)

I'll download developerstudio again and reinstall.

If now result then I'll reinstall JAVA and ABAP stacks

otherway round, first JAVA and then ABAP.

Thank you, bye

[Former Member]

Are you using the NWDS with the same SP as SAP?