Archive for January, 2009

LiveCycle 7: MissingResourceException in FontManagerService during LiveCycle startup


You may encounter problems starting the application server with LC7 installed where it can take up to an hour to start, or you may get the following exceptions:

FontManagerService: Exception while attempting to read initialization properties from com/adobe/config/FontManagerService-init

java.util.MissingResourceException: Can’t find bundle for base name com/adobe/config/FontManagerService-init, locale de_DE


These problems occur when using JDK version 1.4.2_10.  This JDK version has backwards compatibility issues and is therefore not supported for LC7.


 Use a different supported JDK version and this will resolve the issues.

reference: (1-21393042)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: LCMerror101 trying to run ConfigurationManager


If you have successfully installed Workflow, FormServer or FormManager and then run LiveCycle Configuration Manager (LCM), you may receive the following error:

Configuration Manager Errors

Error Code:LCMerror101

Message: Livecycle modules could not be copied to working directory.


 This is due to the version of the JDK being used: JDK 1.4.2_10.  This JDK version has broken backwards compatibility, and so is not supported for LC7.


 Use a different JDK version and this will resolve the problem.

reference: (1-21322849)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Designer: Unable to initialize ACE interface


 If you are working with Designer on terminal server, you may experience intermittent problems starting the Designer client, such as the following error:

Unable to initialize ACE interface


Designer 6 or 7 are not supported on Terminal Server.  Designer versions 8 and later are supported on terminal server.

There is an ACE.dll in the designer product folder, which is the Adobe Colour Engine.


 As a workaround, you can copy the ace.dll from the Reader/Acrobat installation folder, and overwrite the one in the Designer folder.  Make a backup of the Designer ACE.dll first.  This has been known to resolve the issue for some customers.

reference: (1-16374929)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (3 votes cast)

LiveCycle 7: how to create a WebDAV connection to the Forms appstore


 You can use Web Folders to browse the appstore from FormManager, or to publish forms directly from Designer, however you may encounter problems trying to connect to it using the following URL:



You will need to apply this fix first to enable Web Folders on your system: (Follow method 2)

Then follow these instructions to connect to the WebDAV server:

For XP and W3K:

1.) Navigate to My Network Places

2.) Select Add a network place

3.) Enter http://<server>:<port>/appstore/Forms

4.) When prompted enter the username and password of a user that has the roles of Adobe Administrative Console User and LiveCycle Form Manager Administrator.

5.) You will be prompted for the credentials once again then the add network wizard will display a panel letting you identify a name for the network place.

6.) Select Next

7.) Select the check box to open this connection and select finish.

8.) You have now a webdav connection to the root of the appstore and can publish forms directly to it.

You can then use this Network place directly from Designer to publish/edit forms in the appstore.

reference: (1-22309006)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.5/10 (2 votes cast)

LiveCycle PDFG7: LCMerror 9007 trying to start the application server after installing PDFG


 If you have installed PDFG7 you may encounter the following error when the application server is trying to start:

LCMerror 9007 Failed to start turnkey service JBOSS

Trying to start the application server service manually results in this error:

Error 1029 The service did not start due to a logon failure.


  During the installation, you would have been asked to enter the username and password for PDFG so that you can install the product.  This should be the same user which installed the application server and should be an administrator with sufficient privileges to install new software and run processes.


First check that you are logged in as an administrator.  Then you should check in Control Panel -> Services, and open the Properties for the application server service.

In here you will find the properties for LogOn for the service, and here you must enter the Administrator logon details.

Additional Information

 After resolving this issue you may receive error 1053, which says that the service did not respond in the allocated time.  You can ignore this error as the application server just takes a long time to reply, but it does start successfully after some delay.

reference: (1-23596767)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle PDFG7: Error Code 1015: This file type is not supported


 If you are using PDFG7 to convert HTML files to PDF using the Convert PDF function you may receive the error message:

Error Code: 1015

Error Message: This file type is not supported.


This is the expected behaviour.  When you enter a physical HTML file in the browser Create PDF servlet, then it will be sent to Distiller, but Distiller does not understand HTML files.

PDF Generator 7 can convert the following content to PDF:

  • PostScript and Encapsulated PostScript (EPS)
  • Image formats (JPG, JPG 2000, GIF, BMP, TIFF, PSD)
  • Microsoft Word, Microsoft Excel, and Microsoft PowerPoint (DOC, XLS, PPT)
  • Microsoft Project (MPP)
  • Corel WordPerfect
  • Plain text and rich text (TXT, RTF)
  • Web (HTML)
  • AutoCad (DWG)
  • Microsoft Visio (VSD)


When you want to convert an HTML file, then you must enter the URL with “http://…” or “https://…” and convert it using the web page converter function. Then it will be sent to Acrobat to be conveted with Web Capture.  HTML files reside on a webserver and so it is expected that they are referenced through the URL, not as a local .HTML file.

If you really need to work with local .HTML files, then you could open the .HTML file using Microsoft Word, and save it as a .doc for example.  PDFG can then convert this .doc file without problems.

reference: (1-25037774)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

How to load dynamic images in a PDF file using Adobe Reader/Acrobat 8+


When you change the href property in a PDF form at runtime, images no longer load dynamically in Adobe Reader/Acrobat 8 and later versions.


Here are some suggested workarounds used in different situations to get avoid this issue:

  • Solution 1: Embed the images in the form as hidden objects.
  1. Add the image to the form in Designer, and set its presence to “hidden” in the object panel.
  2. Then set the image field’s presence to “visible” on the “initialize” event, or the “click” event of a button.
  3. Repeat for each image that you want to use on the form.

Note: This solution is only applicable when you use a few images. This solution affects performance, but if the images are in a compressed format, the effect can be minimized.

  • Solution 2: Upload the images as attachments.
  1. Do one of the following to upload the images as attachments:
    • Use the attachment panel in Acrobat (View > Navigation Panels > Attachments > Add).
  2. Update the value of the image field using script at runtime to point to the attachment. (See the “Opening and saving attachments” section in the Javascript scripting guide)
  • Solution 3: Use either a web service or a database connection.
  1. Configure a web service or database connection to return a string that contains Base64-encoded image content. (To build a web service or a database connection is complex and requires some custom coding, so it is out of the scope of this blog entry.)
  2. Open the form in Designer and go to the “Data View.”
  3. Add a new Data Connection.
  4. Select OLEDB Database, or WSDL file. (Press the Help button on this dialog in Designer to get more context help on how to configure each data source.)
  5. Add an image field to the form.
  6. Go to the Object panel and set the Binding for the image field to the return object from the web service or database.
  • Solution 4: Use the Privileged folders functionality in Acrobat 9+.
  1. Put all the images in a folder on a network share, available to all computers that access the form.
  2. Open the enhanced security settings in Acrobat/Reader 9 (Edit > Preferences > Security (Enhanced)).
  3. Add a folder path or the host name where the images are stored. The folder path tells Acrobat/Reader 9 that the path for the images is exempt from the enhanced security settings.

Note: Only try this solution after approval from your system administrator. You are essentially disabling some of the security features of Acrobat or Reader, which are there to prevent potential hacker attacks.

Additional Information

There were a few reasons for this change in the security settings:

a) A form could point to a “file://” URL for data mining purposes.
This condition allows for potential hacking as external parties see where the pictures are stored, and the names of the files on your computer. For example, they could see that the pictures were stored under My Documents\Pictures and that all had names like PIC000xx.JPG.

b) PDF documents are supposed to be self contained.
Pointing to an “ftp://” or “http://” URL to load an image dynamically breaks that promise. When a user certifies a document for example, the user certifies that the content of the document is safe. However, if the document dynamically loads an image, that image file stored on some web server can be changed without breaking certification. But, the meaning of the document can be different.

Consider the following situation where the content of the PDF reads:

You owe me:


…but could be changed to…

You owe me:


….just by changing the image on the server.

c) The same issue could appear with a signed document.
If you sign the document, you are signing the form in its current state and agreeing to the content as it stands. If the image on the server changes afterwards, the signature would still be valid. As some Adobe customers use signatures in legally binding workflows, Adobe cannot allow the content to change without reflecting that in the PDF or the signature.

The strategy moving forward is to have encapsulated PDF files remain true to the PDF specification. If you find another workaround to allow the images exist outside the PDF, it is also likely that Adobe would disable it in some future version of Reader and Acrobat.


You could change the href property in Reader up to version 8.0. But from 8.1 onward the security was tightened and potential security holes, like this one, were closed.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.3/10 (4 votes cast)