Archive for March, 2012

LiveCycle ES2: LCMException[ALC-LCM-030-200]: Failed to deploy component


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
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(
         at com.adobe.livecycle.lcm.headless.HeadlessLCMImpl.deployDSCFilesLFS(
         at com.adobe.livecycle.lcm.cli.DeployLCComponentsCLI.executeCommandLineImpl(
         at com.adobe.livecycle.lcm.cli.LCMCLI.execute(
         at com.adobe.livecycle.lcm.cli.LCMCLI.main(

and the LC logs may contain the following exception messages:

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


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


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.


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


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

Acrobat/Reader: PDF files not displaying in the browser

If you are having problems displaying PDF files in the browser using Adobe Acrobat/Reader in an enterprise environment, there are 3 things to check in your environment.

  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:

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

  1. Go to Start > Run.
  2. Type regedit and click OK.
  3. Browse to the key HKEY_CLASSES_ROOT\Software\Adobe\Acrobat\Exe.
  4. Make sure that the (Default) value is set for the path where Acrobat or Reader is installed.
    • The default path for Reader is “C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe”.
    • The default path for Acrobat is “C:\Program Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe”.

Note: If Acrobat or Reader isn’t installed in the default path, make sure that the key’s (Default) value points to the actual location.

If the above registry item doesn’t exist on the system, do the following:

  1. Go to Start > Run.
  2. Type regedit and click OK.
  3. Go to Edit > New > Key and create the missing HKEY_CLASSES_ROOT\Software\Adobe\Acrobat\Exe.
  4. Go to Edit > New > String Value and name this key (Default).
  5. Select (Default), and then go to Edit > Modify. Type the default path (listed above) in the “Value data” for your product.
  6. Restart the computer.

2. Repair the HKCR\AcroExch.Document registry key

It is possible that this key is damaged, is pointing to an obsolete version of Acrobat or Reader, or is pointing to a third-party PDF viewer.

  1. Choose Start > Run, type regedit in the Open text field of the Run dialog box, and then click OK.
  2. Back up your current Registry file:
    1. In the Registry Editor dialog box, choose File > Export.
    2. Type a name for the file and choose the location.
    3. For Export Range, choose All.
    4. Click Save.
  3. Navigate to HKEY_CLASSES_ROOT\AcroExch.Document.
  4. Right-click AcroExch.Document and select Delete; make sure that you have the correct key, and click Yes on any prompts.
  5. Right-click AcroExch.Document.7 and select Delete; make sure that you have the correct key, and click Yes on any prompts.
  6. Repair your Acrobat or Reader installation using one of the 2 methods below:
  • Repair using Control Panel (Windows).  Although you can repair your product installation by choosing Help > Repair [product] Installation, the Control Panel method sometimes provides better results. Close Reader or Acrobat.
      1. Click Start > Control Panel.
        • (Windows 7/Vista) Click Programs, and then click Programs and Features.
        • (Windows XP) Double-click Add or Remove Programs.
      2. In the list of programs, select Adobe Reader or Adobe Acrobat.
      3. Click Change and follow the instructions to repair the application.
      4. When the process is complete, click Finish.
  • Repair from within Reader or Acrobat.
    • (Reader) Choose Help > Repair Adobe Reader Installation.
    • (Acrobat) Choose Help > Repair Acrobat Installation.

3. Change the content-type header on the web server

If you’re a webmaster or have administrative rights to a website, configure the web server to send content-type headers of ‘application/pdf’ for PDF files. For instructions, see the documentation that came with the web server, or see article 305153 on the Microsoft website at

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

CRX2.2: BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 running SQL2 query


If you are running an SQL2 query in CRX 2.2 you may encounter the following exception:$TooManyClauses: maxClauseCount is set to 1024

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


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.


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


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)

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

CQ5: preview mode in sidekick does not refresh automatically


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.


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

  1. Open /libs/wcm/core/components/init/init.jsp
  2. Add the previewReload property 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.

reference: (32750)

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

CQ: design and preview mode toolbar not visible


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.


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.


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.

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

CQ5.5: how to start the server in debug mode


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.


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


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:

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

Acrobat/Reader: how to automatically check the installed version


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.


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

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


reference: (183022625)

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