LiveCycle: Troubleshooting protocol for PDF Generator ES2

Jayan Kandathil has posted a really useful troubleshooting protocol for PDF Generator ES2 at the LiveCycle Product Blog. Here are the questions that Jayan suggests you consider while troubleshooting PDFG issues:

  • Is the operating system Windows?
  • Is the hardware sufficient?
  • Is the memory sufficient?
  • Is Microsoft Office installed (Windows only)?
  • Did you start Microsoft Office applications after the install and dismiss all dialogs?
  • Is Adobe Acrobat Professional 9 installed (Windows only)?
  • Is OpenOffice.org installed (Linux or Solaris only)?
  • Is the ‘Print Spooler’ service running?
  • Is the ‘Adobe PDF’ printer set as the default printer?
  • Did you start Acrobat Professional after the install and dismiss all dialogs?
  • Which Windows user’s credentials is PDF Generator running with?
  • Does the PDFGen.api file exist in the \Acrobat\plug_ins\ folder?
  • Is the System Readiness Tool happy?

For the complete blog post, visit this URL.

Content Services: Dependencies for indexing different types of content

Indexing of content in LiveCycle Content Services 9 depends on different LiveCycle ES2 components and services. Here are a few important prerequisites:

  • Indexing of PDF files (except for dynamic PDF forms) requires the Assembler service, which is part of all LiveCycle ES2 installations.
  • Indexing of dynamic PDF files requires LiveCycle Output 9. If Output is not installed, the FormDataIntegration service, available on all LiveCycle ES2 installations, is used instead. However, in such cases, for dynamic PDFs created in Acrobat, only the form data is indexed. The form design is left unindexed.
  • Indexing of Microsoft Word 2007/2010 files (.docx) requires PDF Generator 9 (the GeneratePDF service).
Additionally, files protected by LiveCycle Rights Management 9 are not indexed.