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 (2 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)