Archive for April, 2009

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.
Rating: 0.0/10 (0 votes cast)

LiveCycle: TaskNotFoundException: no task found for task ID=2850

Issue

After you upgrade an LC7 installation to LC ES 8.2.1 SP1 and use the Process Upgrade Tool, you may receive the following error accessing a form:

An error occurred trying to create the form. ALC-WKS-007-040



The server log file includes the following exception:

ALC-WKS-005-028: A problem occurred in the Render Service. Please review the render orchestration for this process.
 at com.adobe.workspace.AssemblerUtility.createMessageException(AssemblerUtility.java:384)
 at com.adobe.workspace.tasks.TaskActions.render(TaskActions.java:714)
 at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
 at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;
...
Root cause: com.adobe.idp.taskmanager.dsc.client.task.TaskNotFoundException:
no task found for task ID = 2850
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.renderForm(TaskManagerServiceImpl.java:3705)
 at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.java:118)
 at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor.java:140)
 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.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
 at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerService.invokeWithRetry(TypedTaskManagerService.java:102)
 at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerService.callRenderService(TypedTaskManagerService.java:1324)
 at com.adobe.workspace.tasks.TaskActions.render(TaskActions.java:680)


Reason

The main cause for the exception is:

Root cause: com.adobe.idp.taskmanager.dsc.client.task.TaskNotFoundException: 
no task found for task ID=2850



This error can occur in 3 situations:

  1. The lc7form variables were not converted to xfaform variables after upgrading the process.
  2. The User component is the version compatible with LC7 and not compatible with LC ES.
  3. There is a problem with the taskid in the dB.

Solution

  1. Convert the lc7form variables to xfaform variables manually using the information in the Workbench Help:
  2. Get the updated User component, which is compatible with LC ES and deploy it under the LC7.x Components view. This component is usually deployed for you during the ES installation process. However, if the installation did not have access to your LC7 installation, then you can do it manually. You can find the updated LC7inES components under LIVECYCLE_HOME/configurationManager/upgrade.
  3. Ensure you are using the latest ServicePack for LiveCycle ES.  The latest service packs contain fixes for DB issues related to this error.

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

LiveCycle PolicyServer7: MySQL error 1005 restoring mysqldump of EDC database

Issue

 If you are attempting to restore a backup copy (mysqldump) of the EDC database into MySQL, you may encounter a MySQL error 1005.

Reason

 This is linked to INNODB and the foreign keys.

Solution

 You should follow the steps below to backup and restore the EDC database successfully on JBoss/MySQL:

A/ Backup

To fully backup the current state of a policy server, you need to do the following:

  1. While the APS service is running, export the configuration settings from the UI by going to Configuration -> Manual Configuration -> Export
  2. While the APS service is either running or shut down, backup the login-config.xml from the jboss\server\all\conf directory (and any other JBoss configuration files that you might have manually modified)
  3. While the APS service is shut down, backup the database using mysqldump (from the bin directory in mysql) by issuing the following command on a command prompt: mysqldump –user=root –password edc > backup.sql

B/ Restoration

Assuming that you are restoring on a clean machine, here are the steps you would follow:

  1. Install Policy Server and logon as Admin
  2. Import the APS configuration settings which you saved in step a) above
  3. Shut down the service and edit/restore the jboss\server\all\conf\login-config.xml so that the <application-policyname="UsernamePwd_Auth_Search"> section matches the one you were using previously
  4. Logon to mysql (mysql -u root -p) and issue the following commands:  drop database edc;        create database edc;        grant ALL on edc.* to root@localhost;

Note: The last step shouldn’t really be necessary, as the root user should already have all rights on all databases.  These commands clear the whole database content.

       5. edit the backup.sql which you saved in 3) above, and add the following line at the beginning:

  SET foreign_key_checks=0;

Note: If you don’t do this, you will get error 1005 / errno 150 from mySQL when restoring the table – this is a known issue with foreign_keys and mysqldump, and can be easily addressed with the above line.

       6. run the following command to restore all the SQL data:

     mysql -u root -p edc < backup.sql

This should not give you any error.

7. restart the APS service. Once APS is started, you should be back to the state from the backup, and all the policies should work exactly as before.

After running these exact steps, you should be able to open a PDF with an existing policy even after you have removed the server and its database completely.

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

LiveCycle Workbench ES: QPAC properties dialog not appearing for LC7 components

Issue

When importing processes from LiveCycle7 into Workbench ES, and clicking on the LiveCycle7 component in Workbench, the properties dialog for that component may not appear. This behaviour can also be observed when attempting to drag one of these LiveCycle7 components onto a new process map in Workbench.

Reason

When the LC7 Components in Workbench have not been updated to be compatible with the ES compatibility layer, you will not see the properties dialog. Most QPACs from LC7 need to be updated for use in LC ES, especially to use the new “lc7form” variable, in place of the old LC7 “form” variable type.

This information can be found in the following document:
http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf#page=4

If you analyse the QPAC JAR file and open the manifest.mf in a text editor, you can check the version. The version of Adobe’s QPACs which are compatible with ES all start with version 8.x for example “AdobeVersion: 8.2.xxx.xxx.x”. If the version of the QPAC is 7.x, then it has not been updated for use in ES. This applies to the Adobe QPACs only. Other software vendors may not use the same version numbering.

Solution

Get a version of the QPAC compatible with the LC ES compatibility layer, and deploy it in the LC7.x Components view in Workbench ES. You will then be able to view and change the properties of the activities in your LC7 imported process maps.

reference: (180802977/2302710)

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

Acrobat/Reader 7: install with MSI failed with SQL errors

Issue

 If you are trying to install Acrobat/Reader 7.0.7 using the MSI you may receive the following error:

Action start 12:35:52: INSTALL.
DEBUG: Error 2235: Database: . Column ‘Action’ not present or ambiguous in SQL query:

SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence` WHERE `Sequence` > 0
ORDER BY `Sequence`

Internal Error 2235. , Action, SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence`
WHERE `Sequence` > 0 ORDER BY `Sequence`Action ended 12:36:50: INSTALL. Return value 3.

Reason

 This is a problem with the InstallShield configuration.  Such issues should be raised directly with InstallShield support, or in their forums.

Solution

 This problem is described here:

http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q107132&sliceId=

reference: (1-28110668)

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

Acrobat/Reader: “Acrobat fail to load it’s Core DLL” error after installation

Issue

 If you have installed Reader/Acrobat and are having problems starting it, you may receive the following error message:

"Acrobat fail to load it's Core DLL"

Reasons

Acrobat/Reader 6 or 7:

This error occurs if you are installing Acrobat/Reader to a Windows NT platform.  There is a BIOS setting “limit CPUID Function” that should be enabled for NT machines and disabled for Windows XP/2000 machines.

Later Acrobat/Reader versions

This error has also been reported with later Acrobat/Reader versions when computers were infected with malware.  The virus/malware can usually be detected and removed with the use of Kaspersky TDSSKiller tool.  We would strongly recommend that you clean any infected systems immediately as this malware could be used to steal personal data from your computer.

Solutions

Acrobat/Reader 6 or 7:

With this setting enabled on Windows NT in the BIOS the problem does not occur.

Later Acrobat/Reader versions:

If you are facing this issue, we recommend running the Kaspersky TDSSKiller tool on your system. For installation and usage instructions, please refer to “How to disinfect a compromised system” on http://support.kaspersky.com/5350?el=88446

Additional Information

If the solutions above do not help it may be because the Acrobat/Reader installation is corrupted.  You should try to repair the installation, or do a complete uninstall, download and re-install.  Also check your permissions on the Adobe installation folder and ensure you have adequate permissions.  It has also been reported that some anti-virus programs cause conflicts in Acrobat/Reader.  There are further details in the following technote: http://helpx.adobe.com/acrobat/kb/reader-core-dll-error.html

Here are some forum entries related to this error message:

http://forums.adobe.com/message/5229585#5229585
http://forums.adobe.com/message/1943611#1943611
http://forums.adobe.com/message/5207131
http://forums.adobe.com/message/5204572
http://forums.adobe.com/message/4695630
http://www.ehow.com/how_7342111_fix-load-its-core-dll.html
http://www.helpinfo.com/index.jsp?k2dockey=1021096170711579407&formwassubmitted=true
http://forums.techguy.org/all-other-software/566428-solved-adobe-reader-8-failed.html

reference: (1-28187701)

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

Acrobat/Reader7: how to disable the “Keep forms data temporarily on disk” option

Issue

 If you are using Reader 7 you may want to disable the option “Keep forms data temporarily on disk“.

Reason

 This prevents form data being cached on the local disk, which may pose data integrity/security risks to enterprise customers.

Solution

There are a few workarounds to disble this functionality:

1. create a registry key to disable the option automatically:

The location is [HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\7.0\Originals].

Create the key named bCacheFormData.

Create a dword value of 00000000.

Close registry and relaunch Acrobat/Reader.

2. Another option is to control this in the form itself using JavaScript

From the Acrobat JavaScript Scripting reference available at http://partners.adobe.com/public/developer/en/acrobat/sdk/AcroJS.pdf#page=219

this.nocache = true; 

This will only have an affect in the form context.

3. Your third option is to use the Web browser settings:

Set the preference “Do not save encrypted pages to disk” as checked.

Empty Temporary Internet Files Folder when browser is closed.

Additional Information

 This setting has been disbled by default in Acrobat/Reader 8.0 and later versions.

reference: (1-29705311)

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