dmcmahon

dmcmahon

Sr. Technical Account Manager at Adobe Systems

Posts by dmcmahon

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

0
294 days
by in FAQ, LiveCycle Enterprise Suite

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 —-\\server\WatchedFolders\folder\stage\Wx840560ff8bdc142771fc0a18\CreatePDF-2012-07-23 12-05-26.643.doc— to —\\server\WatchedFolders\folder\failure\CreatePDF-2012-07-23 12-05-26.643\CreatePDF-2012-07-23 12-05-26.643.doc

---

Read the complete post at David's Blog.

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

0
296 days
by in LiveCycle Enterprise Suite

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

0
297 days
by in FAQ, LiveCycle Enterprise Suite

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)

Adobe Reader cannot open Protected Mode due to a problem with your system configuration.

0
298 days
by in Internal

Issue

If you are starting Adobe Reader and have Protected Mode enabled, you may encounter the following dialog:

“Adobe Reader cannot open in Protected Mode due to a problem with your system configuration. Would you like to open Adobe Reader with Protected Mode disabled?”

Reason

This dialog appears when protected mode cannot be started due to environmental settings on your computer.  It can occur due to anti-virus software conflicts, and/or conflicts with accessibility tools or smart card software and drivers.

Troubleshooting

1. Unsupported configurations:

  • Installing Reader on a mapped network drive.
  • Running Reader on WinXP when the OS is installed in a public folder.
  • Launching Reader in XP-compatible mode on Vista and Win7.
  • Launching Reader by right clicking AcroRd32.exe and choosing Run As.
  • Using PKCS#11 smart cards in signature workflows. Some cards can work in the presence of custom protected mode policies. For a workaround, see below.
  • Collaborating in real time using the Collaborate Live feature.
  • Certain configurations of anti-virus software that have not yet white-listed AcroRd32.exe. See Anti-virus software conflicts below.
  • JS-invoked processes: Launching a process through JavaScript is not allowed with Protected Mode enabled.

2. Antivirus software conflicts:

By default, Adobe Reader X runs in Protected Mode. In certain situations Reader experiences compatibility issues with anti-virus software when that software intercepts some system calls for the Reader sandbox. In these cases, Reader could fail to open or crash after displaying an incompatible-configuration dialog.

For example, Protected Mode is known to be incompatible with:

  • Some Symantec Endpoint Protection configurations. Adobe recommends that users update to Symantec Endpoint Protection 11.0 RU6 MP2 or higher.
  • McAfee VirusScan Enterprise for certain actions in Reader. Known actions include the following:
    • Clicking Help or a Weblink from an embedded Flash widget such as a Portfolio navigator (Fixed 10.1).
    • Launching of some IME tools. Note: Disabling Buffer Overflow Protection can provide a workaround for many McAfee users.
    • Reader sometimes removes a user’s cached credentials when signing out of Adobe.com which could be an issue for a multiuser machine. Fixed 10.1.2 with MVE 8.8.

Adobe is working with anti-virus companies to resolve these problems.

3. Accessibility

For XP only: Accessibility features sometimes doesn’t work. The Read Out Loud feature is unsupported. Therefore, screen readers such as JAWS, Windows Eyes, and Windows Narrator aren’t always able to read PDF content. Much of the Accessibility menus involving things like quick check, change Reading options are removed. Keyboard navigation is not implemented.

Note: When a screen reader like JAWS, Window-Eyes, or Narrator is running when Reader is started for the first time on XP, Protected Mode is disabled. On Vista and Windows 7, screen readers do work normally.

4. P11 smart card workaround

The installation of some smart cards doesn’t work for Reader X users when in Protected Mode. Because Protected Mode sandboxes certain processes that make system calls, smart card installation can fail or result in the “unsupported configuration” dialog appearing. However, a simple workaround is available. Install the smart card software with Protected Mode turned off as follows:

  • Disable Protected Mode by going to Edit > Preferences > General and deselecting Enable Protected Mode at startup
  • Restart Reader
  • Install the smart card software according to the provider’s instructions
  • Re-enable Protected Mode
  • Restart Reader

5. Windows Permissions

You should also check the permissions on the Adobe Reader installation folder.  Protected mode will only work on Windows when the group “BuiltIn\Users” has the following permissions on the Reader installation folder (for a default installation C:\Program Files (x86)\Adobe\Reader 10.0):

  • Read & execute
  • List folder contents
  • Read

Further Information

http://helpx.adobe.com/acrobat/kb/protected-mode-troubleshooting-reader.html

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

0
328 days
by in LiveCycle Enterprise Suite

- 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

0
328 days
by in LiveCycle Enterprise Suite

- 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

0
329 days
by in LiveCycle Enterprise Suite

- 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>\log\server.log

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

---

Read the complete post at David's blog.

LiveCycle ES3: Authentication failed for user (Scheme – Username/Password) Reason: Username or password is incorrect

0
337 days
by in LiveCycle Enterprise Suite

- David McMahon, Sr. Technical Account Manager @ Adobe

Issue

If you are accessing any LiveCycle services and have problems getting a response, you may notice the following warning in the server logs:

WARN  [com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] (Thread-21) 
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect. 
Refer to debug level logs for category com.adobe.idp.um.businesslogic.authentication for further details
 

If you enable DEBUG level logging you will see the following DEBUG information in the log:

DEBUG [com.adobe.idp.common.errors.exception.IDPLoggedException] (Thread-21)
UserM:: [Thread Hashcode: 1796127844] com.adobe.idp.common.errors.exception.IDPLoggedException|
[com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] errorCode:12803 errorCodeHEX:0x3203 message:
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect
 =========== Authentication failure detail report ================== 
 Scheme Type : Username/Password 
 UserId : user 
 Current Thread : ajp-0.0.0.0-11148-8 
 Following are the response details from various authProviders.  
 1 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl - 
 Authentication Failed : Exception stacktraces are avialable at TRACE level 
 Messages collected for this AuthProvider are provided below
      - No local user found with UserId [user] in Domain [DefaultDom]
      - No local user found with UserId [user] in Domain [EDC_SPECIAL]
These warnings in the log may also be accompanied by an Error 500 if you are attempting to call the LC services through a browser/web application.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle Workbench ES3: AttributeNotFoundException trying to create a new process

0
349 days
by in LiveCycle Enterprise Suite

Issue

If you have installed ES3 SP1 (10.0.3) to your LiveCycle ES3 server and Workbench ES3 you may encounter a problem creating new processes.  Selecting the menu item to create a new process does not have any effect.  If you look in the Workbench log file (C:\Users\<YOUR_USER_NAME>\Workbench ES2\.metadata\.log) you may notice the following exception:

!ENTRY org.eclipse.ui 4 0 2012-05-31 21:58:28.424
!MESSAGE Unhandled event loop exception
!STACK 0
ALC-DSC-110-000: com.adobe.idp.dsc.registry.endpoint.EndpointStoreException: endpoint registry failure.
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: parent_oid does not exist on object-type: dsc.sc_category.
 at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(POFAbstractObjectType.java:177)
 at com.adobe.pof.omapi.POFDefaultQuery.addSort(POFDefaultQuery.java:323)
    at com.adobe.pof.omapi.POFDefaultQuery.addSortAsc(POFDefaultQuery.java:372)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointStoreImpl.getEndpointCategories(EndpointStoreImpl.java:219)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointRegistryImpl$2.doInTransaction(EndpointRegistryImpl.java:155)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:357)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(EjbTransactionCMTAdapterBean.java:299)
    at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)

Reason

ES3 SP1 includes some feature enhancements in Process Management.  This involved addition of new columns and tables to the existing ES3 DB schema and hence requires a DB re-initialization when running LCM.

Solution

You should always read the installation steps in the ES3 SP1 readme (link below) before attempting the installation.  In this case, you will need to re-run LCM and select the step to initialize the database.

https://www.adobe.com/products/livecycle/pdfs/lces3_sp1_readme.pdf

You can download ES3 SP1 here:

https://www.adobe.com/cfusion/entitlement/index.cfm?e=lces3_sp1

LiveCycle ES3: ReaderExtensionsService – PKI Intialization failed. Exception: com/rsa/jsafe/provider/JsafeJCE

0
379 days
by in LiveCycle Enterprise Suite

Issue

If you have installed ADEP/LC ES3 (10.0.x) you may notice the following error in the server log when starting the application server:

2012-04-18 15:32:49,500 ERROR [com.adobe.livecycle.readerextensions.ReaderExtensionsService] (main) PKI Intialization failed. 
Exception: com/rsa/jsafe/provider/JsafeJCE
2012-04-18 15:32:49,515 ERROR [org.jboss.ejb.plugins.LogInterceptor] (main) RuntimeException in method: 
public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterLocal.doRequiresNew(
com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.TransactionCallback) 
throws com.adobe.idp.dsc.DSCException:ALC-DSC-099-000: com.adobe.idp.dsc.DSCRuntimeException:
java.lang.ClassNotFoundException: Class name com.rsa.jsafe.provider.JsafeJCE from package com.rsa.jsafe.provider not found.

Reason

This error can occur when the wrong JSAFE and CERTJ JAR files have been imported to your application server.

Solution

Review the installation/configuration documentation and ensure the correct JAR files have been copied to your application server.

For example:

http://help.adobe.com/en_US/enterpriseplatform/10.0/ClusterJBoss/WSf7e9d1e3f353177725b65b451306fc33289-8000.html

reference: (183158539)

« Previous
Next »
dmcmahon's RSS Feed
Go to Top