|
Some output files are not converted from a watched folderSome LiveCycle servers (most commonly those running on
UNIX) invokes the conversion process before all the associated files
are copied to the watched folder, and therefore missing some of
the files. To avoid this issue, create a folder outside the watched
folder hierarchy, copy all of the required files into the folder, and
then copy the entire folder to the watched folder root.
OutputIVS Printer not foundIf you see this error, then follow the steps below:
In the URL \\<servername>\<printername>,
specify the full name of the printer.
Add the printer to the windows account before starting JBoss.
Enable JBoss to run in the context of a valid user. To perform
this task, change the properties of the JBoss service by clicking
the Log On tab and selecting This account. Supply
a valid user name and password and restart the service for this
change to take effect.
The server that hosts LiveCycle needs to have permissions
to access the printer; the connection fails if it does not have
the necessary permissions.
Diagnosing cache related problemsIf you have an older form that is being cached and re-used
instead of a newer or changed version of the form, you will see
unexpected results after generation. Make the following updates
to resolve this problem:
Ensure that the cache validation settings are set so
that the template you are using had been revalidated. If an update
is made and the form is re-rendered within a few seconds, it is
possible that the revalidation checkpoint time has not yet occurred
and the updated form will not be picked up. To avoid this issue,
set the validation method to Unconditionally or manually
reset the cache.
Ensure that uniquely generated templates being passed by
value have empty UUID strings, so that they are treated as non cacheable.
If you have a cacheable form but are not seeing the performance
benefit of caching, review the following settings:
Ensure that the LiveCycle Designer 11 settings allow
for caching rendered forms.
Ensure that the render options allow the render cache to
operate. In general, flat PDF document renderings cannot be cached,
whereas render-at-client forms benefit from the render cache.
Search within the physical directory structure of the cache
to find the cached template and rendered elements of your document
to confirm that the form is being physically cached.
Make a copy of the form and manually removed the form’s UUID.
This creates a version of the form that will always bypass the cache.
Then compare the performance of the non-cached and cached version
of the form to determine what benefit the cache is yielding.
Some output files are lost when a clustered WebSphere Application Server shuts downSome expected output files may be lost when one WebSphere
Application Server of a cluster shuts down. One possible cause is
that invocation requests from a watched folder cannot, for various
reasons related to the shutdown, access files that are placed in
the staging folder.
Complete the following procedure to recover the lost files.
To recover files from a staging folder:Ensure that the node is restarted.
Log in to Administration Console and click Services > Applications and Services > Endpoint Management.
In the Provider list, select WatchedFolder, and then
click Filter to display the endpoints for the watched folder.
Select the check box for the service name endpoint, and then
click Disable. The watched folder is now disabled from processing
new files.
Wait for LiveCycle to recover and process any files it can
access. The waiting time depends on the time that is required to
process the operation being called and the number of files being
recovered.
Check the date-time stamp of the files that remain in the
staging directory to identify which files are old enough to be files
that were lost due to the shutdown.
Copy the lost files to the input directory.
Re-enable the watched folder to process new input files by
repeating steps 2 to 4 and selecting Enable.
Password encryption errorWhen Federal Information Processing Standards (FIPS) mode
is enabled in LiveCycle (set either during the LiveCycle configuration
process or manually in the Core Systems Settings web pages within
Administration Console), password encryption will not be applied
to any document. If you attempt to encrypt the password on a FIPS-enabled
document, the error “Password encryption is not permitted in FIPS
mode” is displayed.
PDF output contains an unwanted orange watermarkA PDF file generated from a Microsoft Word document may
have an unwanted orange (not gray) watermark “LiveCycle Generator
Evaluation”. (A gray watermark results from other LiveCycle settings.)
This error is typically caused when the example.ps file becomes
corrupted (for example, by multiple installations of LiveCycle on
the same server). To correct this problem, delete the C:\Documents and
Settings\[user]\Application Data\Adobe\Adobe PDF\Distiller\Startup\example.ps
file from the application server that LiveCycle runs on and then
restart the server. In a clustered environment, delete the file from
all servers where it occurs and then restart each server that you
deleted the file from.
Browser cache may interfere with HTML renditionIf you are rendering to HTML an XDP form that contains
references to images (either through links or embedded images) or
contains data with links or image data, you should disable browser
caching to avoid having cached data interfere with image display.
“Failure to create directory” error on WindowsOn a Windows environment, you may encounter an error when
converting PRN files to PDF format from a watched folder endpoint.
This error is dependent on the Output parameter that is set in Administration
Console.
When a watched folder endpoint’s Output parameter is set to %E/%F.pdf,an output
directory named with the originating file name extension is created
to receive the converted files (%E = file name
extension, %F = file name). For example, when the
file example.prn is converted to PDF, a new directory is created
(if it does not already exist) and the file is stored there. The
result would be //prn/example.pdf.
On a Windows operating system, prn is reserved for system
directories only and an attempt to create it generates the “Failure
to create directory” error.
To avoid this error, set the value of the Output parameter for
the PRN file to PDF endpoint to %E_/%F or %E_Files.%F.
(See LiveCycle Administration Help.)
“Error while converting image to PDF” on WindowsOn a Windows environment, you may encounter any one of
a set of related errors when you convert an image file to PDF. To
address this error, configure the Generate PDF service to use Adobe®
Acrobat® Professional image conversion.
To configure Acrobat image conversion:In Administration Console, navigate to Services > Applications and Services > Service Management and
click GeneratePDFService: 1.1.
On the Configuration tab, in the Use Acrobat Image
Conversion (Windows Only) box, type true, and then
click Save.
Conversion of OpenOffice.org files to PDF fails on SolarisConversion of OpenOffice.org files to PDF may fail with
a timeout error if a long temp directory name is specified on Solaris.
The temp directory name should be 20 characters long at the maximum.
Do the following to resolve this issue:
Navigate to Settings > Core System > Core Configurations in
the Administration Console.
Enter a shorter directory name in the Location of temp directory field.
For example, /tmp or /usr/temp.
Click OK.
“Content URL 404 error” using template in ContentspaceWhen using the doc_info.php template in Contentspace ,
you may encounter an error message indicating a Content URL error.
To address this error, replace the contents in the doc_info.php
template.
To replace the contents:Log in to Contentspace as administrator and
click Company Home > Data Dictionary,
In the right pane, click Presentation Templates and
then click the doc_info.php content item.
Replace the contents of the doc_info.php file with
the following text:
<?php
$document = $_ALF_MODEL["document"];
if ($document != null)
{
?>
<h4>Current Document Info:</h4>
<b>Name:</b> <?php echo($document->cm_name); ?><br>
<b>Ref:</b> <?php echo($document->__toString()); ?><br>
<b>Type:</b> <?php echo($document->type); ?><br>
<b>DBID:</b> <?php echo($document->sys_node_dbid); ?><br>
<b>Content:</b> <a href="<?php $pos1 = strpos ( $document->url , 'ticket');echo ( substr( $document->url, 0, $pos1 -1 )) ?>"><?php $pos1 = strpos ( $document->url , 'ticket');echo ( substr( $document->url, 0, $pos1 -1 )) ?></a><br>
<?php
if ($document->hasAspect("cm_countable") == true)
{
?>
<b>Counter:</b> <?php echo($document->cm_counter); ?><br>
<?php
}
?>
<b>Aspects:</b>
<table>
<?php
foreach ($document->aspects as $aspect)
{
?>
<tr><td><?php echo($aspect); ?></td></tr>
<?php
}
?>
</table>
<b>Properties:</b>
<table>
<?php
foreach ($document->properties as $name=>$value)
{
echo("<tr><td>".$name." = ".$value."</td></tr>");
}
?>
</table>
<?php
}
else
{
echo "No document found!";
}
?>
 Save the file.
Bell Gothic font deprecated in LiveCycle and DesignerThe LiveCycle server and Adobe® LiveCycle® Designer 11
installations no longer include the Bell Gothic font. If you are
upgrading and have forms that use this font, either substitute it
with one available on your system, or purchase it from the Adobe
Store.
How a form using Bell Gothic is affected during runtime:LiveCycle server: If
this font is missing from the LiveCycle server, PDF Generator will
automatically substitute the font in the generated PDF output file.
Designer: When
opening the form in Designer, the Missing Fonts dialog appears and
prompts the user to substitute the missing font.
"Cannot retrieve the resource from Repository Path" errorAfter upgrading from LiveCycle 9.x or 8.2.1.x, exceptions
such as the following warning appear in the server logs while retrieving
images from the LiveCycle repository. Inspite of the exception,
the PDF file generates as expected.
00000041 FormServerExc W com.adobe.livecycle.formsservice.logging.FormsLogger logMessage
ALC-OUT-002-058: Cannot retrieve the resource from Repository Path. Authority component retrieved is "<somestring>". Path component retrieved is "/somefolder/someimage.jpg".Underlying Exception is : ALC-REP-018-000: Resource [/somefolder/someimage.jpg] does not exist or you do not have sufficient rights to access it.
This exception occurs due to the use of incorrect syntax in the
URL to the image repository where resources are cached. If "repository://"
is used instead of "repository:///", the resource is not cached.
Because resources were not cached in LiveCycle 9.x or 8.2.1.x, the
exceptions were not seen on that system.
To resolve this issue, modify any instances of repository://
to repository:/// in forms migrated from LiveCycle 9.x or 8.2.1.x.
Middle-Eastern and Indic characters do not appear in PDF documentsWhen you convert a file that contains characters of Middle-Eastern
or Indic languages to a PDF document, the characters of Middle-Eastern
and Indic languages does not appear in the output document.
To convert the documents that contain characters of Middle-Eastern
or Indic languages to a PDF document, use Adobe Acrobat WebCapture.
For detailed information about Acrobat WebCapture (Windows Only),
see Generate
PDF service settings in the Administrator's Guide.
|
|
|
