"Failed to process the request."

[Former Member]

We developed the FlightList WebDynpro Application which are going to pick the Bapi data from R/3 and display it on browser.

We specified the R/3 System in EP SLD, and created new Logical system (for JCo Connection)pointing to the R/3 system in WebDynpro Content Administration.

When we are running the Webdynpro Application we are getting the following error in the browser

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.1; SV1), 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 local/FlightListProject:

No information available

Web Dynpro code generators of DC sap.com/tc_wddispwda:

No information available

Web Dynpro code generators of DC sap.com/tc_wdcorecomp:

No information available

J2EE Engine:

6.40 patchlevel 87289.311

Java VM:

Java HotSpot(TM) Server VM, version: 1.4.2_08-b03, vendor: Sun Microsystems Inc.

Operating system:

Windows 2003, version: 5.2, architecture: x86

-

---

Error stacktrace:

java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Node.getParentElement()Lcom/sap/tc/webdynpro/progmodel/context/NodeElement;

at com.sap.demo.flightlist.wdp.InternalFlightListComponent$ReturnNode.doSupplyElements(InternalFlightListComponent.java:819)

at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:460)

at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:424)

at com.sap.tc.webdynpro.progmodel.context.Node.createMappedElementList(Node.java:552)

at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:447)

at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:424)

at com.sap.tc.webdynpro.progmodel.context.Node.validate(Node.java:647)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.validate(DataContainer.java:564)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.validateDataContainer(ClientComponent.java:599)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.retrieveData(AbstractClient.java:208)

at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.retrieveData(HtmlClient.java:161)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:409)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)

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.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: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)

[Former Member · Accepted solution]

Hi Chitti,

What is your NWDS and WAS version?

NWDS version should be equal or less than the WAS version.

Regards,

Bhavik

[Former Member · Accepted solution]

Server has Web Dynpro SP9, NWDS must not be newer.

Armin

[Former Member · Accepted solution]

NWDS is SP3 and Server is SP9.

what can be other cause for this error.

[Former Member · Accepted solution]

If this is the case, then there would have been an incompatible change between SP3 and SP9.

In any case, upgrading the NWDS to SP9 will fix this.

Armin

[Former Member · Accepted solution]

We have upgraded the NWDS to SP9. Now the error has changed. Now the error is as follows.

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.1; SV1), 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 local/FlightListProject:

SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)

SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)

SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:55:01[UTC], changelist=290362, host=PWDFM026)

SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:55:01[UTC], changelist=290362, host=PWDFM026)

SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)

SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)

SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)

SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)

SapDictionaryGenerationTemplates: (unknown)

Web Dynpro code generators of DC sap.com/tc_wddispwda:

No information available

Web Dynpro code generators of DC sap.com/tc_wdcorecomp:

No information available

J2EE Engine:

6.40 patchlevel 87289.311

Java VM:

Java HotSpot(TM) Server VM, version: 1.4.2_08-b03, vendor: Sun Microsystems Inc.

Operating system:

Windows 2003, version: 5.2, architecture: x86

-

---

Error stacktrace:

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.demo.flightlist.model.types.Bapimaxrow could not be loaded: com.sap.dictionary.runtime.DdException:

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)

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.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: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)

Caused by: com.sap.dictionary.runtime.DdException:

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)

at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)

at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)

at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)

at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)

at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)

at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)

at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)

... 31 more

[Former Member · Accepted solution]

Hi Chitti,

Have you configured JCO for your webdynpro application in Content administrator?

If not then look at the following link for configuring JCO:

If you have already configured then test that connection from content administrator.

If it gives success, then rebuild your project and then deploy on the server.

Regards,

Bhavik

[Former Member · Accepted solution]

we are not able to reach the link specified by you. can you tell me where it was specified in SDN. can you reply us with the steps.

thanks in advance

[Former Member · Accepted solution]

Hi Chitti,

1. Open visual administrator at <drive>:/usr/sap/<system id>/jc<instance number>/j2ee/admin/go.bat.

2. Select server->services->SLD data supplier.

3. Choose CIM Content setting tab.

4. Give server information and login information.

5. Save data.

6. test connection.

7. Open webdynpro visual content from link http://<server>:<port>/webdynpro/welcome

8. Goto create JCO destinations

9. first create destination for model data.

10. Second, create destination for metadata.

11. Test both connections by clicking test button.

Regards,

Bhavik

reward points if answer was helpful.

[Former Member · Accepted solution]

When testing the JCo connection for Metadata , it is giving the following error

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=dqt GROUP=PUBLIC R3NAME=DQT MSSERV=sapmsDQT PCS=1 ERROR service '?' unknown TIME Thu Oct 27 18:54:36 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1

[Former Member · Accepted solution]

You haven't defined the message server as a service in the services file.

As a side note generating multiple postings for a single issue makes if very difficult for others to find solutions based on this, unless you go back and update all three of your threads with the answer you get.

[Former Member · Accepted solution]

Hi Chitti,

Restart your J2ee server.

Regards,

Bhavik

[Former Member · Accepted solution]

sapmsDQT 3600/tcp

Here DQT means my SAP Server. Do I need to add this entry in the SAP Server Services.ini file (OR)

Add this entry into my Portal Server where my SAP J2ee Engine is running. (DQT & Portal Servers are different machines)

[Former Member · Accepted solution]

we are able to create the JCo connections pointing to SAP R/3 server in WEBDYNPRO Content Administrator. We are getting the entries stored in SLD of Portal Server.

The messages are : JCo Connection are created successfully in SLD. but, JCo Connections are not started in WebDynpro Content Administrator(Jco connections are still in RED color).

what to do to make it up?

[Former Member · Accepted solution]

Hi Chitti,

You said that you got message saying "JCo Connection are created successfully". Means you should get green symbol against your JCO connections in Visual administrator.

Have you tested those connections?

Regards,

Bhavik