PDF Document Creation Exception

Former Member · ‎01-27-2008

Hi,

When creating a new requisition from the Portal system using MSS, we get the following error message. Our setup is we have a Portal system (ABAPJ2EE) & ECC6 (ABAPJ2EE) system source. The adobe forms all reside on the ECC6 system. In our case ADS has been fully configured on the PORTAL system and nothing done on the ECC ADS setup side (Should ADS also be setup on ECC systems as well). When I click on create requistion on the Portal the URL it generates is that of the portal so thats how I'm thinking the config on ECC for ADS is not required.

All the tests on the ADS configuration work as per the configureation guide:

(1) Credentials file imported

(2) HTTP connection created in J2EE engine and working

(3) All the ABAP connection test working with no error

- FP_PDF_TEST_00 - working

- FP_CHECK_DESTINATION....

- FP_TEST_00.....

(4) Frontend ACF file

Testing of the ADOBE form via trns SFP works as well in print preview with the form displayed: ISR_FORM_SRQ1 (Create simple requistion).

Yet I get the below errror when selection "Create new requistion" from MSS function in portal (ANy ideads how to fix trhis issue.)

*ERROR*

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

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.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/mss_recreq/RequisitionCreation/~wd_key51_1201471623451/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=DefaultExternal1201471608656&sap-ext-sid=6XWuNftjN_sLOEYf4WN3yA~~J_MlUTWCvJND0Q6plKBx_Q~~%2Fpcd%3Aportal_content%2Fcom.sap.pct%2Fline_manager%2Fcom.sap.pct.erp.mss.bp_folder%2Fcom.sap.pct.erp.mss.roles%2Fcom.sap.pct.erp.mss.manager_self_service%2Fcom.sap.pct.erp.mss.manager%2Foverview%2Fcom.sap.pct.erp.mss.team%2Frecruiting%2Fcom.sap.pct.erp.mss.requisition_request%2Fsap.com%2Fmss%7Erec%7Ereq%2FRequisitionCreation%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200708120253

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

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

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

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

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

... 41 more

See full exception chain for details.

Correction Hints

PDF Document Render Exception.

Please check the following:

Template file is not corrupted.

Data being passed is a vaild XML.

You have configured the web service client proxy properly.

Adobe Document Service (ADS) is configured properly (follow the configuration guide available at SAP service market place to check with all the supported configuration options).

If the problem still persists, report it to us. We need the following information to investigate the problem further:

Click here to download the error pdf that has been generated instead of the actual pdf. This is an important document to analyse the problem further.

Follow the steps below to get the system information where web dynpro is running:

Go to : http://host:port/sap/monitoring/SystemInfo

Log on as Administrator user.

Click on link all components... there. This will take you to the system information page that lists the version information of all the componenets installaed on your server.

Save this entire page (containing the version information of all the componenets installed on your server)

Follow SAP notes mentioned below to get the trace files for web dynpro and ADS. Then run your application again. Get the latest updated trace files from the server. If webdynpro and ADS are not running on the same server, then you need to turn on the tracer for the respective servers:

#742674 to turn on the web dynpro trace on the server where web dynpro is running.

#846610 to turn on the ADS trace on the server where ADS is running.

Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)

Version null

DOM version null

Client Type msie7

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: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat Oct 13 00:41:54 EST 2007

J2EE Engine 7.00 patchlevel 109044.44

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

Operating system Linux, version: 2.6.16.13-4-bigsmp, architecture: i386

Session & Other

Session Locale en_AU

Time of Failure Mon Jan 28 09:07:03 EST 2008 (Java Time: 1201471623478)

Web Dynpro Code Generation Infos

sap.com/pb

SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)

SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)

SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)

SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)

SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)

SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)

SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)

SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)

SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)

SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)

SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)

sap.com/tc_wddispwda

No information available null

sap.com/pb_api