Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Adobe Forms render problem

We are implementing MSS at a customer and want to use the standard HCM

Forms and Processes. If we execute the Java Web Dynpro that launch the

HCM Forms and Processes (sap.com/paasrprocst/com.sap.pa.asr.procst.appl.StartProcessForManager)

the PDF that is expected to render just don’t render. It is as if the PDF

component is hanging. The is how ever 1 PDF the renders but it is not a

interactive PDF(Request for Transfer (Enhanced)). All the other standard PDFs never appears. Every time this happens there is the same error in default trace file.

-


EXCEPTION]

#2#sap.com/pb/#com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'sap.com/pb' and application '' are not deployed on the server. Please check the used URL for typos.

at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:413)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:347)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:145)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

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

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

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(AccessController.java:215)

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: com.sap.tc.webdynpro.services.exceptions.WDIllegalArgumentException: The argument 'applicationName' is null.

at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getApplication(AbstractDeployableObject.java:138)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:411)

... 20 more

-


The component 'sap.com/pb' is deployed and the application 'PageBuilder' is running.

We tested on the following client software combinations:

Adobe Reader 8.1

xAcf_NW04s_SP14

Browser: IE7

Adobe Reader 8.0

xAcf_NW04s_SP14

Browser: IE6

We looked at all the following notes but not one of them identified the

problem we experience.

1021103

976913

894009

834573

894009

834573

905753

956074

944221

846712

736902

811342

994045

900493

925741

Former Member
Not what you were looking for? View more on this topic or Ask a question