Miscellaneous Error Messages

In LiveCycle, users and groups are synchronized from an LDAP server in batches of 200. When the results returned from an LDAP server is >= 200, an AutoDetectionLogic is automatically enabled, which disables the paging if the LDAP server is Oracle Directory Server Enterprise (previously known as SunOne) edition 5.2 or 6.3.

However, the paging gets enabled for Oracle Directory Server Enterprise if you have a proxy server acting as Active Directory. As a result, the synchronization fails with the LDAP: error code 12 – Unavailable Critical Extension error.

To fix this issue, perform the following steps to turn off AutoDetecitonLogic to prevent LiveCycle from sending any paging request:

1. Login to LiveCycle administration console using administrator credentials.

2. Go to Home > Settings > User Management > Configuration > Manual Configuration.

3. Export the config.xml file to the filesystem.

4. Look for the tag entries starting with <entry key="enablePaging" value= present under nodes named LDAPUserConfig and LDAPGroupConfig for a particular Enterprise or Hybrid domain.

   By default, the entry is <entry key="enablePaging" value="true"/>.

5. Modify the entry to <entry key="enablePaging" value="false"/>.

6. Save the config.xml and import it back into LiveCycle.

If you use TCP for caching, you may encounter the following exception while starting the TCP locator:

Exception in thread "main" com.gemstone.gemfire.SystemIsRunningException: Locator "/usr/prod/lbs/domains/lbsdomain/idplib/caching" is already running. 
 
    at com.gemstone.gemfire.internal.ManagerInfo.setManagerStarting 
    (ManagerInfo.java:65) 
    at com.gemstone.gemfire.internal.ManagerInfo.setLocatorStarting 
    (ManagerInfo.java:61) 
    at com.gemstone.gemfire.internal.DistributionLocator.main 
    (DistributionLocator.java:87) 
    at com.gemstone.gemfire.distributed.Locator.main(Locator.java:359) 
 
[info 2009/08/26 16:18:29.770 PDT <Thread-0> nid=0x15d56d5] Locator stopped

To resolve this issue, check for the existence of the .locator lock file in the caching folder and delete the file.

If some cluster nodes are unable to access the global document storage (GDS) directory, you may encounter the following error:

• com.adobe.idp.DocumentError: The document pointing to the file "B:\lc9_share\docm1245494450089\c5c0f6c0a324c0d45396deb69b6e11db" has expired. Consider increasing the document disposal timeout

  Ensure that:

• All nodes in the cluster are time-synchronized

• All nodes have access to the GDS

  If you still encounter this issue, check for network and latency problems.

IDPSchedulerService is not restarted although Workbench indicates that it is in the started state. The following exception appears in the server logs:

ALC-DSC-020-000: com.adobe.idp.dsc.InvalidStateException: Service: IDPSchedulerService is not in a RUNNING state

If you need to restart Scheduler from within Workbench, explicitly start IDPSchedulerService to avoid exceptions.

The following warning may appear in the application server logs during conversions to PDF:

WARN [Document] DOCS007: Failed to delete a directory "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\AdobeDocumentStorage\local\removeOn2006Y08M31D18h16m15s.1157028375000" after 60 attempts. The file(s) under this directory may still be locked."

If this message appears consistently in the logs, restart the application server.

Failed to load resource: the server responded with a status of 500 (Internal Server Error). There was an error while getting data xml.

The above error message appears on submitting Forms that contain images of approximately 2 MB. Use images of smaller size to avoid the error.

Do not use the software applications used for running PDF Generator on the server. Also, do not print any documents from the server. This may lead to failed PDF Generator conversions or stability issues for the software applications. For a list of the software applications that can be used with PDF Generator, see Native file conversion software installation section in the System Requirements topic of Preparing to Install Adobe LiveCycle ES4 (Single Server).