Archive for December, 2011

LiveCycle ES: NoSuchMethodError installing/uninstalling patches

Issue

If you are installing/uninstalling patches or service packs for LiveCycle ES you may encounter the following exception in the server log:

Caused by: javax.ejb.EJBException: Unexpected Error
java.lang.NoSuchMethodError: com.adobe.pof.omapi.POFQuery.addFilter(Ljava/lang/String;Ljava/lang/String;IJ)Lcom/adobe/pof/omapi/POFFilter;
    at com.adobe.idp.event.util.EventDBHelper.getNewAsynchEventIDs(EventDBHelper.java:5704)
    at com.adobe.idp.event.notification.NotificationManagerImpl$2.doInTransaction(NotificationManagerImpl.java:375)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:342)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(EjbTransactionCMTAdapterBean.java:284)
    at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.in

This exception will usually occur following the EAR deployment.

Reason

When you install/uninstall patches for LiveCycle ES they will update files included in the EARs and also the DSC component files which are then deployed as services.  The versions of the EARs and components deployed must match, otherwise you will see this exception.  If the versions do not match, then the components may be referencing Java methods which were added/modified in the later patch, and therefore not available in the EARs or vice versa.

This exception will often occur directly after the updated EARs are deployed but the components have not yet been updated, as these are two separate steps in LCM.  Even after deploying the updated components the exception may still occur, as they are still loaded in the cache.

Solution

Ensure you have successfully completed deployment of the updated EARs and components.  If the error is still occurring, then restart your application server and perhaps even clean the application server temp files before restarting.  This should refresh all of the deployed services in the cache and the error should not occur.

reference: (182876692)

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

LiveCycle ES: how to uninstall a patch or service pack

Issue

If you have installed a patch or service pack for LiveCycle ES you may need to uninstall this at a later date, or you may have a requirement to document this process fully as part of your installation/configuration documentation.

This information is outlined in the readme file provided with each patch or service pack, and I will just expand on that giving some more detail here.  In this example I will discuss uninstalling LiveCycle ES Update 1 SP4 (8.2.1.4), to go back to LiveCycle ES Update 1 SP3 (8.2.1.3) on Windows.

Preparation

Before installing/uninstalling any patch you should take note of the current versions installed so you can verify your steps have been successful later.  Take a screenshot of the About screen, and the Service Management screen from the AdminUI.

AdminUI > About screen (note the Patch version “SP4″ and Service Pack version “8.1.5192.1.284202.47”, and the Patch level of each deployed component “SP4″):

AdminUI > Services > Applications and Services > Service Management screen (note the Component Versions “8.1.5192.1.284202.47”, “8.1.5193.1.279333.70”, etc…):

Before running through the uninstallation process it would advisable to make a backup of your existing configuration in case any unexpected problems should arise.  To do this, you should make a copy of the entire LiveCycle installation directory (excluding the MySQL folder if it exists within the LiveCycle directory).

You should also take note of the following configuration properties from AdminUI > Settings > Core System Settings > Configurations:

  • Location of temp directory
  • Global document storage root directory (Changing this value will result in data loss unless you also manually move the data)
  • Location of the Adobe Server Fonts directory
  • Location of the System Fonts directory

If you have LiveCycle Content Services ES installed, you should also have the location of the Content Services root directory which you entered during the original installation/configuration process.

Uninstallation

1. It is possible to leave your application server running for the moment, however you should stop your application server (JBoss, WebSphere, Weblogic) if possible.

2. Delete any files listed in <LiveCycle_HOME>\patch\SP4\backup_SP4\FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt from the <LiveCycle_HOME> directory.  These are new/updated files which were added with this service pack/patch.  To go back to a pre-SP4 state, we need to remove these files.

3. Copy all files under <LiveCycle_HOME>\patch\SP4\backup_SP4\ and paste them into their corresponding folder under the <LiveCycle_HOME> directory.  This will overwrite the files which were updated by SP4 and restore them back to the SP3 state.  This can include files in the configurationManager, deploy, LiveCycle_ES_SDK, and jboss folders.

4. Goto <LiveCycle_HOME>\licenses and edit each of the xxx.properties files.  You will have a .properties file for each component installed, so you will need to perform the 2 steps below for each .properties file.

i). Delete the last PatchID section from the bottom of each file (in this case the entire SP4 section highlighted):

ii). Change the PatchVersion value at the top of the file to match the last PatchID now at the bottom (in this case SP3, as we just deleted SP4):

5. As we have now restored all the files in the <LiveCycle_HOME> directory, and have a backup of the SP4 configuration, we can now delete the EAR files in the <LiveCycle_HOME>\configurationManager\export directory.

6. Run Configuration Manager (LCM) and select the LC components you wish to configure.

7. Select the following tasks on the task selection dialog:

  • Configure LiveCycle ES
  • Deploy LiveCycle ES EARs (optional, you can also deploy the EARs manually once they are configured in the export folder, before initializing the DB)
  • Initialize LiveCycle ES database
  • Deploy LiveCycle ES components
  • Validate LiveCycle ES component deployment

8. Follow all the dialogs and check the values of the local folders which you noted in the preparation tasks.

9. Once LCM has successfully completed deploying the EARs and components, you should check the version numbers again in the AdminUI to ensure they now show the original version numbers (in this case SP3).

AdminUI > About screen:

AdminUI > Services > Applications and Services > Service Management screen:

Note: if you see NoSuchMethodErrors in the server log, this would indicate that the DSC components do not match the version of the EARs deployed (e.g. the components are still SP4, whereas the EARs are SP3 or vice versa).  Ensure you have successfully completed the EAR and component deployment, and you may need to restart your application server and perhaps even clean the application server temp folders to resolve such exceptions that appear in the server log.

reference: (182873522)

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

LiveCycle ES: CONTENT INTEGRITY ERROR using Content Services

Issue

If you are working with Content Services ES you may notice the following exception in the log files:

ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.
ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.
ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.
 at org.alfresco.repo.admin.ConfigurationChecker.check(ConfigurationChecker.java:312)
 at org.alfresco.repo.admin.ConfigurationChecker.access$000(ConfigurationChecker.java:72)
    at org.alfresco.repo.admin.ConfigurationChecker$1.execute(ConfigurationChecker.java:178)
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:278)
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:227)
    at org.alfresco.repo.admin.ConfigurationChecker.onBootstrap(ConfigurationChecker.java:182)
    at org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:62)

Reason

This exception will occur when the data in the database is no longer synchronized with the data in the file system data store.  Both must remain synchronized at all times, otherwise data loss will occur.  It is part of the maintenance tasks to ensure that the following items are backed up regularly at the same time:

  • GDS document store (file system/network location)
  • Content Services data store (file system/network location)
  • Database schema

This information is described in detail with instructions in the LiveCycle Administration guide:

http://help.adobe.com/en_US/livecycle/8.2/admin_guide.pdf#page=129

If the data in the Content Services data store is no longer synchronized with the data in the database, then this exception is thrown, as data integrity has been compromised.  This can happen if another server/user has access to the file data store and makes changes, or if the data in the database is modified by another user/application.

It can also occur while performing configuration changes to your LiveCycle installation if the deployment of these changes quits unexpectedly leaving the database and local data stores out-of-synch.

Solution

To resolve this situation you will need to restore the components above from the last valid configuration.

If this is a fresh installation of LC content services, then you can drop the Content Services tables in the database, delete any content in the data store, and re-try the deployment. The following technote describes which tables you need to drop (i.e. it gives you the SQL commands to run):

http://kb2.adobe.com/cps/405/kb405444.html

The Content Services tables in the database get created while the adobe-contentservices.ear file is being deployed (not during database initialization).  Once you have cleaned the DB and the data store, simply re-start the application server with the content services EAR file, and the tables will be re-created.

reference: (182870106)

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

LiveCycle ES2: ALC-RES-001-008 Unable to apply the requested usage rights to the given document

Issue

If you are trying to apply usage rights to a document you may encounter the following error in the server logs:

servlet       I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I:
[LiveCycleES2] [/ReaderExtensions] [ApplyRightsServlet]: Initialization successful.

PKIException  W com.adobe.livecycle.signatures.common.CommonBaseException logException
ALC-DSS-310-048 Could not sign PKCS7 data (in the operation : sign)
    Caused By: com.rsa.jsafe.provider.JSA_RSAPrivateKey incompatible with com.rsa.jsafe.provider.JS_PrivateKey(null-1)

PKIException  W com.adobe.livecycle.signatures.common.CommonBaseException logException
ALC-DSS-310-048 Could not sign PKCS7 data (in the operation : sign)
    Caused By: ALC-DSS-310-048 Could not sign PKCS7 data (in the operation : sign)
        Caused By: com.rsa.jsafe.provider.JSA_RSAPrivateKey incompatible with com.rsa.jsafe.provider.JS_PrivateKey(null-1)

CryptoProvide E com.adobe.livecycle.signatures.common.CommonBaseException logException
ALC-CRP-302-002 There was an error computing the PKCS7 signature. (in the operation : sign)
    Caused By: ALC-DSS-310-048 Could not sign PKCS7 data (in the operation : sign)
        Caused By: ALC-DSS-310-048 Could not sign PKCS7 data (in the operation : sign)
            Caused By: com.rsa.jsafe.provider.JSA_RSAPrivateKey incompatible with com.rsa.jsafe.provider.JS_PrivateKey(null-1)

ReaderExtensi E com.adobe.livecycle.readerextensions.ReaderExtensionsImplementation applyUsageRights
ALC-RES-001-008: Unable to apply the requested usage rights to the given document.

Reason

This error can be caused after you have installed some updates (i.e. patches) to the LiveCycle components and have completed running LiveCycle Configuration Manager (LCM).

Solution

The solution in this case is to simply restart the application server (JBoss, WebSphere or Weblogic).  Then the ReaderExtensions service will be working again.

reference: (182819171)

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

LiveCycle ES2: ALC-LCM-030-300 Error while deploying LCA

Issue

If you are running LiveCycle Configuration Manager (LCM) and deploying the components to a WebSphere server you may receive an error when it attempts to deploy the LCAs.  If you check in the lcm.0.log you may see the following exceptions:

SEVERE, Thread-18, com.adobe.livecycle.lcm.feature.deployment.DeployLCAs,
 Error while deploying LCA /opt/adobe/adobe_livecycle_es2/deploy/adobe-livecycle-launchpad.lca.
 com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-300]:
 Error while deploying LCA /opt/adobe/adobe_livecycle_es2/deploy/adobe-livecycle-launchpad.lca.
 at com.adobe.livecycle.lcm.feature.deployment.DeployLCAs.deployLCAFile(DeployLCAs.java:261)
 at com.adobe.livecycle.lcm.feature.deployment.DeployLCAs.deployLCAFiles(DeployLCAs.java:177)
 at com.adobe.livecycle.lcm.feature.deployment.DeployLCAs.deployLCA(DeployLCAs.java:146)
 at com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask$ActualTask.<init>(DeployDSCsTask.java:99)
 ...
 Caused by: ALC-DSC-005-000: com.adobe.idp.dsc.DSCNotSerializableException: Not serializable
 ...
 Caused by: ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
 ...
 Caused by: com.adobe.livecycle.design.client.DesigntimeServiceException: Error Removing the application :Invocation error.
 ...
SEVERE, Thread-18, com.adobe.livecycle.lcm.feature.deployment.DeployLCAs,
 Error while deploying LCA /opt/adobe/adobe_livecycle_es2/deploy/adobe-process-management-system.lca.
 ...
SEVERE, Thread-18, com.adobe.livecycle.lcm.feature.deployment.DeployLCAs,
 Error while deploying LCA /opt/adobe/adobe_livecycle_es2/deploy/adobe-guides.lca.
 ...
SEVERE, Thread-18, com.adobe.livecycle.lcm.feature.deployment.DeployLCAs,
 Error while deploying LCA /opt/adobe/adobe_livecycle_es2/deploy/adobe-mobile.lca.
 ...
SEVERE, Thread-18, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask, Task failed

Reason

These errors can occur when the LiveCycle EAR files have not been deployed correctly to WebSphere.  If you have deployed the EAR files manually after they have been configured in LCM, then you have forgotten to enable the “Generate Default Bindings” option while deploying the EAR files.

Solution

When you deploy each EAR file ensure you select the option to “Generate Default Bindings” in the WebSphere console:

This is described in the documentation also for manually deploying the EAR files to WebSphere:

http://help.adobe.com/en_US/livecycle/9.0/install_websphere.pdf#page=123

reference: (182816166)

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

LiveCycle ES: java.net.BindException in server log following SuSE Linux update

Issue

You may errors similar to the following in your server log:

WARN  [org.jboss.system.ServiceController] Problem starting service jboss:service=WebService
java.lang.Exception: Port 8083 already in use.
...
[org.jboss.system.ServiceController] Problem starting service jboss:service=Naming
java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
Caused by: java.net.BindException: Address already in use
...
[org.jboss.system.ServiceController] Problem starting service jboss:service=invoker,type=jrmp
java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
Caused by: java.net.BindException: Address already in use

Reason

These errors and related non-functioning of the LiveCycle components deployed is usually the result of an operating system update for the bind name server.  These updates are provided by opensuse.org and may have been installed in the OS by the administrators.

These updates will break the functionality in any running LiveCycle server as it affects the communication protocols.

Solution

You will need to restart the entire Linux operating system to allow the updates to be successfully propagated into all the relevant applications.

reference: (182815638)

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

Acrobat/Reader: Some special characters are not escaped in XML submission to a HTTP URL

Issue

If you are using XFA forms to submit/export data in XML format from Acrobat/Reader, you may notice that some of the special characters (<>”&’) are not being escaped in the XML output. This can lead to problems if this XML is then to be parsed server-side or used by custom applications.

Explanation

The XML data submitted/exported from Acrobat/Reader escapes characters like & (ampersand) > (greater than) and < (less than), but not ” (quote) or ‘ (apostrophe).  Custom applications may encounter problems when trying to parse XML data containing apostrophe or quote characters, if they are expecting these characters to be escaped like for <, > and &.

There are 5 predefined entity references in XML (http://www.w3schools.com/xml/xml_syntax.asp):

&lt;  < less than
&gt;  > greater than
&amp;  & ampersand
&apos;  ‘ apostrophe
&quot;  “ quotation mark

Note: Only the characters “<” and “&” are strictly illegal in XML. The greater than character is legal, but it is a good habit to replace it.

So the XML specification recommends to replace only “<“, “&” and “>”.  It does not require quote and apostrophe characters to be escaped for element values.  Therefore all conformant XML parsers should be able to handle this.

Quotes and apostrophes only need to be escaped if they occur in an attribute value surrounded by the same single or double-quote character.  In this case, Acrobat/Reader will escape the quote or apostrophe characters as required.

Notes:

You can use a regular button with script like “event.target.submitForm({cURL: url, cSubmitAs:”XML”});” to submit data in XML format to a specific URL.

reference: (182809204/3054499)

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