When you are working with Designer to edit form you may see the following warning in the report palette:
"Bad value '#f1' of the 'use' attribute of 'font' element - Default will be used."
You may see this error if you delete the “Referenced Objects” node in the Designer hierarchy.
Referenced Objects refer to any repeating objects in the form, fonts, images etc… You can define an object and its properties in the <proto> node in the XML and then just call it many times using its ID through the “use” attribute.
If you delete the Referenced Objects object, the <proto> tag will be deleted, and so the object definitions along with it. The “use” attributes will not be mapped to any object definition and so will result in this warning.
Refer to the XFA 2.4 specification, where, on page 194 it describes how to define these objects in the proto node.
If you are trying to apply rights to a PDF document with ReaderExtensions 7.0, you may receive the following error in the web browser:
Error 400: Applying User Rights to the document ‘SAE_V0.9Static.pdf’ failed:
and the following exception in the log file:
[26.08.05 09:21:03:361 CEST] 500fe7b1 Logger
E com.adobe.document.PDFManipulation document does not have certifying signature
[26.08.05 09:21:19:622 CEST] 50e8a7b1 Logger
E com.adobe.document.PDFManipulation an unknown exception caused the call
This error can occur on all application servers.
1. This is due to an incompatibility when using Designer 6 to design documents to be processed with ARES 7. This issue has also been seen using some language versions of Designer.
2. This issue could also occur if you are trying to apply rights to a password-protected PDF document, and you dont supply the password when applying the rights.
1. If you use Designer 7 or greater then the documents can be correctly extended with LCRE 7.
2. If you supply the password for the PDF when applying the rights, the error will not occur.
If you are trying to ReaderExtend a PDF in LCRE 7 either in the web interface, or using the API, you may receive the following error:
Error 473: Credential permissions are invalid...
This error is related to the credential permissions provided with LCRE. There is a .pfx credential file which must be configured with LCRE to allow you to ReaderExtend documents. This credential is essentially used to certify the PDF when applying the rights, to prevent unauthorized changes to the PDF once distributed. You need to provide an alias/password for this credential file when installing LCRE.
Often the wrong alias/password combination is used for this credential when installing LCRE.
Make sure you use the alias/password provided with the credential file.
Other possible causes:
1) using the wrong JDK or using JDK 1.4.2_10 which is not supported
2) ares-roles.properties, ares-users.properties not correctly mapping users in
When converting a PDF to PDF/a you may notice that the file size becomes bloated, for example 18KB -> 448KB.
There are 2 reasons for the increase in size when we select the “PDFA-1b” conversion:
1) extra fonts which get embedded in the resulting PDF/a document
2) the color scheme chosen in the “PDFA-1b” setting. If you select CMYK then the size gets increased drastically. But if you choose RGB then the difference in size is negligible, assuming there are no fonts to be embedded.
To get the smallest file-size during PDF to PDF/a conversion, you should use the RGB conversion options.
If you are using the Acrobat SDK to control the print functionality in Acrobat/Reader, or to write a custom print plugin, you will need to use the function: AVDocPrintPagesWithParams(avDoc, &docPrintParamsRec);
The length of the input parameters in docPrintParamsRec, e.g. the printer names, are limited to 64 characters, or 32 Unicode characters. Windows however supports up to 240 characters for printer names.
Printing to a printer with a name longer than 64 characters, will not give an error message, the document will just not print.
This is a limitation in the Acrobat SDK as it still uses short printer names. In the Acrobat standard printer dialog, there is no limitation as the dialog uses internal methods which have already been extended for long printer name support.
The Acrobat 9 SDK will resolve this issue and add support for long printer names.
Please refer to the following link for the declaration of the AVDocPrintPagesWithParams function (pg: 1713):
it is discussed again here:
If you are installing Workflow 7.2.2 onto a DB2 database you may encounter the following error during the bootstrapping process:
“A system temporary table space with sufficient page size does not exist”
This is due to the “CREATE TEMPORARY TABLESPACE” command having failed when you created the LiveCycle Database.
This can occur when the DB creation script is invalid, due to missing line breaks, or spaces. Please consult the appropriate LC installation documentation for your version. The script for LC7 is as follows:
CREATE TEMPORARY TABLESPACE ADOBE_TEMP_8K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING (‘C:\DB2\ADOBE_TEMP’) EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE ADOBE_DATA_8K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING (FILE’C:\DB2\ADOBE_DATA’1000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP8K;
If you are attempting to install LC ES on an Italian operating system, you may receive the following error trying to run LiveCycle Configuration Manager:
Failed on 'Stopping JBoss Service JBoss for Adobe LiveCycle ES v8.0'
Service shutdown failed for: JBoss for Adobe LiveCycle ES v8.0
Installation on a localized OS is supported as long as it is one of the supported OS versions, however, localized operating systems have not been tested and you may encounter issues.
Install on an English operating system if possible. If you only have a localized OS, then proceed with the installation and report any issues to Adobe support. We can provide patches as necessary to get LiveCycle running on the localized OS you are using.
If you have manually configured the JBoss4.2.x application server and installed LiveCycle ES, you may receive the following exception when starting JBoss:
13:36:29,277 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:36:29,793 ERROR [[/]] Error configuring application listener of class
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
During the manual configuration of JBoss 4.2.x the documentation from prepareinstallsingle.pdf advises you to disable the JSF libraries contained in [appserver root]/server/all/deploy/jboss-web.deployer. You must disable the JSF libraries, and also remove the related entries from the web.xml, otherwise the above excpetion will occur when starting JBoss.
Comment out or remove the following entries from [appserver root]/server/<config-name>/deploy/jboss-web.deployer/conf/web.xml:
<!-- Comment/Remove this -->
<!-- Configures JSF for a web application if thejavax.faces.webapp.FacesServlet is declared -->
<!-- in web.xml.-->
<!-- Comment/Remove this -->
<!-- Listens to all web app lifecycle events so that @PreDestroy can becalled on -->
<!-- JSF managed beans that go out of scope. You can comment this out if you-->
<!-- don't use JSF or you don't use annotations on your managed beans.-->
<description>JSF standard tlds</description>
You should use the setTimeOut() method with the action defined as closeDoc(). The setTimeOut() method must be assigned to a variable in a top level object in the form, to prevent it from being garbage collected when a lower level variable goes out of scope.
In the form:ready event you should add the following script:
var discard = soUtils.closeDoc();
and then create a new Script object on the form with the following code:
var str = "This document will now close.";
return app.setTimeOut('this.closeDoc();', 1);
Then the PDF should automatically close itself when opened in Acrobat/Reader.
When attempting to import an LCA archive in the adminui you may receive the following exception:
2008-03-18 09:23:11,808 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method:
public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.
DataType: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance version:0.0 not found
at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
This exception occurs when the TaskManager DSC service is not deployed. ProcessManagement usually installs this TaskManager component.
You should check the deployment directory for your application server and confirm that the file “adobe-taskmanager-dsc.jar” is deployed. Then goto the adminui and ensure the service is running under Services > Applications and Services.