Common Problems with SAP Interactive Forms by Adobe - PART II

Always Refer to the original Article at Common problems with SAP Interactive Forms by Adobe - PART I - If you have not read it yet please read it! Part I contained the JAVA side common configuration errors, now in part II we will check the issues wich are connected to ABAP side or occure in a later stage of the configuration.
P5. The destination Service
Sympthoms- The ABAP Test Program: FP_PDF_TEST_00 returns the Version information of the ADS but the Report: FP_TEST_00 fails with the Exception: FPRUNX001- In the default trace you see enty like: com.adobe.ads.destination.DestinationException:
Destination exception during destination lookup: FP_ICF_DATA_
- In the default trace you see enty like: File Not Found while reading Dest URL:
http://:/sap/bc/fp/form/layout/.XDP?fp-language=
Possible cause:- Please check SAP note: #915399 what describes how the destination Servce has to be created / maintained. - When you maitain the URL to the FP_ICF_DATA_ destination, quite often the JAVA port is used instead of the ABAP. Make sure you use the hostname and port what you see in transaction: SMICM on the ABAP side! - If you do not enter specific client, the logon will take place in the default client on the ABAP side. Please make sure the ADS_Agent user exists in the client where the JAVA stack is trying to log on. - Make sure the Service: default_host/sap/bc/fp is activated in Tr. SICF on the ABAP Stack. - Make sure in Transaction SU01, that the ADS_Agent user (-or the user you have defined in the Visual Administrator for the destination -) is: - not locked - type: System - assigned to the role: SAP_BC_FP_ICF
P6. Printer Devices
Sympthoms- message FPRUNX 113 ("Cannot find PDL type for output device XXXXX")
Possible cause:- The SAPWin printer can not be used together with SAP Interactive Forms by Adobe. Please reas SAP note: #685571Unfortunatelly there is no workaround for this.- Check the printer device associated with the caller user, make sure this printer does not uses the SAPWIN device type.
P7. Problem in complex landscapes only in NW04
Sympthoms- You use a Webdynpro for JAVA Application containing an Interactive Form, the form is not displayed. - In the default trace file you can see the following error: java.net.SocketTimeoutException:Read time-out
Possible cause:- Please check the stting:Visual Administrator: Server -> Services -> Configuration Adapter -> webdynpro -> sap.com -> tc~wd~dispwda Check entry "sap.ADSCallingMode" make sure here the value: 'SOAP' is entered. If not please change this to 'SOAP' and restart the cluster.
P8. Problem with the JMX Service.
Sympthoms- In the default trace you can see the following exception: Stack Trace:
com.sap.engine.services.jmx.exception.JmxSecurityException:
Caller Guest not authorized, only role administrators is allowed to access JMX
Possible cause:- Start Visual Administrator and navigate to: Server node -> Services -> Security Provider. Please also make sure that the MBeanAdmin is mapped to the Administrators Security role on both: com.adobe/AdobeDocumentServices*ADS-EJB and com.adobe/DocumentServicesLicenseManager*ADS-License
P9. xACF controls.
Sympthoms- You use Interactive Forms in Webdynpro Applications. The Form you are using uses ACF (Active Component Famework) technology and not ZCI (Zero client Installation). The PDF is not displayed, instead you see something like a broken image at the place the PDF should be displayed. - You do not see adobe specific exceptions in the default trace file of your J2EE engine.
Possible cause:- The Active Component Framework is not installed on your client. Please follow SAP note: #766191 and install the latest version of the Famework to your client.- You are not using Internet Explorer for accessing the Webdynpro Application. Unfortunatelly ACF is only running in Internet Explorer. In Firefox / Mozilla you can only used ZCI based forms. - You Famework is too old. Please try completely removing it as described in SAP note: #846952 and reinstall the latest version again as described above.
P10. Error while reading trusted anchor configuration information
Sympthoms- The Exception: adobe.service.sap.configuration##com.adobe.service.sap.configuration#######
SAPEngine_System_Thread[impl:5_59
##0#0#Error#1#/System/Security#Plain###
Error while reading trusted anchor configuration information: can be raised when the system tries to seach one entry in SeureStore service. But within the default installation, this entry does not exist.
Possible cause:- This can happen if you never opened the DocumentServiceConfiguration Service in the Visual Administrator. Open VA and navigate to: Server node -> Services -> DocumentServiceConfiguration.-> The mentioned exception should not occure again.

Common Problems with SAP Interactive Forms by Adobe - PART I -

Always Refer to the original Article at https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5484

This weblog is based on problems we often see at our standard support chanel. Here I list the common sympthomes, and common causes. The list (of course) is not complete. If you have one of these sympthomes, it is not sure you have the same problem, what you find here. I hope you will find it useful ;-)
P1 - Plattform / Basis Level -
Sympthoms- The standrad test report: 'FP_TEST_00' or 'FP_CHECK_DESTINATION_SERVICE' "hangs". It runs enendless.- There are NO files (n)or directories located in the "/usr/sap///j2ee/os_libs/adssap/XMLFormService" folder. Maybe the complete: "/usr/sap///j2ee/os_libs/" folder is empty. - You see the following exception in the default trace of the J2EE engine: Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001 - You see the following exception in the default trace of the J2EE engine: javax.xml.rpc.soap.SOAPFaultException:
Transaction system failure in method rpData.
Possible cause:- The ADS is installed on a plattform, that is currently not supported by SAP for ADS. Please check the avaliablity at: Product Availability Matrix - Mixing of different Netweaver releases (NW04 and NW04s) -> This is unfortunatelly not possibble the J2EE engine release has to match with the ABAP stack release in order connect them properly.- The ADS SP level does not match the J2EE engine SP level. -> Please update the software components to have the same support package level.
P2 - Problems with the Credential -
Sympthoms- The printforms work fine, but you can not create interactive forms. - You have error during registration of the credential file.("An error occurred while updating the credential expiry date for alias XXXX") In the default trace you see: java.io.IOException: Error in loading the keystore:
Private key decryption error:
(java.lang.SecurityException: Unsupported keysize or algorithm parameters)
- You see the error: "An error occured while indexing the credential files" while trying to open the credential file.
Possible cause:- First make sure the credential file is ok. You can test this as follows: Download the credential to your local machine (Windows). Start it with double click. The certificate import wizard will be started. Try importing this file, and provide the password at step 3, what you have recived with the credential. If the import is successful that means the crendential is ok. If not, please contact SAP support. - Make sure you have the unrestricted version of JCE installed on your system. You can download this from your JDK vendor. For details see SAP note: #899808 - You have to restart the J2EE engine after you have registered the credential. - The IIOP Service has to be running to register the credential. Please check P3. - Make sure the credential can be found in the correct direcotry. For details see SAP note: #848539
P3 - Problems with the IIOP Service -
Sympthoms- You see the error: "An error occured while indexing the credential files" while trying to open the credential file. (as in P2)- You see the following exception in the default trace file: Caused by: org.omg.CORBA.INITIALIZE:
can't instantiate default ORB implementation com.sap.engine.services.iiop.internal.ORB vmcid: 0x0 minor code: 0 completed: No
- You see the following exception in the default trace file: org.omg.CORBA.BAD_PARAM: Not found ServiceContext with id=0 vmcid: OMG minor code: 26 completed: Maybe
- You recive the following exception, while testing the ADOBE Document Services functionality (e.g FP_TEST_00) ERROR CODE :
100.102
ERROR
MESSAGE :
SOAP Runtime Exception: CSoapExceptionFault : SOAP fault found in SOAP document /Transaction system failure in method rpData./...
Possible cause:- Make sure the start up mode for the IIOP Service is set to 'Always' on both Server and Dispatcher nodes! - After enabling IIOP Service please restart the J2EE engine. - Please check P1 as we have quite often see, that there were IIOP related exceptions in the default trace, when the used plattform was not released for ADS. - Make sure you have at least one data element bound to the form. As we have seen CORBA exceptions when there was no databinding at all.
P4 - a common problem with the ADSUser -
Sympthoms- When you try to test the ADS functionality via the URL: http://:/AdobeDocumentServices/ConfigYou recive the error: Incorrect content-type found 'text/html'
- The response headers of the ADS look: HTTP/1.1 302 Found
Connection: close
Location: http://:/AdobeDocumentServices/Config/ChangePassword
Server: SAP J2EE Engine/7.00
Date: Tue, 05 Sep 2006 11:58:10 GMT
Possible cause:- The password of the ADSUser user is initial. This happens often in the following cases:>> a. The Installation is double stack, and the ADSUser is defined as 'DIALOG' on the ABAP side. Please change this to 'SYSTEM'. >> b. You use some other UME mechanism, what request's the password change for ADSUser. -> You should make the necessary steps to aviod this request. >> c. Please check the following: Go to Visual Admin:
-> server -> service -> security provider service -> user management tab, then select user ADSUser.
If option 'No password change is required' is not selected, please check it.