Posts tagged "exception"

CQ5.5 SP1: Inserting variables in newsletters doesn’t work in Chrome

Posted on March 18, 2013 by dmcmahon | Comments (0)

Issue

If you are using Chrome with CQ5.5 SP1 and attempting to insert variables into newsletters as detailed below, you may notice that the variables are not inserted as expected.

1. Open Chrome and go to http://localhost:4502/content/campaigns/geometrixx/monthly_newsletter.emailclient.html
2. Double click on a text component to open the Edit component window.
3. Click on insert to insert a variable, for example ‘Firstname’.

Result: The variable isn’t inserted, and Chrome logs a javascript error: “Uncaught error: Index size error: DOM Exception 1″.

Solution

This issue is fixed in CQ5.5 SP2.1.  Chrome is only supported in CQ5.5 SP2.1 and later versions, as we made many changes to offer Chrome support in these versions.

Workaround

The procedure above works fine in Firefox and Internet Explorer.

reference: (44087/CQ5-16244)

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

LiveCycle ES 8.2.1: “A non-retryable Exception has occurred” assigning tasks

Posted on August 2, 2010 by dmcmahon | Comments (0)

Issue

When you assign a task to a new user created in LDAP and synchronized with LiveCycle, an exception occurs. The error occurs when you assign a task before the new user has logged into Workspace.

2008-07-22 07:51:45,497 ERROR [com.adobe.workflow.AWS] stalling action-instance: 688 with message: A non- retryable Exception has occurred:

Attribute: out_of_office_user_id on object: workflow_user:[DCC77BA9-D281-1D96-D57E-EF9C5B804811] has not been loaded.;

CausedByException is: Attribute: out_of_office_user_id on object: workflow_user:[DCC77BA9-D281-1D96-D57E-EF9C5B804811] has not been loaded.

If the user has logged in to Workspace, the task is assigned without any problems or errors.

Solution

This issue is resolved in LiveCycle ES 8.2.1.1 and later. There is a patch available for LiveCycle ES 8.2.1; contact Enterprise Support to obtain the patch.

Additional information

This problem occurs with the Oracle database. The Oracle POF adapter doesn’t work when a Proxy Object loads for a record not in the proxied table without populating all attributes in the query.

reference: (180316378/1875224)

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

LiveCycle ES: “ALC-UPG-040-005: Exception Migrating Workflow Tasks” Error while migrating the DB in LCM

Posted on December 17, 2009 by dmcmahon | Comments (1)

Issue

When migrating from a LC7 to a LC ES server, you may receive the following exception during the “Migrating Essential Data” step in LiveCycle Configuration Manager:

ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]
com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: Internal error:
ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]
at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:320)
at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateCriticalData(WorkflowUpgradePlugin.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.adobe.livecycle.upgrade.control.PhaseRunner.run(PhaseRunner.java:217)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error:
ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]

Reason

This will occur when a task has been started by opening a form in Form Manager, but a process was never initiated, probably because the user just closed the form again without submitting. The task has no corresponding entry in the TB_ASSIGNMENT table in the DB.

Solution

The solution in this case is to delete the task entry manually from the database, as it does not affect any running processes. This is a very rare case and should not show up at all in most installations. Here is an SQL statement you can use to search for such tasks in the DB before running LCM.

_____________________________________________

select * from tb_task tsk where
not exists (select 1 from tb_assignment assign where assign.id=tsk.current_assignment_id) or ((tsk.process_instance_id > 0) and
not exists (select 1 from tb_process_instance proc where proc.id=tsk.process_instance_id)) or ((tsk.action_instance_id > 0) and
not exists (select 1 from tb_action_instance act where act.id=tsk.action_instance_id)) or
not exists (select 1 from edcprincipalentity ent where ent.id=tsk.create_user_id) or
not exists (select 1 from tb_form_data form where tsk.form_data_id=form.id)

_____________________________________________

reference: (180999333/2360548)

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

LiveCycle 7: “Directory Exception javax.servlet.jsp.JspException” accessing webservice portal

Posted on August 24, 2009 by dmcmahon | Comments (0)

Issue

When you try to access the web service portal in JBoss (http://localhost:8080/services/) using LiveCycle 7, you may receive the following error:

Web Service Directory Services
Directory Exception javax.servlet.jsp.JspException: 
An error occurred while evaluating custom action attribute "items" with value "${directoryBean.deployedServices}": 
An error occurred while getting property "deployedServices" from an instance of 
class com.adobe.workflow.service.WorkflowServiceDirectoryBean (java.lang.NullPointerException)

Solution

 Add the following lines to the service XML file: [appserver root]/server/all/conf/jboss-service.xml:

_____________________________________

<-- Isolate all ears in their own classloader space -->
<attribute name="Isolated">true</attribute>
<-- Enforce call by value to all remote interfaces -->
<attribute name="CallByValue">true</attribute>

_____________________________________

reference: (180009712)

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