If you are using Adobe Acrobat/Reader in a Citrix XenApp environment, you may experience issues related to problems in Citrix or the underlying Windows operating system.  Citrix have issued recommendations for hotfixes in XenApp and Microsoft Windows, which resolve most of the common issues with XenApp 6.0 and later, running on Windows 2008 Server.

If you do experience issues running Acrobat/Reader in a Citrix XenApp environment, ensure you have the recommended hotfixes installed.  You should contact Citrix for support or refer to their technotes such as the one below:

http://support.citrix.com/article/ctx129229

For more information related to Acrobat/Reader deployments on Citrix, please refer to our Enterprise Administration Guide:

helpx.adobe.com/content/dam/kb/en/837/cpsid_83709/attachments/Acrobat_Enterprise_Administration.pdf#page=101

If you have installed ADEP/LC ES3 (10.0.x) you may notice the following error in the server log when starting the application server:

2012-04-18 15:32:49,500 ERROR [com.adobe.livecycle.readerextensions.ReaderExtensionsService] (main) PKI Intialization failed. 
Exception: com/rsa/jsafe/provider/JsafeJCE
2012-04-18 15:32:49,515 ERROR [org.jboss.ejb.plugins.LogInterceptor] (main) RuntimeException in method: 
public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterLocal.doRequiresNew(
com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.TransactionCallback) 
throws com.adobe.idp.dsc.DSCException:ALC-DSC-099-000: com.adobe.idp.dsc.DSCRuntimeException:
java.lang.ClassNotFoundException: Class name com.rsa.jsafe.provider.JsafeJCE from package com.rsa.jsafe.provider not found.

Reason

This error can occur when the wrong JSAFE and CERTJ JAR files have been imported to your application server.

Solution

Review the installation/configuration documentation and ensure the correct JAR files have been copied to your application server.

For example:

http://help.adobe.com/en_US/enterpriseplatform/10.0/ClusterJBoss/WSf7e9d1e3f353177725b65b451306fc33289-8000.html

reference: (183158539)

In LiveCycle ES it is possible to track the dependencies of parent forms to form fragments and vice versa using the functionality in Workbench ES.

In LiveCycle ES2  it is also possible to view the form fragments used by a parent form in Workbench > Form Design > Properties:

It is not possible to track the dependencies from a form fragment to see in which parent forms the fragment is used.  This is due to the architectural changes related to the new application model in LiveCycle ES2.

In LiveCycle ES3 it is again possible to track the dependencies of parent forms to fragments and vice versa.

Solution

If you have a requirement to track the dependencies from fragments to parent forms in LiveCycle ES2, then you can do this using the LiveCycle API using code similar to below:

ResourceRepositoryClient repositoryClient = new ResourceRepositoryClient(myFactory);

String fragmentUri = "/Applications/TestApplication/1.0/fragments/AddressFragment.xdp";

List relations = repositoryClient.getRelated(fragmentUri, false, Relation.TYPE_DEPENDANT_OF);

Here is a full sample class you can execute to test this functionality against a running LC server (you will need to adjust the settings for your environment): ListDependencies.java

reference: (183114773)

If you are trying to reference an OSGi service or component using the SCR annotations, like the SlingRepository in the code below, then you may encounter a NullPointerException when you try to use these objects.

 /**
  * @scr.component immediate="true"
  * @scr.service interface="SampleService"
  */
 public class SampleServiceImpl implements SampleService {
     /**
      * @scr.reference
      */
     private SlingRepository repository;
...

Another symptom of this problem is that your SampleService component may not show up or register correctly in the CQ5 Web Console “components” tab (http://<server>:<port>/system/console/components).

Reason

The SCR annotations are deprecated in the latest builds of Apache Felix.

You should note that CRXDE and CRXDE Lite are both configured to automatically resolve these annotations and build the relevant XML files for you.  In other IDE environments you will have to include the maven-scr-plugin to resolve these annotations and build the XML files yourself.

Solution

To correctly reference these objects in the latest versions you should use the following syntax (note: you will have to explicitly import the Felix scr classes):

 import org.apache.felix.scr.annotations.Component;
 import org.apache.felix.scr.annotations.Service;
 import org.apache.felix.scr.annotations.Reference;

 @Component(immediate="true")
 @Service(interface="SampleService")

 public class SampleServiceImpl implements SampleService {

     @Reference
     private SlingRepository repository;
...

If you are installing and deploying patches for LiveCycle ES2 using the command line version of LiveCycle Configuration Manager (LCM) you may encounter an error similar to the following while deploying components:

com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component
 /opt/adobe/adobe_livecycle_es2/deploy/adobe-usermanager-dsc.jar.
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:419)
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:151)
         at com.adobe.livecycle.lcm.headless.HeadlessLCMImpl.deployDSCFilesLFS(HeadlessLCMImpl.java:285)
         at com.adobe.livecycle.lcm.cli.DeployLCComponentsCLI.executeCommandLineImpl(DeployLCComponentsCLI.java:96)
         at com.adobe.livecycle.lcm.cli.LCMCLI.execute(LCMCLI.java:298)
         at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)

and the LC logs may contain the following exception messages:

Component: com.adobe.PDFServices version: 9.0.0.2.20120202.1.312922
introduced a new service, it should not be patched

….

java.lang.NoClassDefFoundError: com/adobe/idp/um/api/PreferenceManager

Reason

This problem occurs if the order of operations in LCM is incorrect.  For example, if you run the deploy components step (DSCs), before configuring and deploying the new EARs.  This can occur when using the command line LCM as you call each operation separately.  It can also occur using the UI LCM if you run the tool twice in succession and select to deploy components in the 1st run before deploying the EARs in the 2nd run.

Solution

You should re-run the LCM steps ensuring to configure and deploy the EARs first, before deploying the components.

1. Check the registry path for Acrobat or Reader
2. Repair the HKCR\AcroExch.Document registry key
3. Change the content-type header on the web server

If these suggestions do not help, then you can try the general suggestions outlined in this technote: http://helpx.adobe.com/acrobat/kb/cant-view-pdf-web.html

Disclaimer:  These procedures involve editing the Windows registry.  Adobe doesn’t provide support for editing the registry, which contains critical system and application information. Make sure to back up the registry before editing it, or contact a qualified computer service professional to do it for you. For more information about the registry, see the Windows documentation or contact Microsoft.

1. Check the registry path for Acrobat or Reader

If you are running an SQL2 query in CRX 2.2 you may encounter the following exception:

org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024

Running the query through the CRXDE Lite query window, or using QueryManager.createQuery will result in this error.

Reason

This error occurs if you are using the ISDESCENDANTNODE clause in your SQL2 query and there are too many child nodes in the result set.  It is a bug in jackrabbit-core which is part of CRX 2.2.

https://issues.apache.org/jira/browse/JCR-3247

Solution

This issue will be solved in future releases of CQ 5.5 and CRX.

Workaround

The workaround for this issue is to split your SQL2 query into multiple queries to reduce the result set for each query, and then you can consolidate the results afterwards.

reference: (32103)

If you are using the sidekick to switch between edit, design and preview modes, you may notice that the pages refreshes automatically when switching to edit and design mode, but not when switching to preview mode.

This can cause problems if you are using the WCMMode methods and properties in your application to display a different page view depending on the current mode (i.e. using conditional logic based on WCMMode.DESIGN, WCMMode.EDIT and WCMMode.PREVIEW).  If the page does not refresh when switching to preview mode, then it will display the same objects and state as it did in edit mode.

Solution

The solution is simply to force a page refresh automatically when switching to preview mode.

1. Overlay the /libs/wcm/core/components/init/init.jsp component to /apps/wcm/core/components/init/init.jsp.
   For detailed instructions on how to overlay a component watch the following video:
   http://blogs.adobe.com/aaa/2011/11/walkthrough-of-overlaying-or-overriding-a-stock-cq-or-adep-wem-component.html
2. In /apps/wcm/core/components/init/init.jsp add the previewReloadproperty as follows and save the changes:

   CQ.WCM.launchSidekick("<%= currentPage.getPath() %>", {
       propsDialog: "<%= dlgPath == null ? "" : dlgPath %>",
       locked: <%= currentPage.isLocked() %>,
       previewReload: "true"
   });

3. Now CQ is setup to refresh automatically when switching to preview mode.

Note: it is important to overlay the init.jsp component in “apps”, rather than editing the file in “libs”, as libs is overwritten anytime you install a hotfix or a product update from Adobe, and therefore your changes are lost.  It is a best practice to overlay components to apps, and then you always have a backup of the original component in libs.

reference: (32750)

Issue

If you are using the sidekick on an author instance of CQ, you may notice that the toolbar at the bottom which includes the design and preview mode buttons, is not visible or available.

Reason

The functionality in the sidekick is determined by the ACLs (Access-Control-Lists) defined in the CQ server.  If you do not have the appropriate privileges then functionality may be hidden in your sidekick.  Sometimes the sidekick may become unstable if you add faulty components to the page, or after you have installed some packages that may have overwritten required objects in your application, breaking some dependencies.

Solution

You should first try to clear your browser cache, and then reload the page from WCM console to refresh the sidekick.

You should also ensure you have the correct privileges to access the appropriate design in /etc/designs.  This can be changed by an administrator on the Users tab in the siteadmin console.  If the privileges appear to be correct, then try to disable them, save, and then re-enable them and save.  The sidekick should now display the toolbar again as expected.

In CQ5.4 you could start the server in debug mode using the [CQ_HOME]/crx-quickstart/server/server.bat file.  The server folder is no longer there in CQ5.5 on Windows.

Solution

To start the server in debug mode you can edit the [CQ_HOME]/crx-quickstart/bin/start.bat file and add the same debug parameters from a server.bat in an existing CQ5.4 installation, or you can use the command line below:

java -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=30303,suspend=n -jar cq-author-4502.jar

Notes

You may notice that the “Attach Debugger” entry in the CRXDE menu is still disabled even after starting the server in debug mode.  You should analyse the console output on server startup to check for issues related to heap/memory problems which may result in a new process being forked.  The debug options used to start the parent JVM are not passed on to the forked process by default.

You can resolve this by adding more heap to the JVM, and/or by specifying the -nofork command line option to prevent forking.  You can also force the forked process to use the parent JVM parameters by specifying the -forkargs [<arg>...] command line option.

You can find more information on the options mentioned above, and other server startup options under the following link:

http://dev.day.com/docs/en/cq/current/deploying/installing_cq.html#Further%20options%20available%20from%20the%20Quickstart%20file

In enterprise environments it is often required to provide some kind of health check application to check the pre-requisites (i.e. installed apps and versions) on client machines.  This provides an automated way of checking that the client machine is correctly setup for use in business workflows that rely on certain installed applications such as Adobe Acrobat/Reader.

Solution

You can use Javascript to detect and read the Adobe Acrobat/Reader browser plugin version:

http://stackoverflow.com/questions/4122061/javascript-detect-adobe-reader-plugin-for-browser

You can use the Windows GUID from the Registry or the MSI API to read the Reader client version:

Acrobat_Enterprise_Administration

reference: (183022625)

If you are using CQ 5.4 you will notice that the user report is displayed in the browser and you cannot save/export any of the information in this list.

You can view the user report from the “Tools” console in CQ5.  Select “Reports” in the left-hand pane, then double-click the user report in the right-hand pane to open it for viewing and/or configuration.

Solution

It is possible to export the user report as CSV content. You can do this in 3 steps.

1. Overlay the /libs/cq/reporting/components/reportpage/ component to /apps/cq/reporting/components/reportpage/.
   For detailed instructions on how to overlay a component watch the following video:
   http://blogs.adobe.com/aaa/2011/11/walkthrough-of-overlaying-or-overriding-a-stock-cq-or-adep-wem-component.html
2. In /apps/cq/reporting/components/reportpage/body.jsp replace the <body> section with the code in body_code.txt and save the changes.
3. Navigate to the user report again and now you will see a link at the top to “Export” the content as CSV formatted text. This export function has different behaviour depending on the browser version.

Note: it is important to overlay the reportpage component in “apps”, rather than editing the file in “libs”, as libs is overwritten anytime you install a hotfix or a product update from Adobe, and therefore your changes are lost.  It is a best practice to overlay components to apps, and then you always have a backup of the original component in libs.

reference: (32200)

If you are accessing PDF files in the browser from a secure site (i.e. over a HTTPS connection), then you may be presented with a grey blank page, rather than the PDF file. Hitting “Refresh” in the browser will display the PDF file correctly.

Reason

This is a bug in the 10.1.2 version of Acrobat/Reader and has been resolved in the next quarterly release of Acrobat/Reader 10.1.3.  Update to 10.1.3 to resolve this issue, or use the workaround below if you cannot update to 10.1.3 immediately.

Solution

1. Open Acrobat or Reader.

2. Choose Help > Check for Updates.

Reader/Acrobat will install the update automatically.

Workaround

1. Log in to your computer as an Administrator.
2. Click the link to download the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.zip  file.
3. Unzip the file to extract the executable AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe.
4. Close Adobe Acrobat/Adobe Reader if it is running.
5. Do one of the following to run the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file:
1. Double-click the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file.
2. Run the AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.
   Example: <path to AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe> -silent
6. Once the process is completed, you receive a prompt stating the result of the operation. You can choose to restart the system (if prompted) at that moment or later, but a restart will be needed to ensure that the fix has been applied correctly.
   Note: When run in silent mode, all dialog boxes are suppressed. No success message or error message appear.
7. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log. (The changes sometimes only take effect after you restart your computer)

Additional Information

This issue is also being discussed in the following forums:

http://forums.adobe.com/thread/948331?tstart=0

http://forums.adobe.com/thread/948648?tstart=0

reference: (3087872)

http://helpx.adobe.com/acrobat/kb/troubleshoot-pdf-printing-acrobat-reader.html

If you are using servlets or scripts to serve your PDF files in the browser, and you then want to use the standard “Attach to Email” button on the Acrobat/Reader toolbar (also available under the File menu) to forward the PDF to another user by email, you may notice that the PDF does not get attached to the email in some situations.

Reason

When you click on the Acrobat/Reader “Attach to Email” button on the toolbar it sends a request to your default email client to compose a new message.  It will also attempt to create the PDF attachment using the file name specified in the URL where the actual PDF is stored.

The URL may be too long to create a PDF file as attachment if it contains very long parameters as follows:

http://localhost:8080/Simple_Servlet/DMShowPDF?command=getdocuments&PDF=path/123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF

In this case the filename of the resulting PDF attachment would be:

123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF

This can exceed operating system limits, and therefore the attachment does not get created/added to the email message.

Workaround

Simply reducing the length of the URL, particularly the string which will be used for the PDF attachment file name, will allow the PDF attachment to be created.  Even just reducing it by a few characters is sufficient.

Solution

A cleaner solution however, would be to re-structure the URLs so they are shorter, and/or move the PDF parameter to the last parameter position as follows:

http://localhost:8080/Simple_Servlet/DMShowPDF?command=getdocuments&sig=0123456789abcdefghijklmnopqrstuv&ts=0123456789012&category=new&stage=EDITING%3B%3B%3B1%3B%3B%3B&docid=S0123456789abcdefghijklmnopqrst&ext=.PDF&PDF=path/123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf

In this case, the attachment file name will be:

123_4567890abcdefghijklmnopqrstuvwxyz_0_0.pdf

reference: (182987737)

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

Reason

This exception is occurring because of a problem in the Form design.  If you have a table in your form design with, let’s say 4 columns, you should check this table to ensure you don’t have a row with more than 4 fields defined.  This can occur especially when you have created the field objects first, and then converted a whole collection of objects into a table later on.  The extra (5th) field, can exist in a 4-column table if it has a width of “0″.

Here is an sample form to demonstrate the problem: support_test

Cell5 in Row1 is the extra field causing the problem in this case.

Solution

Simply delete the extra field as it is not visible anyway due to the “0″ width.

In future LiveCycle versions we will make changes in Output to return the PDF, and only show this message as a warning in the server log.  This will match the behaviour in Designer ES2 and Forms.