- Saurabh Kumar Singh, Computer Scientist @ Adobe
Following are a few tips and workarounds for LiveCycle PDFG. Please note that the workaround marked as unsupported are not officially supported by Adobe.
- [Unsupported] On UNIX servers customers can use 64-bit OpenOffice to do OpenOffice based conversions. The obvious benefit from this is the performance improvement we get. To achieve this just point JAVA_HOME_32 to 64 bit version of Java. Same can achieved on widows too but you may observe immediate conversion failures for other native file formats.
- [Unsupported] Any file which can be opened by Acrobat (like a text file) can be converted to PDF using LiveCycle PDF Generator. You just need to add the comma separated file extension (for example txt for text files) in XPS to PDF file-type setting.
- A user/administrator can directly jump to PDF Generator UI by hitting http(s)://<server-name>:<port>/pdfgui. This way a user can skip couple of clicks on UI to land on PDF Generator user interface.
If you are using LiveCycle Output to generate PDF documents using XDP files as input, you may encounter the following exception and no PDF will be returned:
0000012a XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage
ALC-OUT-002-017: mid,tid: 29435,23593162.1 sev: f text: Failure to automatically determine column '8' width.
0000012a FormServerExc E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage
ALC-OUT-002-013: XMLFormFactory, PAexecute failure: "(com.adobe.document.xmlform.ReturnStatus@39133913)
Failure to automatically determine column '5' width."
If you load the same XDP file in Designer ES2 and goto PDF Preview, you may notice the same message as a warning in the log, but the PDF will be correctly rendered and displayed:
Failure to automatically determine column '5' width
Read the full article at http://blogs.adobe.com/dmcmahon/2012/02/04/livecycle-output-es2-failure-to-automatically-determine-column-5-width/.
– David McMahon
If you are attempting to configure Adobe LiveCycle server using the LiveCycle Configuration Manager (LCM) with an Oracle database, you may encounter the following exception during the DB configuration step:
Caused by: java.lang.UnsupportedClassVersionError:
(oracle/jdbc/OracleDriver) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.Class.forNameImpl(Native Method)
This error can occur if you are not using the correct Oracle DB driver, or the correct Java JDK for your platform.
You should check the Oracle DB driver and JDK version required in the relevant platform matrix. With LiveCycle ES2 for example the platform matrix is located here:
So if you were to install LiveCycle ES2 on AIX 5.3 with WebSphere 7, you should be using the 64-bit JDK 1.6 SR7 provided by WebSphere (WAS_HOME/AppServer/java), and the ojdbc6.jar Oracle driver.
Be sure to set the JAVA_HOME and PATH environment variables as instructed in http://help.adobe.com/en_US/livecycle/9.0/prepareinstallsingle.pdf
Original article at http://blogs.adobe.com/dmcmahon/2012/01/21/livecycle-es2-unsupportedclassversionerror-oraclejdbcoracledriver-bad-major-version-at-offset6/.
– David McMahon
If you have installed a patch or service pack for LiveCycle ES you may need to uninstall this at a later date, or you may have a requirement to document this process fully as part of your installation/configuration documentation.
This information is outlined in the readme file provided with each patch or service pack, and I will just expand on that giving some more detail here. In this example I will discuss uninstalling LiveCycle ES Update 1 SP4 (126.96.36.199), to go back to LiveCycle ES Update 1 SP3 (188.8.131.52) on Windows.
Before installing/uninstalling any patch you should take note of the current versions installed so you can verify your steps have been successful later. Take a screenshot of the About screen, and the Service Management screen from the AdminUI.
AdminUI > About screen (note the Patch version “SP4″ and Service Pack version “8.1.5192.1.284202.47″, and the Patch level of each deployed component “SP4″):
AdminUI > Services > Applications and Services > Service Management screen (note the Component Versions “8.1.5192.1.284202.47″, “8.1.5193.1.279333.70″, etc…):
Before running through the uninstallation process it would advisable to make a backup of your existing configuration in case any unexpected problems should arise. To do this, you should make a copy of the entire LiveCycle installation directory (excluding the MySQL folder if it exists within the LiveCycle directory).
You should also take note of the following configuration properties from AdminUI > Settings > Core System Settings > Configurations:
- Location of temp directory
- Global document storage root directory (Changing this value will result in data loss unless you also manually move the data)
- Location of the Adobe Server Fonts directory
- Location of the System Fonts directory
If you have LiveCycle Content Services ES installed, you should also have the location of the Content Services root directory which you entered during the original installation/configuration process.
Read the full blog post at http://blogs.adobe.com/dmcmahon/2011/12/20/livecycle-es-how-to-uninstall-a-patch-or-service-pack/.