Posts in Category "PDF Generator"

LiveCycle ES: ALC-PDG-001-001 The Job Configuration either cant be obtained or is invalid

Issue

If you are using PDFG to process documents on your LiveCycle server you may encounter problems with the conversions accompanied by the following exception in the server log:

GeneratePDFIm A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-Job ID for the submitted createPDF job =CreatePDF-2012-07-23 12-05-26.643.docdfaed6-f564cb-14cb09-338b02-c5fd79-ba0c90

GeneratePDFIm E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error.

AWS  E com.adobe.workflow.engine.PEUtil logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

WorkflowDSCIn E com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error. while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

JobManagerBea E com.adobe.idp.jobmanager.ejb.JobManagerBean doOnMessage JobManagerBean:onMessage():Exception:ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.  Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI “#d6f16633df10d6efd649f0d2becce92c”

FileResultHan A com.adobe.idp.dsc.provider.service.file.write.impl.FileResultHandlerImpl tryPreservingFiles FileResultHandlerImpl —– preserved- source —-\\server\WatchedFolders\folder\stage\Wx840560ff8bdc142771fc0a18\CreatePDF-2012-07-23 12-05-26.643.doc— to —\\server\WatchedFolders\folder\failure\CreatePDF-2012-07-23 12-05-26.643\CreatePDF-2012-07-23 12-05-26.643.doc

Reason

PDFG uses file settings to specify what type of PDF file you would like to be generated.  These settings are stored in the LiveCycle server and can be referenced in the AdminUI:

http://livedocs.adobe.com/livecycle/8.2/admin_pdfg/000006.html

This exception occurs when you are converting files using the API, an orchestration, or a custom service, but the settings you have defined do not exist on the LiveCycle server.  This may happen if you have custom conversion settings and then deploy an application/process, which references these settings from one environment to another.  We have also seen this issue when the name of the conversion settings was localized (as LiveCycle was installed on a non-English OS), and therefore the name defined in the service by default was no longer valid.

Solution

You should check your code or custom service to ensure you are referencing a valid PDFG settings file.  You may need to import a settings file in the adminUI, if you use custom settings in your code/service.

reference: (183454350)

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

LiveCycle ES2: barcode visible in PDF file converted to Postscript

Issue

When you use the ConvertPDFService toPS2() operation to convert PDF documents to Postscript in LiveCycle ES2, barcodes are appearing in the PostScript file which were hidden in the original PDF. This issue can occur especially if you used the legacyToSimplePSFlag to convert static documents directly, without flattening them first.

Solution

This issue is a bug in LiveCycle ES2 SP1 and SP2 and has been resolved in a patch.  Contact Enterprise Support if you require this patch for ES2 SP1 or SP2.  Adobe plans to fix this issue in the ES2 SP3, later versions.

You need to set GenerateServerAppearances=true to in the Form render settings when rendering the PDF forms and use the legacyToSimplePSFlag in the PSOptionsSpec for the Postscript conversion to work.

Additional information

 The problem only occurs for pre-generated PDF files which are then merged with XML data on the server side.  The document flow is as follows:

  1. XDP template gets rendered to PDF.
  2. The PDF can then be merged with data on the server, filled and signed by the user.
  3. The PDF is converted to PostScript.

In the input PDF, the barcode value is empty and hidden as expected. When the PDF is converted to Postscript with ES2 SP1, the barcode gets assigned a default value of “123456789…” Therefore, the barcode becomes visible on the resulting PostScript file.  The Postscript file from LC7 works correctly and the barcode remains hidden.

reference: (181754483/2702011)

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

LiveCycle ES2: ALC-PDG-001-026 – transaction timeout settings not respected for watched folders

Issue

When you use watched folders with PDFG ES2 SP1 and increase the timeout, the process still times out after the default 600 seconds. This problem will occur even if you have increased the Application Server transaction timeout, the socket timeout, or JTA timeout in jboss-server.xml, or the timeout settings on the PDFConfigService, and ConvertPDFService.

This problem can be seen with the following log extract:

2010-08-09 08:36:50,485 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-026 133MB File.pdf: Time of Job Execution: 635,047 ms for job = 133MBFile.pdf3f45fc-272597-26ad04-89f5d7-039852-037534

2010-08-09 08:36:50,485 ERROR [com.adobe.pdfg.GeneratePDFImpl] ALC-PDG-001-000
ALC-PDG-010-010-The conversion has timed out.

2010-08-09 08:36:50,485 ERROR [com.adobe.idp.jobmanager.execution.workadapter.PersistentExecutableJob] 
PeristentExecutableJob:execute():Attempting to fail job. Reason:

Solution

This is a bug in PDFG ES2 SP1.  Update to LiveCycle ES2 SP2 or later. You can also contact Enterprise Support if you require a patch for LiveCycle ES2 SP1 9.0.0.1.

reference: (181707812/2686855)

 

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

LiveCycle PDFG7: how to remove the SQL service after uninstalling

Issue

If you have uninstalled PDF Generator 7.2.2 you may notice that the SQL service has been left behind.  You will need to remove this service manually to do a completely clean uninstallation.

Solution

 In order to remove the SQL service in Windows, you can follow these instructions:

Run Regedit or regedt32.

Find the registry entry: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services

Find the service there and delete it.

You may wish to look at the keys and see what files the service was using and perhaps delete them also.

Note:  You will have to reboot before the list gets updated in server manager.

Additional Information

 Some programs change the permissions to make it more difficult for you to delete them. For these you will have to right click on the “service” in regedit, go to permissions and grant the administrator full control before the service can be deleted.

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

LiveCycle ES: ALC-PDG-001-001 Invocation error.

Issue

 If you are using the API for PDFG ES to convert documents to PDF on a localized operating system as outlined in the documentation, you may encounter the following error message:

"Error OCCURRED: ALC-PDG-001-001 Invocation error."

It may also say that the Job settings cannot be found, or are invalid.  Conversion through the PDFG web interface works successfully.

You may be using code similar to:

HtmlToPdfResult result = new HtmlToPdfResult();
result = new GeneratePdfServiceClient(factory).htmlToPDF(
    inputFileName,
    "Standard",
    "No Security",
    null,
    null);

Reason

The names of the settings files for file type (“Standard”), and security settings (“No Security”) as mentioned in the documentation, may have been localized, which explains why the server cannot find the files at run time.

Solution

 Use the localized names for these settings files in your code.  You can check the names for these settings files in the AdminUI > Services > LiveCycle PDFG ES > File Type Settings.

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

LiveCycle PDFG: file bloat when converting PDF to PDFA

Issue

 When converting a PDF to PDF/a you may notice that the file size becomes bloated, for example 18KB -> 448KB.

Reason

 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.

Solution

 To get the smallest file-size during PDF to PDF/a conversion, you should use the RGB conversion options.

reference: (180029449/1707078)

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

LiveCycle PDFG7: Error 1009 trying to start application server

Issue

 If you have installed PDF Generator 7, you may receive the following error when trying to start the application server service:

Error 1009

Reason

 You must use the same user to install MS Word and PDFG, and this user must be the same user account used to start the application server service.

Solution

 Re-install MS Word and PDFG using the same user account (this should be an Administrative user), and then change the LogOn properties for the application server service in the Control Panel to use this account to start the service.

reference: (1-32085976)

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

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

Issue

 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.

Reason

  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.

Solution

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

Issue

 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.

Reason

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)

Solution

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)