Archive for April, 2010

LiveCycle ES: ALC-DSC-119-000: InvalidCoercionException: Cannot coerce object: Apr 07, 2010

Issue

When you use Date objects in a LiveCycle ES 8.2.1 orchestration after migrating from LiveCycle 7, the following exception may occur:

ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: Apr 07, 2010 of type: java.lang.String to type: class java.util.Date
 at com.adobe.idp.dsc.util.CoercionUtil.toDateTime(CoercionUtil.java:532)
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:966)
 at com.adobe.workflow.datatype.CoercionUtil.toType(CoercionUtil.java:168)
 at com.adobe.workflow.dom.VariableAttr.setBoundValue(VariableAttr.java:67)
 at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionContextImpl.java:791)
 at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataWithExpression(PATExecutionContextImpl.java:375)
 at com.adobe.workflow.qpac.set_value.SetValueService.execute(SetValueService.java:72)
 at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:558)

Reason

This exception occurs if you are trying to use the parseDate() or parseDateTime() functions in your XPath expressions. In LiveCycle ES, it’s not necessary to use these functions to convert Strings into Date objects. These functions cannot handle formatted date strings. For more information about the date functions, see the LiveCycle online Help: http://livedocs.adobe.com/livecycle/8.2/wb_help/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Workbench_ES&file=000812.html.

Solution

Use a direct assignment in the XPath expression to convert the String into a Date variable.

reference: (181553843/2610966)

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

Acrobat/Reader: Application crash using HP Universal Print driver

Issue

 When you use the Hewlett-Packard Universal Printer driver, Adobe Reader and Acrobat may crash. The following error may appear in the OS event log:

Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=083a8310 ebx=0701649c ecx=08431f30 edx=00000be8 esi=00000000 edi=0000002c eip=0700bf92 esp=0012cea4 bp=0012cef4 iopl=0
 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 fl=00210206

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\BIB.dll -BIB!BIBLockSmithAssertNoLocksImpl+0x4b7b:0700bf92 0fb772fe
 movzx esi,word ptr [edx-2] s:0023:00000be6=????0:000> kb
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WTSRV\system32\ntdll.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\AGM.dll -

Explanation

This issue occurs only after printing multiple times; sometimes only after the fourth or fifth print job. It is only reproducible in certain environments (for example, German Windows locale, with a German domain).  This issue was thought to be an Adobe issue, based on the error message above pointing to an Adobe DLL.

After further investigation, Adobe discovered that strange results from the call to the Microsoft API “DeviceCapabilities” cause this error. When correct, this call returns the number of pages that were sent to the printer. For a document with 22 pages, it sometimes returns 39 sometimes 22 and sometimes -1, which means the function failed. Any result other than 22 is false and could result in the crash. If the function returns 39, then there is space for 39 pages reserved in memory when only 22 are written. Therefore, some other memory is overwritten by mistake, which would result in an application crash.

HP have developed an updated driver to fix this issue.  Other customers experiencing this issue should contact HP to get the updated driver.

reference: (181283908/2558881)

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

LiveCycle Designer: Render a trailing page in a form for duplex printing

When you use duplex printing (that is, printing on both sides of the paper), you can print a separate blank trailing page. To print a trailing page, the last page must always have an odd page number (that is, page 1, 3, 5, 7, and so on). When the last page is odd, it prints on a new sheet of paper separate from the rest of the form.

Render a trailing page in LiveCycle Designer 7.x

LiveCycle Designer 7.1 includes a script for rendering a trailing page.

To make sure that the last page has an odd page number, do the following:

  1. insert a blank hidden body page in the form just before the page you want to use as a trailing page.
  2. insert the following script in the layout:ready event of the form to show/hide the blank page at run-time:
var pageCount = xfa.layout.pageCount();

if(pageCount%2 == 0) {
    //even, show the blank page to shift the trailing page down to an odd page number
    form1.blank_page.presence="visible";
} else {
    //odd, hide the blank page as the trailing page is already on an odd page number
    form1.blank_page.presence="hidden";
}

Note: The layout event ensures that the trailing page always falls on an odd number, even if the end user alters the form contents. Such alterations cause the layout:ready event to run and adjust the page numbers accordingly.

Rendering a trailing page in LiveCycle Designer ES

LiveCycle Designer ES includes functionality in the Master Pages to handle duplex printing.

  1. Add Master Pages for odd/even numbers, for the last page, and for the blank page.
  2. Using the Printing option in the Master Pages page set, set up the form for duplex printing.
  3. For the odd/even Master Pages, choose the appropriate option in the Master Page >Pagination tab under Odd/Even.
  4. For the last page, choose the Last Page option in the Master Page > Pagination tab under Placement.
  5. For the blank page, choose the Blank Pages option in the Master Page > Pagination tab under Odd/Even.
  6. For the body page that occurs just before the trailing page, choose Go To Even Page in the After settings under the Pagination tab.

Sample files

Here are some sample file showing the solutions as outlined above for Designer 7.1 and ES.  I have included some test data files also to test the solutions with different page numbers.  You can import the data files into the XDP templates using Designer to test the solutions.

sample_files

reference: (181512630)

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