Posts tagged PDF Generator

Converting DOC(X) in LiveCycle PDF Generator yeilds error: ALC-PDG-019-060-Encountered error while importing the XMP file.

0

- Tai

When PDFG ES2 converts Word documents, it extracts the metadata and compiles it as an XMP for the PDF.

There is a known problem however, when a file contains custom metadata: PDFG cannot compile the XMP properly for such files.

To check the metadata in the DOC, open Word.
Use the MS Office menu (the big round one, top left) : Prepare : Properties
A small yellow info bar will appear above the editing area.
In that area, Click “DIP Properties – …” and select “Advanced properties …”
Go to the “Custom” tab

If there are items in the space at the bottom labelled “Properties”, then your DOCX is likely to fail to convert.

There are two solutions to this:

A) Workaround.
1/ Log on to the LiveCycle Admin UI
2/ Go to Services : PDF generator : File type Settings : [your file type settings]
3/ Open Word file type settings
4/ Uncheck “Convert document info”
5/ Save

This will prevent PDFG from trying to extract and convert the Word metadata – thus excluding the problematic custom information

2) Obtain the patch

If you have an Adobe Platinum support agreement, you can contact technical support and request the patch.

——-
Original article at http://blogs.adobe.com/an_tai/archives/64.

LiveCycle PDF Generator – Configuring WebSphere AppServer Instance to Run As Windows Service

0

Jayan Kandathil

If you get exceptions such as follows in WebSphere SystemOut.log when you try LiveCycle PDF Generator document conversions, you might need to run the WebSphere appserver instance as a Windows service running as the ‘SYSTEM’ account:

ERROR: API = CreateProcessAsUser
INFO [STDOUT] ERROR CODE = 1314
MESSAGE = A required privilege is not held by the client.

Download the utility WASServiceCmd.exe from here. Copy it to %WAS_HOME%bin and run it to create a Windows service for the WebSphere appserver instance that hosts LiveCycle.

Eg:
WASService.exe -add “Adobe_LiveCycle” -serverName “server1″ -profilePath “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01″ -logRoot “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01logsserver1″ -logFile “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01logsserver1SystemOut.log” -encodeParams -stopArgs “-username SYSTEM” -startType manual -restart false

If it worked, you should get a response similar to this:

Adding Service: Adobe_LiveCycle
Config Root: C:ProgramsIBMWebSphereAppServerprofilesAppSrv01config
Server Name: server1
Profile Path: C:ProgramsIBMWebSphereAppServerprofilesAppSrv01
Was Home: C:ProgramsIBMWebSphereAppServer
Start Args:
Restart: 0
IBM WebSphere Application Server V7.0 - Adobe_LiveCycle service successfully added.

Start the service and try the document conversion again. If you still have problems, see this.

——-
Original article at http://blogs.adobe.com/livecycle/2011/04/livecycle-pdf-generator-configuring-websphere-appserver-instance-to-run-as-windows-service.html.

Submitting PDF to a servlet

0

Girish Bedekar

I have written a simple servlet which writes the submitted pdf to the c drive of the server. I have written the instructions in the pdf document which can be found here
Click here to access the pdf
Download the war file
Deploy it on your server
Design your form with a submit button configured to submit “PDF” and pointing to the url
The url should be of the following format

http://:/SaveToFile/SavePdf

in my case it was http://ginger:8080/SaveToFile/SavePdf. Where ginger:8080 is my server and port no.
Save the form and hit the submit button
The form will get submitted to the servlet which writes the pdf to the c drive of the server
Let me know if you need any more help
thanks
girish

—-
Original article at http://eslifeline.wordpress.com/2009/08/13/submitting-pdf-to-a-servlet/.

Go to Top