Ugent :Code of Conduct Application in ESS fails...

[Former Member]

Hi,

In ESS1.0 ans SAP_ESS SP6 with EP 7.0 i am trying to run the Iview Code of Conduct Application.

I calls a scenario SECC in ECC 6.0(transaction QISRSCEnario)

I am getting the following error..

com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF

at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:396)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:887)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)

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

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)

at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)

at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)

at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:596)

at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:683)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/ess_{essforms/CodeOfConductApplication/}wd_key14_1163092016222/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=WID1163089584796&sap-ext-sid=Umxbx6540if8e70PODov8g%3D%3DhTQdeqlbbwq9lfKUWniqLg%3D%3D%2Fpcd%3Aportal_content%2Fcom.sap.pct%2Fevery_user%2Fcom.sap.pct.erp.ess.bp_folder%2Fcom.sap.pct.erp.ess.roles%2Fcom.sap.pct.erp.ess.employee_self_service%2Fcom.sap.pct.erp.ess.employee_self_service%2Fcom.sap.pct.erp.ess.area_corporate_info%2Fcom.sap.pct.erp.ess.codeofconductapplication%2Fsap.com%2Fess%7Eessforms%2FCodeOfConductApplication%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200608201842

at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:383)

... 46 more

Both the config checks in abap:

FP_PDF_test_00

and the config test through webservice:

host:port/AdobeDocumentservices/Config? are giving positive results of version information..

The ADSUSER in j2ee ume is having "no pass word check required" checked.

Pls do help me solve this issue and its very urgent. All valid answers will be rewarded..

Regards,

Ramesh

[Former Member]

Hi Ramesh,

To get to know if this an ADS Problem, try creating a Java WD Iview referring the application<b> IsrForm</b> with Application parameters of your scenario name and see the preview. If you get to see the same error, then I am sure, it would be some <b>ADS</b> Config problem. If you can see you Adobe form in the preview, then I think there is some problem with <i>SECC</i> scenario standard, in such case, raise an OSS Message.

Hope this is helpful.

Regards,

<b><i>Raja Sekhar</i></b>