Posts tagged error messages

LiveCycle Designer ES2: Unable to save old XDPs with external data binding option

Issue

If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager.  If you analyse the files on your local disk, you will notice some tmp files with large file sizes.

Reason

This issue is related to the Data Binding option Allow binding to data not defined by the default data connection.  For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file.  You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:

<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>

---

Read the complete post at Adobe LiveCycle Blog.

Debugging Livecycle Data Services in Livecycle ES

The other day I was spending some time with a client of mine who ran into an issue with a Flex Remoting endpoint in Livecycle/ADEP

Essentially what happened was that within an object tree supposed to be sent from the Flex application to a Livecycle endpoint contained a lot of unexpected null references. Monitoring the AMF remoting traffic with Charles showed however that the data was serialised fine on the Flex side of things. At the other end of the wire though, something clearly went wrong. Even more confusing was that the serialisation seemed to work fine for non-complex data types which led us to the suspicion that the conversion of ArrayCollections to Java generics was setup incorrectly.

Without elaborating on details of coding and configuration switches that can modify how all that works in depth (hint: IExternalizable and java.io.Externalizable are your friends…), I rather want to explain some other configuration settings that a lot of people wouldn’t be aware of, but that are extremely helpful when you run into a possible serialisation problem.

---

Read the complete post at Blog In Black.

LiveCycle ES: ALC-PDG-001-001 The Job Configuration either cant be obtained or is invalid

Issue

If you are using PDFG to process documents on your LiveCycle server you may encounter problems with the conversions accompanied by the following exception in the server log:

GeneratePDFIm A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-Job ID for the submitted createPDF job =CreatePDF-2012-07-23 12-05-26.643.docdfaed6-f564cb-14cb09-338b02-c5fd79-ba0c90

GeneratePDFIm E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error.

AWS  E com.adobe.workflow.engine.PEUtil logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

WorkflowDSCIn E com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error. while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

JobManagerBea E com.adobe.idp.jobmanager.ejb.JobManagerBean doOnMessage JobManagerBean:onMessage():Exception:ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.  Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI “#d6f16633df10d6efd649f0d2becce92c”

FileResultHan A com.adobe.idp.dsc.provider.service.file.write.impl.FileResultHandlerImpl tryPreservingFiles FileResultHandlerImpl —– preserved- source —-serverWatchedFoldersfolderstageWx840560ff8bdc142771fc0a18CreatePDF-2012-07-23 12-05-26.643.doc— to —serverWatchedFoldersfolderfailureCreatePDF-2012-07-23 12-05-26.643CreatePDF-2012-07-23 12-05-26.643.doc

---

Read the complete post at David's Blog.

Could not initialize class com.documentum.fc.client.DfClient while starting livecycle documentum connector services for documentum 6.7 SP1

If you are trying to configure documentum 6.7 sp1 with livecycle and while starting the services for livecycle connector for emc documentum you are getting the below error, then this post may be help ful to you.

java.lang.NoClassDefFoundError: Could not initialize class com.documentum.fc.client.DfClient     at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43)     at ……..

The cause of this error is that the classpath required for connecting for documentum 6.7 SP1 is not correct.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES2: XMLForm.exe terminated abnormally with error code {3}

Issue

If you are using LiveCycle to process PDF documents you may encounter problems displaying/converting forms or PDF documents, accompanied by exceptions similar to the following in the server log:

ProcessResour W com.adobe.service.ProcessResource doProcessExitCleanup BMC024: Service XMLFormService: Process ProcessResource@f1f45(name=XMLForm.exe,pid=0) terminated abnormally with error code {3}

XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage ALC-OUT-002-004: Unable to find service: XMLFormService, error: Connection to failed service.

---

Read the complete post at David's Blog.

LiveCycle ES2: This scheduler instance (SchedulerName) is still active but was recovered by another instance in the cluster

Issue

If you are working with LiveCycle ES2 in a cluster you may notice the following message in the server log:

org.quartz.impl.jdbcjobstore.JobStoreSupport findFailedInstances “This scheduler instance (<SchedulerName>) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior”.

Reason

This exception often occurs when the clock times on the cluster nodes are not synchronized.  If the clock times on cluster nodes are more than 1.7 seconds out of synch you will start to see these Quartz messages in the log.

Solution

Synchronize the time on all cluster nodes and then restart the cluster.  The messages should no longer appear in the log.

reference: (1647846)

How to Fix Error Code 19457 BackingStoreException

Recently I worked on troubleshotting an issue for a customer who was encountering issues while deploying components.

The following error was seen in the LCM log and no error was seen in the server log:

============

[2012-06-29 03:55:54,681], SEVERE, main, com.adobe.livecycle.lcm.cli.LCMCLI, Failed to deploy component.

Cannot connect to service container.

com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-201]: Failed to deploy component.

Cannot connect to service container.

at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:303)

…..

…..

…..

at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)

Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.

at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.throwExceptionHandler(SoapAxisDispatcher.java:211)

…..

…..

…..

at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:292)

… 5 more

Caused by: com.adobe.idp.common.errors.exception.IDPException| [com.adobe.idp.um.config.util.CachedConfigManager] errorCode:19457

errorCodeHEX:0x4c01 message:Error occured while initializing the configuration

chainedException:java.util.prefs.BackingStoreExceptionchainedExceptionMessage:null chainedException

trace:java.util.prefs.BackingStoreException

at com.adobe.idp.config.AdobeLocalPreferences.flush(AdobeLocalPreferences.java:223)

…..

…..

…..

at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatcher.java:127)

… 10 more

==============

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES3: CertificateException: Terminating SSL connection – The server is not trusted

- David McMahon, Senior Technical Account Manager @ Adobe

Issue

If you are using LiveCycle ES3 Digital Signatures to apply signatures to PDF documents using a timestamp (TSP) server you may encounter the following exception:

WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) Exception from transport package   (in the operation : internalSendReceive)

Caused By: java.security.cert.CertificateException: Terminating SSL connection – The server is not trusted(Alerts.java174)

Caused By: Terminating SSL connection – The server is not trusted(PKISocketFactory.java255)

---

Read the complete post at David's blog.

LiveCycle ES3: PKIException: ALC-DSS-310-033 Invalid timestamp mime type

- David McMahon, Senior Technical Account Manager @ Adobe

Issue

If you are using LiveCycle ES3 Digital Signatures to sign PDF files using a timestamp server (TSP) you may encounter the following exception:

2012-06-22 06:48:31,608 WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) ALC-DSS-310-033 Invalid timestamp mime type. (in the operation : createTimestamp)

---

Read the complete post @ David's blog.

LiveCycle: JBoss stopped logging in server.log

- David McMahon, Senior Technical Account Manager @ Adobe

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>server<profile>logserver.log

If the JBoss log is no longer logging activity you should check the following:

---

Read the complete post at David's blog.

Go to Top