Ameeth Palla

Ameeth Palla

Ameeth Palla is a Technical Account Manager for the Adobe Digital Enterprise Platform team. Previously he was in the role of a Technical Expert for LiveCycle for the the Technical Response Team (what is now the Sr.Support Architect role). In both roles, Ameeth handled several technical issues for various customers and worked closely to aid with Sales POC's, Development/Implementation and Manitenance of LiveCycle/ADEP Projects. In the current role he handles several high profile customer accounts and provides guidance in all aspects of LiveCycle/ADEP. Also he is a Certified LiveCycle ES2.5 Process Management Expert. He was nominated for the 'Adobe Founders Award' and the 'Excellence Matters' award for LiveCycle/ADEP BU.

Home page: http://www.linkedin.com/in/gettoknowameeth

Posts by Ameeth Palla

How to Fix Error Code 19457 BackingStoreException

0
328 days
by in FAQ, LiveCycle Enterprise Suite

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.

Managing Process Recordings in LiveCycle

0
329 days
by in LiveCycle Enterprise Suite

Process Recordings are stored in the /GDS/audit/workflow/ directory.

By default, the maximum number of recordings that can be stored is set to 50.

The value for maximum number of recordings can be configured via Workbench:

---

Read the complete post at Adobe LiveCycle blog.

Canonical name ‘vs’ User ID

0
332 days
by in FAQ, LiveCycle Enterprise Suite

Issue:

Recently I worked on a customer issue where in they were seeing an error when the user logged into their AIR client on MAC and was unable to access the application.

The error seen was :

LC_AuthenticateUser Error: com.adobe.idp.um.api.UMException| [com.adobe.idp.um.api.impl.AuthenticationManagerImpl] errorCode:16386 errorCodeHEX:0×4002 message:user_identifier:Z027223 domain:DefaultDomcom.adobe.idp.common.errors.exception.IDPException| [com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean] errorCode:13316 errorCodeHEX:0×3404 message:user_identifier: Z027223 domain:DefaultDom;

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification

0
334 days
by in LiveCycle Enterprise Suite

Issue:

For LC ES3 – the “Preparing to Install Adobe LiveCycle ES3″ Guide – section 2.2.9 (Additional requirements for Connector for IBM FileNet) – for FileNet Connector configuration is unclear.

The section reads as below -

=======

IBM FileNet 5.0

If LiveCycle is connecting to IBM FileNet 5.0 Content Engine, you must install the Content Engine Java Client. Use the IBM FileNet 5.0 content engine client installer located by default in C:\Program Files\FileNet\CEClient. During installation, select at least one of the components from Application Engine or Process Engine on the component selection screen.

For IBM FileNet 5.0 Process Engine, you must install the IBM FileNet 5.0 Process Engine Client located by default in C:\Program Files\FileNet\BPMClient. During installation, select the Other option on the component selection screen.

=======

Questions:

The above text in red does not clearly answer the below questions:

- Does this mean that during the Java Client installation, the user needs to point to an existing Application Engine installation (which maybe be on a different server than LiveCycle)?

- Or does this mean that the Java Client has to be installed where the Application Engine resides (which it already is) and so this step can effectively be skipped?

- Or does this mean that another instance of Application Engine needs to be installed on the same server as LiveCycle?

---

Read the complete post at Adobe LiveCycle Blog.

Process ID value comes up as “-1″

0
334 days
by in FAQ, LiveCycle Enterprise Suite

- Ameeth Palla, Technical Account Manager @ Adobe

Issue: Recently I worked on an issue for a customer who reported a problem with Process ID value becoming “-1″.

Scenario: Customer had a process where they were naming the output file using a combination of “Process ID + time-stamp”. They reported that the value of the output filename was coming up as “-1+time-stamp” for some files.

Trouble-shooting: Upon reviewing their process, the design was – A long-lived process takes an input from a watched-folder end-point and checks to see if the incoming file is a TIFF, MS Word document or XML data file. If the input was any other format other than XML, then these files would be converted to PDF’s and the output file would be named as “Process-ID+timestamp” and stored in a directory. If the input file was an XML data file then it would be sent to a sub-process and merged with a form-template and flattened and then named as “Process-ID+timestamp” and stored in the same output directory. By running some tests, we could see that the file name would come out as “-1+timestamp” only when the input file was an XML data file.

---

Read the complete post at Adobe LiveCycle Blog.

Dealing with – Tried to assign more tasks [xxx] than the maximum tasks per transaction threshold [110]. – error message

0
393 days
by in FAQ, LiveCycle Enterprise Suite

- Ameeth Palla, Technical Account Manager @ Adobe

I had recently worked on an issue where the process had an ‘Assign Mutiple Tasks’ step in it. It was assigning the same task to many users (>110). During runtime, when this step was executed, it would fail with the below error message and stack trace:

Tried to assign more tasks [xxx] than the maximum tasks per transaction threshold [110].

---

Read the complete post at Adobe LiveCycle Blog.

Ameeth Palla's RSS Feed
Go to Top