Archive for May, 2011

LiveCycle ES: java.lang.OutOfMemoryError deploying DSC components in LCM


 If you are deploying the DSC components using the LiveCycle Configuration Manager (LCM) on WebSphere (particularly WAS7), you may receive an error that not all components were successfully deployed.  In the server log you may see the following error:

JVMDUMP006I Processing dump event “systhrow”, detail “java/lang/OutOfMemoryError” – please wait.


The default memory settings for the EJB Deploy tool in IBM WebSphere are not enough for deploying the LiveCycle components, and/or the EAR files.


To fix this issue, edit %WAS_HOME%\deploytool\itp\ejbdeploy.bat (or in UNIX). Change -Xms256M -Xmx256M to -Xms1024M -Xmx1024M.  Then re-run LCM.

Note:  There is no need to re-start the appserver instance.

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

How to enable the Javascript debugger in Adobe Reader

Using the debugger with Adobe Reader

 The JavaScript Debugger is normally accessed from the Acrobat Pro user interface, but it can also be triggered to appear in Adobe Reader when an exception occurs.  Though fully supported JavaScript debugging is only available in Acrobat Pro, the following instructions make the complete Debugger functionality available in Adobe Reader on Windows and Mac OS platforms.

For Windows, note that this procedure involves editing the registry. Adobe Systems Incorporated does not provide support for editing the registry, which contains critical system and application information. It is recommended that you back up the registry before modifying it.

  1. Get a copy of the file debugger.js from an installation of Acrobat (plugins folder), the Acrobat Developer Center, or from the SDK (Acrobat 9.0 SDK/JavaScriptSupport/Debugger/debugger.js)
  2. Copy the debugger.js into the Reader 9.0/Reader/JavaScripts folder.
  3. Create key/value pairs in the registry settings, starting at the location HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\JSPrefs\ on Windows as shown in the table below, or in the property list file :Library:Preferences:com.adobe.Reader9.0.plist on Mac OS.

For Mac OS, use an appropriate editor for the property list file, and add the following children under JSPrefs, using Type “Array” in each case: ConsoleOpen, ConsoleInput, EnableDebugger, and Exceptions. Under each of these children, add the following children: 0 (number) and 1 (boolean).

bConsoleInput REG_DWORD 0×00000001
bEnableDebugger REG_DWORD 0×00000001
iExceptions REG_DWORD 0×00000002
(This will break into the Debugger when exceptions occur.)

4. Close and restart Adobe Reader. At this point the Javascript Debugger will be available.

Note: Since Adobe Reader does not provide access to the Debugger through its menu items or the Ctrl + J key sequence, the only ways to access the Debugger are to execute a JavaScript, cause an error, or customize the user interface (for example, you could add a button that runs a JavaScript causing the Debugger to appear).

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

LiveCycle ES: ALC-TTN-011-031: Bootstrapping failed for platform component [DocumentServiceContainer] | clustered environments


 If you are attempting a clustered installation of LiveCycle ES, you may experience errors during the bootstrapping phase of LiveCycle Configuration Manager (LCM) with the following exception in the LCM log:

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log TRAS0014I: 
The following exception was logged com.adobe.livecycle.bootstrap.BootstrapException: ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)
 at com.adobe.livecycle.bootstrap.bootstrappers.DSCBootstrapper.bootstrap(
 at com.adobe.livecycle.bootstrap.framework.ManualBootstrapInvoker.invoke(
 at com.adobe.livecycle.bootstrap.framework.BootstrapServlet.doGet(
 at javax.servlet.http.HttpServlet.service(
 at javax.servlet.http.HttpServlet.service(

LCM may also display error message dialogs such as the following:


In a clustered environment, the cluster caching must be configured correctly and working before the database initialization can complete successfully.


The cluster caching should be configured using one of the options below, depending on whether you are using UDP or TCP caching:
A) UDP caching uses the following Java argument to set a port number: -Dadobe.cache.multicast-port=<port number>
The multicast port must be unique to the LiveCycle ES cluster (that is, the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> on all nodes in the LiveCycle ES cluster.

B) TCP caching uses the following Java argument: -Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress><port number>]
Configure, as a comma-separated list, the locators for all nodes of the cluster. The value for <IPaddress> is the IP address of the computer running the locator, and the value for <portnumber> is any unused port between 1 and 65535 (the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> for all locators.


Here are some further troubleshooting tips for LCM errors related to the DB initialization step:

  • ensure the DB privileges for the DB user match what is specified in the installation documentation
  • ensure sure the user that is starting the application server has R/W access to the GDS and LC TEMP directories (Bootstrap will fail if the permissions are incorrect)
  • it may be necessary to drop the DB and re-create it if there was an error the first time
  • if using WebSphere, test the DB connection from the WAS admin console
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (2 votes cast)

Acrobat/Reader: how to handle the Adobe Approved Trust List (AATL) update dialog


When you use Adobe Acrobat or Reader to open PDF documents that were signed or certified using certificates, you may see the following message:

A new security settings update is available from Adobe Systems.  Would you like to install it now?”  This dialog is a trusted Adobe dialog referring to updates to the root certificate list (AATL) in Acrobat or Reader.


AATL or Adobe Approved Trust List is a program that allows millions of users around the world to create digital signatures. The signatures are trusted whenever the signed document is opened in Adobe Acrobat 9 or Reader 9 or later.  The list of trusted certificates is updated from time to time in case some certificates have been added, renewed, or have expired.

These updates are distinguished from the standard product updates for Acrobat or Reader, which can be triggered by choosing Help > Check For Updates.

Related preferences

If you want to check for certificate updates, choose Edit > Preferences > Trust Manager > Click Update Now under the section Automatic Updates. The same update dialog box opens. Using this option, the certificate updates are loaded from a trusted server.

To enable the automatic update check, choose Edit > Preferences > Trust Manager > Load Trusted Root Certificates From An Adobe Server.  To enable the automatic check without any notification, deselect Ask Before Installing.

Assuming that you have enabled the automatic check, the certificate updates are triggered under the following conditions:

  1. you open a file that has a digital signature, and
  2. you have never checked for updates before, or
  3. you have checked before, but
    1. 28 days have elapsed and
    2. there is a new update available

You can select Yes and the trusted certificate list in Acrobat or Reader is updated. If you want to see the trusted list, choose Open Adobe Reader > Document > Manage Trusted Identities. In the window that opens, choose Display > Certificates. The entire Trusted Certificates list currently installed with your Reader appears.

Enterprise deployment

If you are working in an enterprise environment and want to control these settings for an enterprise deployment, use the Customization wizard to activate or deactivate these options.

Additional information

 reference: (182278250)

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

Configuring Adobe Reader help files for offline use


If you are using Adobe Reader 9 or greater, you may have noticed that the help files are now only available online with an active internet connection to  In Adobe Reader 8 the help files were available within the product itself on your local machine and you did not need an internet connection.

If you do not have an active internet connection on the computers where Adobe Reader 9 and greater is installed, then you will not be able to access the help documentation, and will receive a 404 error in the browser.  This can occur for large enterprises where some machines are not allowed to have an open internet connection for security and data protection reasons.


There are 2 different solutions or workarounds to this issue:

1. Create a local PDF file containing the Help content.

You can reference this PDF file locally, or put the PDF file in a central location where all of your users can access it, i.e. on a network location, or on your internal web server. Here are the example PDF files for Adobe Reader 9 in English and German:

Adobe_Reader_9.0_Help.pdf (English)

Adobe_Reader_9.0_Hilfe.pdf (German)

Note: To create PDF files of the Adobe Reader 9 Help for other languages, go to the Help page for your language on (use a computer where you have Adobe Acrobat installed). Use the Acrobat Web capture plug-in to export the page as a PDF. Then, use Acrobat to fix the links in the PDF file and correct any structural issues.

For Reader X the help documentation is now available online in PDF format, so you can just download the PDF file from:

2. Re-construct the online Help documentation for Adobe Reader within your organization’s intranet environment.

You can deploy the Adobe Reader help pages on your internal web server where everyone in your organization can access them using a browser.

Download the .zip file below and extract it, maintaining the folder structure. Deploy the files to an internal web server. These Help files are available in English and German.

Addendum: Use Customization Wizard to tune the Adobe Reader installation.

In an enterprise environment you may want to configure Adobe Reader for all users to point to the custom Help documentation automatically. You can use the script in this solution to disable the standard Help menu item in Adobe Reader, and replace it with a custom Help menu item pointing to the help documentation from solution 1 or 2 above.

For solution 1 (local PDF file): create a custom folder in your Adobe Reader installation using Customization Wizard (e.g. C:\Program Files\Adobe\Reader <version>\Help), and put the local PDF file in there. Place the WinReader_Local_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

For solution 2 (HTML help files): after putting the Reader HTML files on your local intranet server, place the WinReader_Intranet_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

Now when Adobe Reader is launched on the user’s computer the help menu link will be replaced with your custom link. There may be a short delay before the link is updated after starting Adobe Reader.

reference: (181774134)

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

Acrobat/Reader: Invalid ColorSpace error opening a PDF


 When you try to view a PDF file in Adobe Reader or Acrobat, you see the following error:

“There was an error processing a page. Invalid ColorSpace.”

Try opening other PDF files in the same way and compare the results.  This problem only occurs for certain PDF files.


This error usually occurs viewing PDF files in the browser when there is a problem with the PDF file itself, particularly for PDF files generated with third-party applications or tools.  It will not prevent you from opening the file, but rather, some pages will not be visible.


If you are attempting to open the file through a browser (that is, from an Internet site), try to download the file to your local computer. Then, open it locally using Adobe Acrobat or Reader.  Check the file properties and see if a non-Adobe application was used to create the PDF file.

Here are some suggestions that have resolved the problem for other users:

  • If a non-Adobe application was used, then try using an Adobe application to generate the PDF file again.
  • If it is not possible to re-generate the PDF with an Adobe application, then try to resave it, and/or use the PDF Optimizer tool in Acrobat.  This will often fix any obvious syntax errors in the PDF.
  • If you used an Adobe application other than Acrobat to create the PDF file, ensure you have flattened all layers in the original file before creating the PDF, and check the colorspace settings you have used when exporting the PDF file.  For example, it is not valid to have a DeviceN color space with a colorant value “All”.  You can find details in the PDF Reference Manual (
  • If you have uploaded the file to a website using FTP, ensure you have transferred the file in binary mode.
  • You can try to disable the “Allow Fast Web View” option in the Internet preferences in Adobe Acrobat/Reader.

reference: (182325862)

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

LiveCycle ES: EventPolicyException on IDPSchedulerService during server startup


 If you are running LiveCycle ES (8.x) you may notice the following exceptions in the server log when you restart the application server:

[05.05.11 10:40:43:809 CEST] 00000084 ExceptionCont W Scheduling subscription evaluation resulted in error. 
Reason: There is no active service configuration for service: IDPSchedulerService
[05.05.11 10:40:43:809 CEST] 00000084 EventManagerI E Event Data storage failed. 
Reason: com.adobe.idp.event.policy.EventPolicyException: There is no active service configuration for service: IDPSchedulerService
Caused by: ALC-DSC-023-000: com.adobe.idp.dsc.registry.service.NoActiveServiceConfigurationException: 
There is no active service configuration for service: IDPSchedulerService

The same kind of exception can also refer to other services like EncryptionService, OutputService and so on, depending on the services deployed and used on your installation.  Something has gone wrong during server startup and these services have not finished loading successfully.  There can be many different causes for such behaviour, i.e. the app.server was somehow busy handling other requests or under load during LiveCycle start.


 Restart the application server again, paying attention not to send any requests or calls to the server if possible.


If there are other applications deployed on the same application server as LiveCycle, then try to stop/remove those applications to identify which one may be interrupting the LiveCycle startup.

reference: (182305661)

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