Posts in Category "ProcessManagement"

LiveCycle7: javax.mail.MessagingException: 554 Mail from [email@mail.com] rejected for policy reasons

Issue

 If you are using the mail/notification functionality in LiveCycle 7, you may find that the mails are never received by the intended recipient.  If you look in the adminui you may find the action has stalled with the following error:

"javax.mail.MessagingException: 554 Mail from <email@mail.com> rejected for policy reasons"

Reason

 This is caused by a lack of privileges to use the SMTP mail server in your organisation.

Solution

Consult your IT department and request permission for the Lc Server to use the SMTP mail server to send email notifications.

reference: (1-28762420)

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

LiveCycle ES: DocumentError submitting a task after migrating to LC ES 8.2.1

Issue

 After you migrate your server from LiveCycle 7 to LiveCycle ES 8.2.1, the following error may appear in the log when you submit a task in Workspace:

javax.ejb.EJBException: EJB Exception: : com.adobe.idp.DocumentError: The document pointing to the file 
"/data/myservermydomain/AdobeDocumentStorage/session_wfattach585520/9084040089345862489" has expired. 
Consider increasing the document disposal timeout.
 at com.adobe.idp.DocumentFileBackend.checkFileExistance(DocumentFileBackend.java:412)
 at com.adobe.idp.DocumentFileBackend.copy(DocumentFileBackend.java:419)
 at com.adobe.idp.Document.passivate(Document.java:1065)
 at com.adobe.idp.Document.passivate(Document.java:1012)
 at com.adobe.idp.Document.<init>(Document.java:565)
 at com.adobe.idp.Document.<init>(Document.java:621)
 at com.adobe.idp.DocumentStorage.persist(DocumentStorage.java:78)
 at com.adobe.idp.taskmanager.dsc.client.task.AttachmentInfoImpl.persistDoc(AttachmentInfoImpl.java:201)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsToTask(CopyAttachments.java:326)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsForward(CopyAttachments.java:291)
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.createTask(TaskManagerServiceImpl.java:467)
 at sun.reflect.GeneratedMethodAccessor1968.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

The process itself stalls when this error occurs.  The error refers to a task attachment that no longer exists in the DocumentStorage directory. This error can occur if the LiveCycle 7 session referencing the target file was deleted, and LiveCycle 8 references to the target file remained. Deleting the LiveCycle 7 session deleted the session_wfattch…. directory, leaving the LiveCycle 8 references pointing to deleted resources.

Solution

Restore the missing files from a backup of your LiveCycle DocumentStorage directory. Or, delete the source task whose attachments are being copied or delete the attachment itself.

reference: (181609130/2630482)

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

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

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: Error 500 in the AdminUI when searching for tasks

Issue

When you search for tasks in the AdminUI (Adminui > Services > LiveCycle Process Management ES > Task Search), the following HTTP error occurs:

Error 500--Internal Server Error 

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.5.1 500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Reason

This error occurs when there is information missing from the database entry for a certain task in the returned list of results. For example, if the PROCESS_NAME value is empty or null for a task in the TB_TASK table. This issue can happen if you use custom code to access the database directly and modify it. It can also occur if you are running a purge utility not supplied by Adobe on the database.

Adobe plans to fix this issue in ES2 SP2 and in ES3.

Solution

This error is a product issue in LiveCycle ES and there are patches available for 8.2.1.2 and 8.2.1.3.  You should contact enterprise support if you require one of these patches.  The issue has been fixed in ES2 SP2 and later versions.

 reference: (181590010/2633888)

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

LiveCycle ES: AdminUI does not show all process names in the process search tool

Issue

 If you are using LiveCycle ES to search for processes using the adminui, then you may notice that not all processes are listed under the “Process Name – Version” drop-down list.  Only processes which are activated in Workbench, and which have process instances in the TB_PROCESS_INSTANCE table in the database, will show up in this drop-down list.

Solution

 Check that the process is activated in Workbench, and then you can run the following SQL query to verify that there are existing process instances for that process:

select distinct service_name, count(id) from tb_process_instance

group by service_name

order by service_name

reference: (181613727)

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

LiveCycle ES: Performance of AdminUI stalled operations and branches list is slow

Issue

 If you are using the Administration UI for Process Management and particularly the stalled operations/branches views in LiveCycle ES 8.2.1, you may notice it takes a long time to return the list of stalled items, particularly if there are many pages to be returned.  In some environments a delay of up to 1 minute can be observed which would be unacceptable for a production environment where the IT team need to be able to react quickly to any stalled instances in production.

This issue has been reported mainly with Oracle databases.

Solution

 The following SQL statements will add indexes to the appropriate tables in the LiveCycle database which will greatly improve the performance of these AdminUI views:

CREATE INDEX status_idx ON tb_action_instance(status);
CREATE INDEX sub_status_idx ON  tb_branch_instance(sub_status);

These indexes need to be created manually in ES (8.x) and ES2 (9.x) as they cannot be applied through ServicePacks.  The issue is fixed in ADEP (ES3).

reference: (181470980/2570677)

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

LiveCycle ES: old XDP templates with invalid WSDL URLs used for running processes

Issue

 If you have migrated from LC7 to LC ES and you were using webservices in your XDP templates in LC7, you may have modified these templates after the mgiration to LC ES to use updated WSDL URLs.  You may notice however that even for process instances started in LC ES the old template version is still being used, and so the invalid WSDL URL which means the tasks will no longer work as expected.

Reason

In LC7 we set both the template_url and hardened_template_url fields in the tb_form_data table to reference the forms used in LC7.  In LC ES we no longer use the hardened_template_url field for new LC ES processes.  However for processes migrated from LC7, we still use this field to reference the exact version of the form that was used to start the process.

The template_url field in tb_form_data contains only the URL to the form in the repository (/Forms/form1.xdp).  The hardened_template_url contains a timestamp with the URL to reference a particular version of the form in the repository, and can therefore referenence different versions of the form (@1271757648748/Forms/from1.xdp).

Solution

If you set the contents of hardened_template_url to empty in tb_form_data, then LC ES will use the template_url by default, which does not have a timestamp, and therefore will always refer to the latest version of the XDP form in the repository.  This will ensure that your updated XDP template with updated WSDL URL will be used for each process.

You can run the following SQL statements first to see how many rows are going to be changed:

Statement1:

This is used to check which forms are being used for active tasks which have a hardened URL set.  These are the forms that are going to be modified by the SQL query, so they should relate to the forms you have modified for the WSDL changes.

SELECT DISTINCT f.template_url, f.hardened_template_url
FROM tb_form_data f
WHERE f.task_id IN (SELECT t.id
 FROM tb_task t
 WHERE t.status < 100)

Statement2:

This is used to ensure that there are no NULL entries in the template_url field.  The template_url field is the field we are going to use to refer to the modified form. Therefore, this statement should not return any rows.  You should probably run this statement again checking for “ “ instead of NULL values just to be sure there are no empty strings in template_url.

SELECT t.form_data_id, f.id, f.template_url, f.hardened_template_url
FROM tb_task t, tb_form_data f
WHERE (f.template_url IS NULL) AND
 (f.hardened_template_url IS NOT NULL) AND
 f.task_id IN (SELECT t.id
 FROM tb_task t
 WHERE t.status < 100)

Statement 3:

If statement2 does not return any rows, then you can run this SQL to actually make the required changes in hardened_template_url.

UPDATE tb_form_data
SET hardened_template_url = NULL
WHERE (template_url IS NOT NULL) AND
 (hardened_template_url IS NOT NULL) AND
 task_id IN (SELECT t.id
 FROM tb_task t
 WHERE t.status < 100)

Notes

If you are unsure about applying these SQL queries to the Database, or if this occuring in a production environment, then contact your support representative to discuss the workaround and to verfiy the results of the first two SQL statements.

reference: (181544186)

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

LiveCycle ES: Error “Stalling action since child process is terminated”

Issue

 Terminating a sub-process in LiveCycle ES (8.x) stalls the sub-process’s parent action with the following message:

2010-04-23 10:55:21,884 ERROR [com.adobe.workflow.AWS] stalling action-instance: 328 with message: Stalling action since child process is terminated

This happens even if the parent action is already complete.  The expected behavior is that the parent action would not be stalled and this is how it worked in LC7.

Solution

This issue has been addressed in LiveCycle ES2 SP2 and later verions.   There is a patch available for this issue for LC ES 8.2.1.2, so contact enterprise support should you require this patch.

reference: (181577032/2610886)

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

LiveCycle ES: RequiredParameterException: Parameter: service-id is required

Issue

 When you try to access a task through the Process Management Process/Task search tools in the administration interface, the following exception occurs:

####<Mar 15, 2010 5:35:34 PM MET> <Error> <HTTP> <server> <managed_server> <[ACTIVE] ExecuteThread: '5' for 
queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1268670934789> <BEA-101017> <
[weblogic.servlet.internal.WebAppServletContext@80d069 - appName: 'adobe-livecycle-weblogic', name: '/PMAdmin', 
context-path: '/PMAdmin'] Root cause of ServletException.
ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.getService(ServiceRegistryClient.java:137)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.taskList(TaskListAction.java:210)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.execute(TaskListAction.java:109)
 ...
ALC-DSC-002-000: com.adobe.idp.dsc.RequiredParameterException: Parameter: service-id is required.
 at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor.java:117)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(TransactionInterceptor.java:74)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTransactionBMTAdapterBean.java:197)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapter_jmbvky_ELOImpl.doBMT(EjbTransactionBMTAdapter_jmbvky_ELOImpl.java:141)
 at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvider.java:95)
 at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInterceptor.java:72)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStrategyInterceptor.java:55)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateInterceptor.java:37)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterceptor.java:109)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
 at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
 at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:91)
 at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:215)
 at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:57)
 at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.invoke(ServiceRegistryClient.java:994)
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.getService(ServiceRegistryClient.java:122)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.taskList(TaskListAction.java:210)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.execute(TaskListAction.java:109)
 ...

Reason

Corruption in the LiveCycle ES database resulting from manual database modifications can cause a “RequiredParameterException” error.  Database corruption can also occur if you are using an external (not from Adobe) purge utility on the LiveCycle database.

Solution

Restore the database from backup to a valid state.

reference: (181491816)

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

LiveCycle ES: Processes in Workspace and AdminUI appearing as “null – 0.0″

Issue

After you upgrade from LiveCycle 7 to LiveCycle ES 8.2.1, some of the processes in the Admin user interface and Workspace appearing as “null – 0.0″.

Reason

Corruption in the LiveCycle ES database causes process names and versions to be listed in the Admin user interface as “null – 0.0.”.  The corruption can be caused if the database content has been modified manually, or if you are using an external (not from Adobe) purge tool on the database.

Solution

Restore the database to a valid state.

reference: (181491899)

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

LiveCycle ES: start_task=0 in TB_TASK table in LiveCycle database

When you develop a custom interface for an upgraded Adobe LiveCycle ES server, you can encounter problems referencing initial tasks for a process. Initial tasks must correctly show the audit history for processes in your custom interface, much the same as Workspace displays them in the tracking view.

In the TB_TASK table in the database, a start_task flag set to “1” appears for initial tasks from a process started through the TaskManager endpoint. However, for some initial tasks, this flag is set to “0.”

 

This behavior is as designed. Start_task is an ES concept that doesn’t come into play when anything from LiveCycle 7 is involved.  Any tasks migrated from LiveCycle 7, and any tasks started in Workspace with a LiveCycle 7 init-form definition in use, have a start_task value of “0.”

To determine whether a task is an initial task in all cases, locate the task that doesn’t have an action instance. That is, one where the action_instance_id=null or zero. If the process instance ID has a value, but the action instance ID doesn’t, then it’s an initial task.

reference: (181494242)

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

LiveCycle ES: com.adobe.idp.DocumentError using the UserPlus QPAC with attachments

Issue

The following error occurs at run-time when you use the UserPlus QPAC from Avoka with attachments in Adobe LiveCycle ES 8.2.1:

javax.ejb.EJBException: EJB Exception: : com.adobe.idp.DocumentError: The document pointing to the file 
"/mydomain/AdobeDocumentStorage/session_wfattach443760/6261454814295665168" has expired. Consider increasing 
the document disposal timeout.
 at com.adobe.idp.DocumentFileBackend.checkFileExistance(DocumentFileBackend.java:412)
 at com.adobe.idp.DocumentFileBackend.copy(DocumentFileBackend.java:419)
 at com.adobe.idp.Document.passivate(Document.java:1065)
 at com.adobe.idp.Document.passivate(Document.java:1012)
 at com.adobe.idp.Document.<init>(Document.java:565)
 at com.adobe.idp.Document.<init>(Document.java:621)
 at com.adobe.idp.DocumentStorage.persist(DocumentStorage.java:78)
 at com.adobe.idp.taskmanager.dsc.client.task.AttachmentInfoImpl.persistDoc(AttachmentInfoImpl.java:201)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsToTask(CopyAttachments.java:326)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsForward(CopyAttachments.java:291)
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.createTask(TaskManagerServiceImpl.java:465)
 at sun.reflect.GeneratedMethodAccessor1243.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

Attachments are stored in the Adobe DocumentStorage directory for LiveCycle 7 and in the GDS directory for LiveCycle 8. An error occurs in LiveCycle 8 if the attachments are stored in the DocumentStorage directory, and are not available in the GDS directory.  This can occur if you have upgraded your server from LiveCycle 7 to LiveCycle ES.

Solution

Manually copy the documents from the LiveCycle 7 DocumentStorage directory to the LiveCycle ES GDS directory.

reference: (181472965)

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

LiveCycle: data variable values lost for migrated LC7 process containing branches

Issue

If you have a process created using LiveCycle 7.x that has been migrated into LiveCycle ES, and it contains branches, you notice that data variables lose their values when moving from one branch to the next.

Consider this example:

 

The example shows two branches, each containing a User activity, which assigns a task to a user’s queue with a form merged with data. Different data is set for each user in the first step in each branch. Therefore User1 opens a form in Workspace and expects to see <BRANCH 1 DATA>; User2 expects to see <BRANCH 2 DATA>.

Note the following variables for this process:

There are separate variables for each branch. However, when the process is run and the flow reaches the first User activity in branch1, it overwrites the data in branch2 (in the branch2_form), which means that both users see <BRANCH 1 DATA> in the form at run time.

Solution

This issue has been fixed in ES SP4 (8.2.1.4), ES3 (10) and later versions.  If you require a patch for this issue for LiveCycle ES 8.2.1. contact Enterprise Support.

reference: (181371341/2528237)

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

LiveCycle ES: How to enable task assignment emails and links to forms in Workspace

Enabling e-mail feature

Adobe LiveCycle Administration user interface has a feature that enables ‘Assigned Task’ e-mails to be sent to users as soon as a task in Workspace is assigned to them. To access or configure this feature for all users, a LiveCycle administrator enables it under: Home > Services > LiveCycle Process Management ES > Server Settings > Task Notifications. The template that is displayed can be customized with the tags as described here: http://livedocs.adobe.com/livecycle/8.2/wb_help/001004.html.

Enabling e-mail link

You can add an HTTP link to the e-mail template that points to the form in Workspace that the user must complete to continue the process. If the user is not already logged in to Workspace, or if their session has expired, they get re-directed to the login dialog before being taken to the form. You can add an HTTP URL to this notification e-mail as described in the documentation here: http://livedocs.adobe.com/livecycle/8.2/wb_help/001330.html.

The default setting for the link is: http://[server name]:[port]/workspace/Main.html?taskId=[value]

The URL http://[server name]:[port]/workspace?taskId=[value] also works.

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

LiveCycle ES: ALC-FDI-001-307: Processing importData operation on source document

Issue

 If you are trying to render a form in Workspace, you may encounter the following exception in the server log:

2007-08-28 16:39:16,604 INFO [com.adobe.livecycle.formdataintegration.server.FormData]
ALC-FDI-001-307: Processing importData operation on source document 182270.
2007-08-28 16:39:16,963 ERROR [com.adobe.livecycle.formdataintegration.client.ImportFormDataException]
ALC-FDI-001-305: Operation aborted: malformed PDF or data.

exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service.
Please review the render orchestration for this process.

This exception can occur especially when you have created a process, dragged an XDP form from the repository in Workbench to the variables view to create a variable.  It will automatically create an xfaForm type variable, and use the Default Render service.

Reason

The Default Render service does not render XDP forms, only PDFs.

Solution

 You must change the render properties manually for the xfaForm variable and choose another render service.

reference: (1568204)

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