Posts in Category "ProcessManagement"

LiveCycle ES: ALC-DSC-504-000 TaskManager DSC not installed error

Issue

 When attempting to import an LCA archive in the adminui you may receive the following exception:

2008-03-18 09:23:11,808 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: 
public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.
EjbTransactionCMTAdapterLocal.doRequiresNew(com.adobe.idp.dsc.transaction.TransactionDefinition,
com.adobe.idp.dsc.transaction.TransactionCallback) throws 
com.adobe.idp.dsc.DSCException:ALC-DSC-504-000: 
com.adobe.idp.dsc.registry.DataTypeNotFoundException: 
DataType: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance version:0.0 not found
 at com.adobe.idp.dsc.registry.datatype.impl.DataTypeRegistryImpl$1.doInTransaction(DataTypeRegistryImpl.java:94)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:336)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequired(EjbTransactionCMTAdapterBean.java:259)
 at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

This exception occurs when the TaskManager DSC service is not deployed. ProcessManagement usually installs this TaskManager component.

Solution

You should check the deployment directory for your application server and confirm that the file “adobe-taskmanager-dsc.jar” is deployed.  Then goto the adminui and ensure the service is running under Services > Applications and Services.

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

LiveCycle ES: “ALC-WKS-005-029: A problem occurred in the Submit Service” error submitting a form in Workspace

Issue

 When you are trying to submit a form in Workspace with LiveCycle ES you may receive the following error in the Workspace UI:

Task 101 has failed to submit. (ALC-WKS-007-072)

and the following exception in the server log:

2009-06-24 11:51:12,968 WARN [com.adobe.workspace.tasks.com.adobe.workspace.tasks.DocumentSubmitServlet] 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
flex.messaging.MessageException: 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
at com.adobe.workspace.AssemblerUtility.createMessageException(AssemblerUtility.java:384)
at com.adobe.workspace.tasks.DocumentSubmitServlet.doPost(DocumentSubmitServlet.java:230)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.adobe.workspace.events.RemoteEventClientLifeCycle.doFilter(RemoteEventClientLifeCycle.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)

Reason

 This is due to an incorrect configuration in the submit service settings.

Solution

 The submit service for the form variable should have the following configuration:

reference: (181013769/2365358)

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

LiveCycleES: ALC-WKS-007-040 error in Workspace trying to open a form

Issue

When trying to open a form in Workspace you may receive an error ALC-WKS-007-040, and the form will not be displayed.

Reasons

This error can occur in many different situations.  You should analyse the server log and see what the cause of the exception is.

Here are some examples where this error can occur:

  1. The form as specified in the render options cannot be found, or the render options are incorrect.  This situation would often be accompanied by the following errors in the log:
    • ALC-FRM-001-058: Cannot retrieve the resource from Repository Path
    • ALC-FRM-001-035: Failed to load TemplateStream for FormQuery=
    • ALC-WKS-005-028: A problem occurred in the Render Service
  2. It is using some cached version of the form, and the cached version is then deleted.  You may see the following errors in the logs in this situation:
    • EJB Exception: : com.adobe.workflow.template.document.TemplateNodeNotFoundException: Template object: A1239961657505 not found.
  3. The root cause in the exception trace is: com.adobe.idp.taskmanager.dsc.client.task.TaskNotFoundException: no task found for task ID = xxxx
  4. “The application has failed to start because omniDynamic411_vc8_rt.dll was not found.” error received in Windows.

Solutions

Follow the respective solutions related to the situations above:

  1. Verify your render options in the xfaform variable.  Use the parameters as specified in the online help:
  2. Upload the form again to the Resources view in Workbench, or create a new folder, and change the xfaform variable to reference the new form location.
  3. This error can occur in numerous situations following a migration from LC7 to ES.  Solutions can be found under:
  4. Refer to solution in:

Additional Information

If you are upgrading a LC7 process which contains a User QPAC, to ES, there are some manual steps you should follow to be able to make the process work in ES.

You will need to change the lc7form variable to an xfaform variable, remove the init-form, configure endpoints and so on.  You can find a detailed guide to this process under:

http://livedocs.adobe.com/livecycle/8.2/wb_help/000397.html

reference: (180890414)

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

LiveCycleES: description of manual tasks after upgrading from LiveCycle 7

For anybody looking for more information about migration from LiveCycle 7.x to LiveCycle ES, there are some manual steps involved which you should know about so that you can plan your resources and testing around this.

The main manual tasks are:

  1. Upgrade process using Upgrade tool
  2. Delete init-forms
  3. Change each form variable type from ‘lc7form’ to ‘xfaform’
  4. Set render/submit service for each xfaform variable
  5. Remapping User QPAC’s input and output variables (in LiveCycle 7.x, the input can be a variable name, but in LiveCycle ES, it must be an xPath expression), if multiple User QPACs are used in a process, you have to remap the input/output one-by-one.
  6. Activate the new process version

You can find more information on each of the steps above in the LiveCycle Workbench ES documentation below.
Upgrading processes in LiveCycle Workbench:
http://livedocs.adobe.com/livecycle/8.2/wb_help/wwhelp/wwhimpl/js/html/wwhelp.htm
…see the section under Creating Processes > Upgrading processes, particularly the section on Performing Upgrades.

For LiveCycle Workbench ES2.5 you should read the following documentation:
http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb4e389e8612826be7e6a-8000.html

More information about the tasks involved in upgrading a process that uses an init-form bound to a schema:
http://kb2.adobe.com/cps/404/kb404420.html

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

LiveCycle: NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl

Issue

After performing an upgrade from LC7 to ES 8.2.1 and then trying to run a process in the LC7 compatibility layer, the process instance may stall at a User component with the following exception in the server log:

java.lang.NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl
at com.adobe.workflow.qpac.user.UserService.execute(UserService.java:221)
at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:551)
at com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessEngineBMTBean.java:1933)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878)
at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCommand(adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.java:2153)
at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControllerBean.java:138)
at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandControllerBean.java:99)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Reason

The version of the User QPAC deployed in LC ES is not the updated version compatible with LC ES. It cannot interpret the lc7form variable type which is used in the LC7 compatibility layer when importing LC7 processes into ES.

Solution

Deploy the updated User QPAC available from:
LIVEYCYLE_HOME\configurationManager\plugins\upgrade-plugin\collateral

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
ProcessManagement | Adobe enterprise product blog | David McMahon | Page 2

Posts in Category "ProcessManagement"

LiveCycle ES: ALC-DSC-504-000 TaskManager DSC not installed error

Issue

 When attempting to import an LCA archive in the adminui you may receive the following exception:

2008-03-18 09:23:11,808 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: 
public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.
EjbTransactionCMTAdapterLocal.doRequiresNew(com.adobe.idp.dsc.transaction.TransactionDefinition,
com.adobe.idp.dsc.transaction.TransactionCallback) throws 
com.adobe.idp.dsc.DSCException:ALC-DSC-504-000: 
com.adobe.idp.dsc.registry.DataTypeNotFoundException: 
DataType: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance version:0.0 not found
 at com.adobe.idp.dsc.registry.datatype.impl.DataTypeRegistryImpl$1.doInTransaction(DataTypeRegistryImpl.java:94)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:336)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequired(EjbTransactionCMTAdapterBean.java:259)
 at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

This exception occurs when the TaskManager DSC service is not deployed. ProcessManagement usually installs this TaskManager component.

Solution

You should check the deployment directory for your application server and confirm that the file “adobe-taskmanager-dsc.jar” is deployed.  Then goto the adminui and ensure the service is running under Services > Applications and Services.

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

LiveCycle ES: “ALC-WKS-005-029: A problem occurred in the Submit Service” error submitting a form in Workspace

Issue

 When you are trying to submit a form in Workspace with LiveCycle ES you may receive the following error in the Workspace UI:

Task 101 has failed to submit. (ALC-WKS-007-072)

and the following exception in the server log:

2009-06-24 11:51:12,968 WARN [com.adobe.workspace.tasks.com.adobe.workspace.tasks.DocumentSubmitServlet] 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
flex.messaging.MessageException: 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
at com.adobe.workspace.AssemblerUtility.createMessageException(AssemblerUtility.java:384)
at com.adobe.workspace.tasks.DocumentSubmitServlet.doPost(DocumentSubmitServlet.java:230)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.adobe.workspace.events.RemoteEventClientLifeCycle.doFilter(RemoteEventClientLifeCycle.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)

Reason

 This is due to an incorrect configuration in the submit service settings.

Solution

 The submit service for the form variable should have the following configuration:

reference: (181013769/2365358)

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

LiveCycleES: ALC-WKS-007-040 error in Workspace trying to open a form

Issue

When trying to open a form in Workspace you may receive an error ALC-WKS-007-040, and the form will not be displayed.

Reasons

This error can occur in many different situations.  You should analyse the server log and see what the cause of the exception is.

Here are some examples where this error can occur:

  1. The form as specified in the render options cannot be found, or the render options are incorrect.  This situation would often be accompanied by the following errors in the log:
    • ALC-FRM-001-058: Cannot retrieve the resource from Repository Path
    • ALC-FRM-001-035: Failed to load TemplateStream for FormQuery=
    • ALC-WKS-005-028: A problem occurred in the Render Service
  2. It is using some cached version of the form, and the cached version is then deleted.  You may see the following errors in the logs in this situation:
    • EJB Exception: : com.adobe.workflow.template.document.TemplateNodeNotFoundException: Template object: A1239961657505 not found.
  3. The root cause in the exception trace is: com.adobe.idp.taskmanager.dsc.client.task.TaskNotFoundException: no task found for task ID = xxxx
  4. “The application has failed to start because omniDynamic411_vc8_rt.dll was not found.” error received in Windows.

Solutions

Follow the respective solutions related to the situations above:

  1. Verify your render options in the xfaform variable.  Use the parameters as specified in the online help:
  2. Upload the form again to the Resources view in Workbench, or create a new folder, and change the xfaform variable to reference the new form location.
  3. This error can occur in numerous situations following a migration from LC7 to ES.  Solutions can be found under:
  4. Refer to solution in:

Additional Information

If you are upgrading a LC7 process which contains a User QPAC, to ES, there are some manual steps you should follow to be able to make the process work in ES.

You will need to change the lc7form variable to an xfaform variable, remove the init-form, configure endpoints and so on.  You can find a detailed guide to this process under:

http://livedocs.adobe.com/livecycle/8.2/wb_help/000397.html

reference: (180890414)

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

LiveCycleES: description of manual tasks after upgrading from LiveCycle 7

For anybody looking for more information about migration from LiveCycle 7.x to LiveCycle ES, there are some manual steps involved which you should know about so that you can plan your resources and testing around this.

The main manual tasks are:

  1. Upgrade process using Upgrade tool
  2. Delete init-forms
  3. Change each form variable type from ‘lc7form’ to ‘xfaform’
  4. Set render/submit service for each xfaform variable
  5. Remapping User QPAC’s input and output variables (in LiveCycle 7.x, the input can be a variable name, but in LiveCycle ES, it must be an xPath expression), if multiple User QPACs are used in a process, you have to remap the input/output one-by-one.
  6. Activate the new process version

You can find more information on each of the steps above in the LiveCycle Workbench ES documentation below.
Upgrading processes in LiveCycle Workbench:
http://livedocs.adobe.com/livecycle/8.2/wb_help/wwhelp/wwhimpl/js/html/wwhelp.htm
…see the section under Creating Processes > Upgrading processes, particularly the section on Performing Upgrades.

For LiveCycle Workbench ES2.5 you should read the following documentation:
http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb4e389e8612826be7e6a-8000.html

More information about the tasks involved in upgrading a process that uses an init-form bound to a schema:
http://kb2.adobe.com/cps/404/kb404420.html

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

LiveCycle: NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl

Issue

After performing an upgrade from LC7 to ES 8.2.1 and then trying to run a process in the LC7 compatibility layer, the process instance may stall at a User component with the following exception in the server log:

java.lang.NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl
at com.adobe.workflow.qpac.user.UserService.execute(UserService.java:221)
at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:551)
at com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessEngineBMTBean.java:1933)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878)
at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCommand(adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.java:2153)
at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControllerBean.java:138)
at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandControllerBean.java:99)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Reason

The version of the User QPAC deployed in LC ES is not the updated version compatible with LC ES. It cannot interpret the lc7form variable type which is used in the LC7 compatibility layer when importing LC7 processes into ES.

Solution

Deploy the updated User QPAC available from:
LIVEYCYLE_HOME\configurationManager\plugins\upgrade-plugin\collateral

VN:F [1.9.22_1171]