Posts in Category "LiveCycle"

LiveCycle ES: java.net.SocketException using WebServices

Issue

 If you are using web services in your processes in LiveCycle ES or ES2, you may receive the following exception in the logs:

2011-04-20 17:30:44,072 ERROR [com.eviware.soapui.impl.wsdl.WsdlSubmit] Exception in request: java.net.SocketException: Software caused connection abort: recv failed
2011-04-20 17:30:44,072 ERROR [com.eviware.soapui.SoapUI] An error occured [Software caused connection abort: recv failed], see error log for details
2011-04-20 17:30:44,072 ERROR [soapui.errorlog] java.net.SocketException: Software caused connection abort: recv failed
java.net.SocketException: Software caused connection abort: recv failed
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
 at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
 at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)

This exception occus when the web service WSDL cannot be reached (i.e. network issues, port numbers, firewall).  It can also be related to database problems.

Troubleshooting

1. Check the web service is reachable and responds as expected.

2. Try to restart the database server.

Additional information

 http://forums.adobe.com/message/3203930

reference: (182264455)

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

LiveCycle ES: duplicate events being received on JBoss clustered installation

Issue

 If you are using a JBoss clustered installation of LiveCycle ES2 to handle batches of events, you may notice that some events are received twice, (i.e. 10 events thrown, 12 events received).

Solution

 This can occur if the JBoss cluster is not configured correctly.  In the cluster settings (i.e. run.bat for JBoss) it is important to give each node in the cluster a unique server name using the “Adobeidp.serverName” parameter.  For example, Adobeidp.serverName=server1 for the first node in the cluster, and Adobeidp.serverName=server2 for the second node and so on…

Additional information

 When you give the two servers in a cluster the same name, you wind up with a workmanager on each server that has the same name. Work items get assigned to a specific workmanager, but since they both have the same name it becomes a race to see which one picks up the work item first. In some specific timing cases both will pick up the work item at the same time and process it, which is the reason for the duplication of events.

reference: (182264450)

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

LiveCycle ES2: PDF form state not maintained after converting to PDF/a

Issue

 After converting a PDF file to PDF/A using LiveCycle ES2 you may notice that the form state has not been maintained for unsigned files.  This can manifest itself in that form objects (fields, buttons, subforms etc…) which were hidden in the original PDF file, are now visible in the resulting PDF/A file.

The form state is always maintained for signed files.

Solution

 This is an issue in LiveCycle ES2 (9.0.0.0, 9.0.0.1 and 9.0.0.2).  This issue will be addressed in ES2 SP3 and the new ADEP platform.  There are patches available for ES2 SP1 and SP2, so contact enterprise support if you require one of these patches.

Additional information

 We have added a new flag to the PDFOutputOptionsSpec used during the PDF to PDF/A conversion called “retainFormState“.  This flag must be set in the API parameters, or using the new option in the Workbench UI, to retain the form state on the resulting PDF/A file.

Here is the existing javadoc for PDFOutputOptionsSpec:

http://help.adobe.com/en_US/livecycle/9.0/programLC/javadoc/com/adobe/livecycle/output/client/PDFOutputOptionsSpec.html

reference: (182219821/2818751)

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

LiveCycle ES2: errors after updating to WebSphere 6.1 Fixpack 35 (6.1.0.35)

Issue

 If you are running LiveCycle ES2 on WebSphere and you update to WAS FP35 (6.1.0.35) you may notice some random errors in the server logs such as:

com.adobe.livecycle.docconverter.client.ValidationException: ALC-CVT-S00-003: Error while validating PDF/A conformance of a document: docConverter.pdf
 at com.adobe.livecycle.docconverter.DocConverterServiceImpl.isPDFA(DocConverterServiceImpl.java:463)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:618)
...
Caused by: com.adobe.internal.pdfm.pdfa.PDFAServiceException: PDFM_I27002: PDF/A Validation was unable to release document 
"{SharedPDFMDocHandle name=docConverter.pdf ID=270667810 getStore={SharedStore name=docConverter.pdf ID=637281788 (faux clone of 1810918384) 
idp=<document state="passive" senderVersion="3" persistent="false" senderPersistent="false" passivated="true" senderPassivated="false" deserialized="true" 
senderHostId="127.0.0.1/4.241.117.208/4.241.117.207/4.241.117.214/4.241.117.234/4.241.117.233/4.241.117.232/4.241.117.236/4.241.117.227/4.241.117.226/
4.241.117.210/4.241.117.216/4.241.117.209/4.241.117.215/4.241.117.218/172.16.252.148/4.239.195.28/4.100.183.28" callbackId="0" senderCallbackId="16" 
callbackRef="com.adobe.idp._IDocumentCallbackStub:IOR:00bdbdbd0000002849444c3a636f6d2f61646f62652f6964702f49446f63756d656e7443616c6c6261636b3a312e30000000000
100000000000000c4000102bd000000194431303041455539313535382e443130302e696e7465726e00bd24550000002c4a4d42490000001071960b49000000000000000000000000000000000000
002400000008000000120000000000000007000000010000001400bdbdbd0501000100000000000101000000000049424d0a0000000800bd00011500000200000026000000020002bdbd49424d040
00000050005020102bdbdbd0000001f0000000400bd0003000000200000000400bd0001000000250000000400bd0003" isLocalizable="true" isTransactionBound="false" 
defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="0" contentType="null" length="95543">
<cacheId/><localBackendId><DocumentFileID fileName="/usd/as91558a/work/was-v61/apps/jvmdms.a.1/temp/AdobeDocumentStorage/local/docm1302791768337/1925ec208e7deba285534660215ae481"/>
<localBackendId/><globalBackendId><DocumentFileID fileName="/usd/as91558a/work/was-v61/apps/jvmdms.a.1/native/adobe/jvmdms.a.1.as91558.1/DocumentStorage/docm1302792793931/d570dc3cf31fc6f368d4ee043ede67d5"/>
<globalBackendId/><senderLocalBackendId/><senderGlobalBackendId/><inline/><senderPullServantJndiName>adobe/idp/DocumentPullServant/adobews__957269328</senderPullServantJndiName>
<attributes/></document> pdfDoc=null sharedData=null} getPdfDoc=null getCounted=null refCount=0}".
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:273)
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:193)
    at com.adobe.livecycle.docconverter.DocConverterServiceImpl.isPDFA(DocConverterServiceImpl.java:461)
... 71 more
Caused by: com.adobe.internal.pdfm.NotAPDFException: PDFM_S00025: Document docConverter.pdf of type application/octet-stream is not a PDF.
    at com.adobe.livecycle.assembler.SharedPDFMDocHandle.open(SharedPDFMDocHandle.java:232)
    at com.adobe.internal.pdfm.PDFMDocHandle.acquire(PDFMDocHandle.java:608)
    at com.adobe.internal.pdfm.PDFMDocHandle.acquirePDF(PDFMDocHandle.java:662)
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:217)
... 73 more

The errors that occur depend on what kind of processes and activities you are running in the LiveCycle server, so they could be very different to the above.  The cause of these errors is the WebSphere version and changes that were made to the JDK used by WebSphere.  With WAS FP35 (and probably FP33 and 37) the default behaviour of IgnoreMalformedInput has been set to false, resulting in this change in behaviour for the String constructor in the JDK, causing these issues in LiveCycle.

Solution

 Contact IBM to ensure you have the latest fixes which should contain the solution to this problem as outlined below.  The latest fixes should reset the default behaviour of IgnoreMalformedInput=true.

As an immediate workaround you can manually set the JVM parameter “-Dcom.ibm.IgnoreMalformedInput=true” in your WebSphere administration console.

Additional information

 Information from IBM related to the changes that cause this behaviour and the relevant workaround and fixes:

String constructor does not operate correctly with UTF-16 in Java SR12 FP1

This is a known issue and we had to make changes because of the behavior difference between IBM and OracleJVMs.  The change was to enable conformity with the Oracle JDK for malformed URLs.  To revert back to the original behavior you must add the following  parameter to the “Generic JVM Args” section in the WAS Admin console (instructions in the link below):

-Dcom.ibm.IgnoreMalformedInput=true

Where to set generic JVM arguments in WebSphere Application Server: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365

For more details  on the issue please refer to the APAR- IZ80870  (link below).

IZ80870: REPLACING THE ILLEGAL UTF8 BYTE SEQUENCES WITH \UFFFD: http://www-01.ibm.com/support/docview.wss?uid=swg1IZ80870

Please note, this change went into SR 12 FP1, which is why the same behavior does not occur in the previous SDK releases.  Here is the SDK fix list confirming the above APAR went into SR 12 FP1:

http://www.ibm.com/developerworks/java/jdk/aix/j532/fixes.html#SR12FP1

reference: (182181050/2838202)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)

LiveCycle7: javax.mail.MessagingException: 554 Mail from [email@mail.com] rejected for policy reasons

Issue

 If you are using the mail/notification functionality in LiveCycle 7, you may find that the mails are never received by the intended recipient.  If you look in the adminui you may find the action has stalled with the following error:

"javax.mail.MessagingException: 554 Mail from <email@mail.com> rejected for policy reasons"

Reason

 This is caused by a lack of privileges to use the SMTP mail server in your organisation.

Solution

Consult your IT department and request permission for the Lc Server to use the SMTP mail server to send email notifications.

reference: (1-28762420)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

LiveCycle Workbench ES2: duplicate body tags when saving a form with floating fields

Issue

When using LiveCycle Designer 9 through LiveCycle Workbench 9 to create and modify XDP templates with static text and floating fields, you may notice that saving the form in this situation creates duplicate <body> nodes in the XML source.

There is an issue with the integration between Workbench and Designer and the auto-checkout functionality when saving changes to a file.

Solution

This issue will be addressed in a future release. Currently there is a quick fix available for LiveCycle ES2 SP2. Contact Adobe Enterprise Support to obtain this quick fix.

As a workaround you use the Save button on the Designer toolbar, rather than the File>Save menu item.

Additional information

 This issue can be reproduced using the following steps:

  1. Open Workbench 9.5.
  2. Create new application.
  3. Right-click new application and create new form in Workbench, click Finish.
  4. Add a static text object.
  5. Menu: Insert->Floating field.
  6. Save and close XDP.
  7. Checkin form in Workbench.
  8. Double-click form in WB to open in Designer.
  9. Delete some chars from static text label.
  10. Click on File menu (yes to checkout).
  11. Then view XML.

Result:

Duplicate <body> node in the static text field object.

This behaviour means that only the first node, with the old text label, will be used when the form is rendered, and shown in Designer design view.  It also produces an “Invalid append operation” error in the server log, and in Designer log.

reference: (181920824/2777586)

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

Acrobat/Reader: “There was a problem reading this document (131)”

Issue

When you try to view a document in Adobe Reader or Acrobat, you receive the error, “There was a problem reading this document (131).“.  This error will occur when you used LiveCycle ReaderExtensions to apply usage rights to PDF documents with the Full Save option activated.

Sometimes, the following message precedes the error above:

An error exists on this page. Acrobat may not display the page correctly. Please contact the person who created the PDF document to correct the problem.

Solution

Disable the Full Save option in the ReaderExtensions tool, and apply the rights again. Disabling this option enables the incremental save feature in the PDF. The incremental save feature will increase the file size and allows Acrobat or Reader perform the save operation faster, without the file becoming corrupted. If you aren’t using the web interface, but use the API to apply rights, you can activate the incremental save using the PDFUtilitySaveMode object. For more information, see

http://help.adobe.com/en_US/livecycle/9.0/programLC/help/index.htm?content=001005.html

Additional information

Adobe plans to resolve the problem with the Full Save in ReaderExtensions in a future release.  There is a patch available for LiveCycle ES2 SP2, so if you require this patch, contact Enterprise Support.

reference: (181996532/2785898)

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

LiveCycle Designer: flowed layout in header/footer subforms incorrect

Issue

When you use flowed subforms that repeat on pagination (that is, after pages break), some fields in the subform are rendered on top of other fields.  This can occur in all versions of Acrobat/Reader and LiveCycle.

Solution

You cannot use a flowed layout for subforms that are set up to repeat on pagination, as header or footers to pages.  The objects in the subform aren’t positioned correctly after the page-break and overlapping can occur.

Use a positioned layout for these subforms, rather than a flowed layout. You can change the layout of the subform in LiveCycle Designer. Select the subform, and then choose the Layout tab from the object panel on the lower right.

Additional information

Extract from the XFA Specification 3.1 (Page 277):

“Flowing Layout for Containers…

Error Condition: Inappropriate Layout Strategy:

Flowing layout applied to a subform that is a leader or trailer or is contained within a leader or trailer subform (because the leader or trailer size is fixed).”

reference: (181804954/2724676)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

LiveCycle ES: support for LC ES in virtualized environments

Information

 Virtualization technologies tested and supported by Adobe for LiveCycle ES include VMware ESX, IBM LPAR, and Solaris Zones. Microsoft Hyper-V is not supported.

VMware created the virtualization market in the x86 world. Their product offerings can be grouped under two buckets: hosted and bare-metal. Bare-metal virtualization offers better performance than hosted virtualization.

Hosted virtualization requires a “host” operating system which hosts other “guest” operating systems hat are contained in virtual machines.  A bare-metal virtualization platform is a bases operating system-like kernel called the hypervisor, usually with a management console that runs on top of the kernel. There is no host OS.

http://forums.adobe.com/message/2270201

You can find detailed information about installing/deploying LiveCycle ES and ES2 in virtualized environments under the following links, or by searching on adobe.com:

http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/lces2_virtualized_environments.pdf

http://www.vmware.com/files/pdf/techpaper/Adobe_LiveCycle_ES_Deployment_on_VMware.pdf

http://blogs.adobe.com/livecycle/2009/02/solaris_10_zones_support.html

http://blogs.adobe.com/livecycle/2007/12/livecycle_quick_and_dirty_serv.html

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

LiveCycle ES2: ALC-FDI-001-305: Operation aborted: Malformed input PDF or data

Issue

 When you use the FormDataIntegration Service in LiveCycle ES2 to merge XML data into a PDF file, you may encounter the following exception:

2010-03-29 14:58:31,885 ERROR [com.adobe.livecycle.formdataintegration.client.ImportFormDataException] 
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data. 
2010-03-29 14:58:31,964 ERROR [com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker] 
An exception was thrown with name com.adobe.livecycle.formdataintegration.client.ImportFormDataException message: 
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data. while invoking service FormDataIntegration 
and operation importData and no fault routes were found to be configured.

This exception occurs only for certain PDF files and other XML datasets cause the same error in the PDF file. However, you can use the same data XML in other PDF files without error. There are no visible problems in the PDF file, and no problems reported by Preflight.

Reason

This error occurs because of a bug in our Gibson library. Gibson doesn’t correctly handle a rich text field with an empty body element as value.

Solution

This issue has been addressed in LiveCycle ES2 SP1 and later versions.

reference: (181504595/2591446)

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

LiveCycle ES2: “The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.”

Issue

When you convert PDF files to PDF/A using LiveCycle ES2, and then validate the files with a PDF validator, you receive the following error:

The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.

The font PZSWZL+CustomSymbol must be embedded.

Validation in LiveCycle ES2 and Acrobat 8 or 9 validates the PDF/A without errors.  Validation with current validators such as Acrobat X Preflight, or 3 Heights PDF Validator produce the error above.

Solution

This issue is a problem in LiveCycle ES2 (9.0.0.0, 9.0.0.1, and 9.0.0.2) as it should also return an error that the PDF/A is invalid.  This issue is fixed in LiveCycle ES3 (LC10) and later.  There is a patch available for ES2 SP1 and SP2, so contact enterprise support if you require one of these patches.

Additional information

PDF 1.4 recognizes only the following cmaps for TrueType fonts:

  • cmap subtable with platform ID 3 and encoding ID 1 (Microsoft Unicode, also called  [3,1])
  • cmap subtable with platform ID 1 and encoding 0 (Macintosh Roman, also called [1,0])

In this case, the PDF file was using a custom font CustomSymbol that contained a (3, 0) cmap subtable, which PDF 1.4 doesn’t recognize.  Therefore, Acrobat X and other PDF/A validators correctly reported an error when checking for PDF/A-1b compliance (As PDF/A-1b is based upon PDF 1.4).

reference: (181779161/2714061)

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

LiveCycle ES: how to retrieve a list of groups and roles on your server

Requirement

 You may have a requirement to provide a full breakdown of all Users/Groups/Roles for your installation of Adobe LiveCycle ES. It is possible to find out this information using the AdminUI, however this would take a lot of effort and time to perform all the necessary searches and manually compile the information returned.  The other option would be to run an SQL query on the database to read the information directly from the DB tables.

Solution

 The following are 2 SQL queries to:

==========================================
Query 1: Identify all Users in each Group
==========================================

select epea.commonname as GROUP_NAME,
epeb.commonname as USER_NAME
from lcesprd.edcprincipalentity epea,
lcesprd.edcprincipalentity epeb,
lcesprd.edcprincipalgroupentity epg,
lcesprd.edcprincipalgrpctmntenti epgc
where epea.id = epg.refprincipalid
and epea.id = epgc.refparentprincipalid
and epeb.id = epgc.refchildprincipalid
and epea.status = 'CURRENT'
and epeb.status = 'CURRENT'
and epea.principaltype ='GROUP'
and epeb.principaltype ='USER'
order by GROUP_NAME

==================================================
Query 2: Identify all Roles assigned to each Group
==================================================

select epea.commonname as ROLE_NAME,
epeb.commonname as GROUP_NAME
from lcesprd.edcprincipalentity epea,
lcesprd.edcprincipalentity epeb,
lcesprd.edcprincipalroleentity epre
where epea.id = epre.refroleid
and epeb.id = epre.refprincipalid
and epeb.principaltype ='GROUP' -- (Note: can change this value to 'USER')
order by ROLE_NAME
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.0/10 (1 vote cast)

LiveCycle Forms ES: read-only pop-up menu values modified when navigating through XHTML forms

Issue

The values in pop-up menus change when you move between pages on an XHTML form rendered from an XDP template with LiveCycle Forms ES.  Some drop-down lists (DDLs) show the empty value, whereas others actually have a different entry from the original value.

This behavior is not expected, as the drop-down lists are marked as read-only. This issue is serious, as it affects data integrity in the submitted forms. You can test this behavior using FormsIVS in LiveCycle ES with the NoScriptXHTML transformation.

Solution

Adobe has resolved this issue in LiveCycle ES 8.2.1.4 and 10.  There is a patch available for LiveCycle ES 8.0.1, so contact enterprise support if you require this patch in your environment.

reference: (181801041/2734988)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 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 ES 8.0.1.2: Workspace memory leak using IE6 or IE7

Issue

When you use Workspace ES 8.0.1.2 in Internet Explorer 6 or 7 and you log in, open an XFA form, and log out repeatedly, the memory usage increases. Usage increases between 500 KB to 3 MB when you close forms, and up to 30 MB when you log out of Workspace.

Solution

This is a bug in Workspace 8.0.1.2.  Contact Enterprise Support to obtain a patch for LiveCycle ES 8.0.1.2. Or, use LiveCycle ES 8.2.1.1 or later.

reference: (180457723/1906173)

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