Miscellaneous errors

If you are deploying LiveCycle components to WebSphere on a localized instance of the Windows operating system, the Configuration Manager deployment process reaches approximately 7% completion and then adobe-livecycle-websphere.ear fails to deploy.

Follow these steps to avoid this problem:

1. Use Configuration Manager to configure the LiveCycle EAR files, but do not deploy them.

2. Without exiting Configuration Manager, open the WebSphere Administrative Console and remove the following JVM argument from the server configuration:

                –Dfile.encoding=utf8

1. Restart WebSphere.

2. In Configuration Manager, deploy the adobe-livecycle-websphere.ear file.

3. When complete, return to the WebSphere Administrative Console.

4. Add the –Dfile.encoding=utf8 JVM argument back.

5. Restart WebSphere.

6. Return to Configuration Manager and deploy the remaining EAR files.

The console output will display default value in bind address and port value fields. If you have defined values in the script, the values defined in the script would be considered instead of values displayed on the console output.

On Windows, you may provide TCP locator bind address and port values by following methods:

• You may define values of TCP locator bind address and port parameters in the script. To define parameters in the script:

  1. Open the script to edit.

  2. Set value for bind address.

     set bindaddr=<computername or ipaddress>

  3. Set value for Port Value.

     set port=<port number>

• You may choose to provide values for the bind address and port fields as console input. The default value for bind address is %computername% and default value for port is 22345.

If you select an ECM repository as the working repository on the ECM Connectors Configuration Settings screen in the Administration Console, LiveCycle-specific application model features become unavailable. For example, you may not be able to create, execute, or delete LiveCycle applications.

However, you will be able to work with LiveCycle processes as before.

The level setting on the Home > Services > PDF Generator> File Type Settings > New > HTML to PDF screen in the Administration Console is lost. For example, change the level setting from Get only 1 level to Get only 2 levels. Now, click some other option (for example, PDF optimizer) and then expand HTML to PDF again. The value for the setting changes to Get only 1 level from what you set.

To resolve this issue, set the value for this setting again to Get only 2 levels (or any other desired value) immediately before clicking Save.

Note that if you expand the HTML to PDF section again, you will still see Get only 1 level selected instead of Get only 2 levels. Do not worry about this user interface discrepancy since LiveCycle has correctly stored your selected value.

If you want to confirm that your selected value has indeed been stored, do the following tasks:

1. In Administration Console, click Home > Services > PDF Generator> Configuration Files > Export Configuration File to export the configuration file.

2. In the exported configuration file, verify that the value of the <levels> tag under <html2pdfSettings> is correct.

Administration Console displays English error messages instead of the localized strings on some screens. To resolve this issue, change the JVM locale to have server-side components generate localized error messages. For example, add the following JVM argument to set the JVM locale to French:

• -Duser.language=fr Duser.region=FR–

  See http://java.sun.com/developer/technicalArticles/J2SE/locale for more information.

From Workbench, when you remove an application which has a datatype which is referenced in a process, an exception is recorded in the server log. However, the required application is undeployed and removed successfully. You can ignore this error.

When the storeContent operation for Content Services (deprecated) is invoked with more than 30 threads, the WebSphere Application Server may stop responding.

Follow these steps to resolve the issue:

1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.

2. In the right pane, click Thread pools under Additional Properties.

3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.

4. Click Apply or OK.

5. Click Save directly to the master configuration.

6. Restart the WebSphere Application Server.

This issue is relevant for the Correspondence Management solution.

For objects created using the Asset Manager building block, you may observe that the following message appears repeatedly in the WebSphere logs:

ADMLuceneInde I org.alfresco.repo.search.impl.lucene.ADMLuceneIndexerImpl indexProperty Not indexed: Content Missing  
node: workspace://SpacesStore/aeb5e45f-971f-4f31-8f2b-5ed4f2a15070 at /{http://www.alfresco.org/model/application/1.0}company_home/{http://www.alfresco.org/model/content/1.0}DataStore/{http://www.alfresco.org/model/content/1.0}ObjectWithExtendedPropertiesMap/{http://www.alfresco.org/model/content/1.0}ObjectWithExtendedPropertiesMap-1282274200933

Follow these steps to prevent this message from appearing:

1. In WebSphere Administrative Console, click Servers > Websphere application servers and click the server name.

2. On the Configuration tab, under Troubleshooting, click Change log level details.

3. Click the Runtime tab and then expand the All Components list.

4. Navigate to the org.alfresco.repo.search.impl.* category.

5. Click the org.alfresco.repo.search.impl.lucene.* category and select Message and Trace Levels > warning.

6. Click Apply or OK and then click Save directly to the master configuration.

If you are using a version of the IBM FileNet content engine that is not exactly 4.0 but in between 4.0 and 4.5 (e.g. 4.0.3), you may see the following error message:

java.lang.Exception: Content Engine/Connection URL specified is invalid - cemp:http://<server>:<port>/wsi/FNCEWS40DIME?jaasConfigurationName=FileNetP8WSI.

Imported processes from LiveCycle 9.x or earlier may use a Document Form variable and the Submit PDF Form service. For such processes, users are not able to submit a form to complete a task under the following circumstances:

1. The process is started and then a backup of the database and GDS is performed as part of LiveCycle Backup and Restore functionality.

2. LiveCycle is restored on another machine with a different host name. Under the GDS directory, the "backup" folder is renamed to "restore", and the database is restored.

3. The user submits the form in Workspace.

When the user submits the form, a Security Warning dialog box displays this message: "This document has accessed more than one site and might be trying to share data among different locations. This could be a privacy concern. Are you sure you want to continue?" When the user clicks Yes, this error message appears: "This page cannot be displayed".

To avoid this problem, use the same host name when restoring LiveCycle from a backup.

When a PDF file is exported to Text format, all 4-byte and some 2-byte GB18030 characters are displayed as periods.

Say a server backup / restart operation on the Author instance is performed when a user is publishing assets. After the server is restarted or the backup is complete, the replication agent queue is empty. However, the assets are not published. Also, there is no indication that the assets are not published.

If an asset is exported on a fresh installation of the Corresopndence Management solution where temp folder is not created on the LiveCycle server, the export fails with the following exception:

error - ALC-ACM-007-004

error in exporting