Adobe Reader MUI is Adobe’s Multilingual User Interface version, with which you can install any combination of supported languages. For example, you can install French, German, and Spanish simultaneously and then switch among those languages within Adobe Reader. The user interface changes to the appropriate language automatically.
If you have problems controlling the startup language of Adobe Reader MUI, then try the following to gain more fine-grained control over the startup language:
- Under the Reader preferences, there is a setting for the startup language under the section entitled “International.” You can set this setting to the language of choice. Or, you can set it to “like operating system,” which starts Adobe Reader MUI using the same locale as the host operating system.
- Set the registry key UseMUI as outlined in the screenshot so that the operating system language is used as the Adobe Reader MUI startup language:
If you are still having problems with the startup language, try manually configuring the appropriate keys in the registry. Use either the Customization wizard (for enterprise deployments), or change them directly in the Windows registry for single installations.
- Delete (or make sure that the following keys are not present) NOTE: for a fresh non-customized install these keys are sometimes not present:
- HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Language\UseMUI\UseMUI
- HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Language\next
- Then add the following registry key:
- [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\9.0\Language\next]
Note: For Reader, the value is “RdLang32.DEU”.
The exception below occurs when using a custom component (DSC) in LiveCycle ES 8.2.1 designed to extend the functionality provided by the services from Adobe. The component includes the TaskManager DSC JAR file.
####<09-Jul-2010 15:04:21 o'clock CEST> <Error> <com.adobe.workflow.AWS> <PI> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <BEA1-2CB96822045F171B0B4D> <> <1278680661381> <000000> <stalling action-instance: 2101 with message: Cannot coerce object:
com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo@33142fb of type: com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo to type:
ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo@33142fb of type:
com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo to type: class com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo
This error occurs when you include the TaskManager DSC JAR in your component. The TaskManager DSC (that is, the service itself) is not meant for use as a library.
Remove the TaskManager JAR from your component and use the libraries provided with the SDK. Or, extract any required classes from the DSC JAR and include them in your component.
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.
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.
This error is a product issue in LiveCycle ES and there are patches available for 184.108.40.206 and 220.127.116.11. You should contact enterprise support if you require one of these patches. The issue has been fixed in ES2 SP2 and later versions.
The following exception occurs when you use FormDataIntegration to merge xml data into a prerendered PDF file:
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data.
When a PDF form contains a rich-text enabled field with data (default or already merged), the FormDataIntegrationClient can’t import the data. This issue has been identified as a limitation in the AFML library as it presently does not support the tab-interval style attribute.
In the current LiveCycle ES2 documentation, it states that the FormDataIntegrationClient is the preferred way to import data to a PDF form:
Adobe Engineering confirms that the Forms service using renderPDFForm is the recommended way to import data, rather than using the FormDataIntegrationClient. Adobe plans to update the documentation to reflect this information.
Do one of the following:
- Place the text in rich-text fields that do not have the tab-interval style attribute.
- Use the renderPDFForm API from Forms ES2 by setting “Generate Server Appearances” to false.
If you are using the AdminUI for LiveCycle ES to search for stalled branches, you may notice that some of the items are missing from the returned list. For example in the returned list you may notice the totals report 7 items but only 5 are shown.
The stalled branches list is compiled from the TB_BRANCH_INSTANCE table in the database. Any branch that has a sub_status of “-99” should appear in the list in the AdminUI. If however some of these branch entries refer to processes or actions which do not exist (or have been deleted) from the database, then this list may display the reported behaviour.
To verify this, you should run the SQL statements below on the database. We would expect that the results returned match the missing entries from the stalled branches list in the adminui.
select * from TB_BRANCH_INSTANCE B
where ( select count(*) from TB_PROCESS_INSTANCE
and not B.PROCESS_INSTANCE_ID is null
and B.PROCESS_INSTANCE_ID !=0
order by CREATE_TIME
select * from TB_BRANCH_INSTANCE B
where ( select count(*) from TB_ACTION_INSTANCE
and not B.CURRENT_ACTION_INSTANCE_ID is null
and B.CURRENT_ACTION_INSTANCE_ID !=0
order by CREATE_TIME
If either of these statements return some results, then you can fix the entries in the database to prevent the items from being included in the stalled branches totals. The entires are referring to process/action ids that do not exist in the process/action tables in the database, and so they will never be completed or continued. This situation can occur if you have been modifying the database using external (not from Adobe LiveCycle) code, or if you are running a 3rd party process purge tool.
If you want to prevent these entries from being reported in the list of stalled branches, then you can change the sub_status value to -1. If the status value is already 2 (completed) or 4 (terminated) you should change the sub_status to 4.