on 03-17-2006 9:50 AM
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
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.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:834)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1238)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:279)
... 27 more
See full exception chain for details.
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 2.0.50727)
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.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-20:20:24:49[UTC], changelist=366934, host=PWDFM026)
J2EE Engine 6.40 patchlevel 98256.313
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
Other
Session Locale en_US
Time of Failure Sat Mar 18 15:01:39 IST 2006 (Java Time: 1142674299296)
Web Dynpro Code Generation Infos
local/TutWD_OnlineInteractiveForm
SapDictionaryGenerationCore 6.4014.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:08:16[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates (unknown)
SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:01:32[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:15:40[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:26[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:18[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:05:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:11:31[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)
SapWebDynproGenerationCore 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:16:08[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)
sap.com/tcwddispwda
No information available
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:483)
at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:185)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1154)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:402)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:279)
... 27 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:834)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1238)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
... 29 more
Chitti,
Check end-point URL of your web services.
Seems that this URL is invalid.
VS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure what your question is, but it looks to me like you are trying to generate an Interactive Form, because the error in the detailed stack is an Adobe document services (ADS) error - this one usually due to an unconfigured or inceoorectly configured ADS. Check the ADS Configuration Guide in the Service Marketplace, and make sure that yuo have made all the settings.
Kind regards,
Markus Meisl
SAP NetWeaver Product Management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.