If you are using Firefox profiles to work with Adobe Reader/Acrobat 9 in the browser, you may encounter a browser crash. This can occur when you have a PDF open in one profile and a normal HTML page in another profile in Firefox. Then you close the Firefox window with the PDF, firefox crashes with:
sw: firefox.exe Application Error, the instruction at "0x0700609c" referenced memory at "0x00000014".
The memory could not be "read"
Therefore this error will occur very often and will prevent the users from working. Firefox profiles refers to the functionality when you start Firefox through the command line with "firefox -p -no-remote", this will open a firefox dialog to manage profiles
This is a bug in Adobe Reader/Acrobat 9 and is fixed in version 9.3 onwards.
If you are using a proxy between Workbench and the LiveCycle ES Server, you may want to limit the connection to provide a higher level of security. For the standard installation Workbench communcates with the LiveCycle server over HTTP with servername and port number as follows:
Using a proxy server, you could limit the connection further to just two URLs:
This is subject to change, especially in later versions and must be tested thoroughly to ensure there are no conflicts or unexpected problems. Adobe will investigate issues related to such a configuration but in some cases the only solution may be to return to the default settings, without limiting the connection to specific URLs.
If you have installed Designer 7.1 and you receive an error message on starting the client that it cannot find Designer.xdc, then it looks like you have a corrupt installation. This can occur if you attempt to install a newer patch version of Designer 7.1 on top of an existing installation.
You must always completely uninstall an existing Designer 7.1 installation, before you attempt to install a newer version. You should use the Add/Remove Programs option in the Windows control panel to uninstall the older version.
When you have migrated from LC7 to ES and you setup the LDAP Search component (with the refresh or build buttons), you receive the following error:
Cannot instantiate class com.sun.jndi.ldap.Ldap.CtxFactory
The initial_context_factory parameter (in the deployment settings of this component) has been changed during the migration process by mistake from null to com.sun.jndi.ldap.Ldap.CtxFactory.
Change this parameter to the correct value: com.sun.jndi.ldap.LdapCtxFactory.
When a null value was used in LiveCycle 7, the server interpreted it as com.sun.jndi.ldap.LdapCtxFactory by default. This no longer happens in LiveCycle ES, so you cannot use null values for this parameter.
More information about the mapping of the LDAP Search component in LiveCycle ES can be found under:
If you have uninstalled PDF Generator 7.2.2 you may notice that the SQL service has been left behind. You will need to remove this service manually to do a completely clean uninstallation.
In order to remove the SQL service in Windows, you can follow these instructions:
Run Regedit or regedt32.
Find the registry entry: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
Find the service there and delete it.
You may wish to look at the keys and see what files the service was using and perhaps delete them also.
Note: You will have to reboot before the list gets updated in server manager.
Some programs change the permissions to make it more difficult for you to delete them. For these you will have to right click on the “service” in regedit, go to permissions and grant the administrator full control before the service can be deleted.
If you are using Designer to preview an XDP in the PDF Preview tab, you may receive the following error:
Wrong type parameter supplied to a PDS procedure
This error usually appears when the XML structure is no longer valid, i.e. it has been edited manually.
Open and save the form in Designer7.1, then it will correct any problems in the XML source, and work fine in PDF Preview.
Opening in Designer8.0 and later versions will also correct any issues.