Internal

Resolving java.sql.SQLRecoverableException with the Oracle 11 driver

0
233 days
by in Internal
LiveCycle ES2 and ES3 both support Oracle 11g.  There have been reports of LiveCycle customers experiencing the following database connectivity failure intermittently even when the database is running and the data source has been configured properly for LiveCycle connectivity:  WARN  … Continue reading →

LiveCycle and Adobe Code Signing Certificate Revocation Announcement

0
233 days
by in Internal
Today Adobe announced an issue around our code signing certificate (for details read the Adobe corporate blog post). To be clear, LiveCycle customers are not impacted by this. We have verified through testing that the issue with the digital certificate, … Continue reading →

LiveCycle ES2 – Unicast based Workspace Clustering

0
233 days
by in Internal
Adobe LiveCycle Workspace is based on client-server application model. It has Flex based client and Java based server component. All clients connected to different servers in a cluster, should be in sync all the time. This is achieved using event … Continue reading →

LiveCycle Cluster – WebLogic Unicast Clustering

0
240 days
by in Internal
LiveCycle deployment is supported on both unicast and multicast based appserver clusters. LiveCycle documentation provides steps for default application server cluster configuration, usually multicast based cluster. In this blog, we will go through steps for creating unicast based WebLogic cluster. Steps for … Continue reading →

ALC-BCF-001-001: Undefined filter – JBig2Decode

0
243 days
by in Internal
If you are decoding scanned PDFs with LiveCycle Barcoded Forms, and they contain JBig2 compressed images, you may see this error in your server logs.  ERROR [com.adobe.barcodedforms.decoder.image.PDFImageIterator] ALC-BCF-001-001: com.adobe.internal.pdftoolkit.core.exceptions.PDFCosParseException: Undefined filter – JBIG2Decode  com.adobe.internal.pdftoolkit.core.exceptions.PDFInvalidDocumentException: com.adobe.internal.pdftoolkit.core.exceptions.PDFCosParseException: Undefined filter – JBIG2Decode This happens, because … Continue reading →

LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

0
244 days
by in Internal

Issue

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

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

reference: (183608560/2751566)

Failed to load/render property editor when assigning a Userlist from a process in LiveCycle Workbench ES3

0
246 days
by in Internal
In LiveCycle ES3 (and SP1) Workbench, you could encounter this error when attempting to view the participant’s property editor in the Multiple Assign Task service when attempting to provide a list of Users via a process:  If you look at the … Continue reading →

How to resolve message “Invalid version: The current version of the XFA template model exceeds the capability of Acrobat/Reader” in your server log

0
246 days
by in Internal
In many cases, you will see messages like “ALC-XTG-029-487: [3472] Invalid version: The current version of the XFA template model exceeds the capability of Acrobat / Adobe Reader 9.0″ in your server log file on each render of your form … Continue reading →

Adobe Reader cannot open Protected Mode due to a problem with your system configuration.

0
295 days
by in Internal

Issue

If you are starting Adobe Reader and have Protected Mode enabled, you may encounter the following dialog:

“Adobe Reader cannot open in Protected Mode due to a problem with your system configuration. Would you like to open Adobe Reader with Protected Mode disabled?”

Reason

This dialog appears when protected mode cannot be started due to environmental settings on your computer.  It can occur due to anti-virus software conflicts, and/or conflicts with accessibility tools or smart card software and drivers.

Troubleshooting

1. Unsupported configurations:

  • Installing Reader on a mapped network drive.
  • Running Reader on WinXP when the OS is installed in a public folder.
  • Launching Reader in XP-compatible mode on Vista and Win7.
  • Launching Reader by right clicking AcroRd32.exe and choosing Run As.
  • Using PKCS#11 smart cards in signature workflows. Some cards can work in the presence of custom protected mode policies. For a workaround, see below.
  • Collaborating in real time using the Collaborate Live feature.
  • Certain configurations of anti-virus software that have not yet white-listed AcroRd32.exe. See Anti-virus software conflicts below.
  • JS-invoked processes: Launching a process through JavaScript is not allowed with Protected Mode enabled.

2. Antivirus software conflicts:

By default, Adobe Reader X runs in Protected Mode. In certain situations Reader experiences compatibility issues with anti-virus software when that software intercepts some system calls for the Reader sandbox. In these cases, Reader could fail to open or crash after displaying an incompatible-configuration dialog.

For example, Protected Mode is known to be incompatible with:

  • Some Symantec Endpoint Protection configurations. Adobe recommends that users update to Symantec Endpoint Protection 11.0 RU6 MP2 or higher.
  • McAfee VirusScan Enterprise for certain actions in Reader. Known actions include the following:
    • Clicking Help or a Weblink from an embedded Flash widget such as a Portfolio navigator (Fixed 10.1).
    • Launching of some IME tools. Note: Disabling Buffer Overflow Protection can provide a workaround for many McAfee users.
    • Reader sometimes removes a user’s cached credentials when signing out of Adobe.com which could be an issue for a multiuser machine. Fixed 10.1.2 with MVE 8.8.

Adobe is working with anti-virus companies to resolve these problems.

3. Accessibility

For XP only: Accessibility features sometimes doesn’t work. The Read Out Loud feature is unsupported. Therefore, screen readers such as JAWS, Windows Eyes, and Windows Narrator aren’t always able to read PDF content. Much of the Accessibility menus involving things like quick check, change Reading options are removed. Keyboard navigation is not implemented.

Note: When a screen reader like JAWS, Window-Eyes, or Narrator is running when Reader is started for the first time on XP, Protected Mode is disabled. On Vista and Windows 7, screen readers do work normally.

4. P11 smart card workaround

The installation of some smart cards doesn’t work for Reader X users when in Protected Mode. Because Protected Mode sandboxes certain processes that make system calls, smart card installation can fail or result in the “unsupported configuration” dialog appearing. However, a simple workaround is available. Install the smart card software with Protected Mode turned off as follows:

  • Disable Protected Mode by going to Edit > Preferences > General and deselecting Enable Protected Mode at startup
  • Restart Reader
  • Install the smart card software according to the provider’s instructions
  • Re-enable Protected Mode
  • Restart Reader

5. Windows Permissions

You should also check the permissions on the Adobe Reader installation folder.  Protected mode will only work on Windows when the group “BuiltIn\Users” has the following permissions on the Reader installation folder (for a default installation C:\Program Files (x86)\Adobe\Reader 10.0):

  • Read & execute
  • List folder contents
  • Read

Further Information

http://helpx.adobe.com/acrobat/kb/protected-mode-troubleshooting-reader.html

How to Deal with LiveCycle DSC Classloading Problems

0
302 days
by in Internal
Scenario: Customer had a working LiveCycle 90 SP1 cluster and they upgraded to SP2. After successful upgrade to SP2 (a.k.a 9.0.0.2) their forms were failing to render in workspace. Error message indicated a generic ALC-WKS-007-027 for workspace rendering but server … Continue reading →
« Previous
Next »
Go to Top