Posts tagged "server"

Acrobat/Reader: slow display performance in Terminal Server or Citrix environments


When you view PDF files in Adobe Acrobat or Adobe Reader in a Terminal Server/Citrix environment, the display is slow to update over an RDP connection.  This issue is particularly noticeable when scrolling through PDF documents that contain high-resolution images.


Solution 1: Update the Page Display preferences in Acrobat or Reader.

Change the following settings in Acrobat or Reader.  You can either disable these options directly in Reader/Acrobat under “Edit > Preferences > Page Display > Rendering”, or using the registry keys for system administrators:

  • deactivate “2D Graphic accelerationHKCU\Software\Adobe\Acrobat Reader\9.0\AVDisplay – bUse2DGPUf=dword:0
  • deactivate “Smooth imagesHKCU\Software\Adobe\Acrobat Reader\9.0\Originals – bAntialiasImages=dword:0
  • deactivate “Smooth line artHKCU\Software\Adobe\Acrobat Reader\9.0\Originals – bAntialiasGraphics=dword:0
  • set “Smooth Text” to None (optional: some customers have reported acceptable performance without setting Smooth Text to None)
    • HKCU\Software\Adobe\Acrobat Reader\9.0\Originals – bAntialiasText=dword:0
    • HKCU\Software\Adobe\Acrobat Reader\9.0\Originals – iAntialiasThreshold=dword:0
    • HKCU\Software\Adobe\Acrobat Reader\9.0\Originals – benableDDR=dword:0

Changing registry values is not officially supported by Adobe and you do so at your own risk.  You should only be changing the registry settings if you have the correct privileges and experience in this area.

System Administrators should change these settings first using the Preferences dialog in Adobe Reader (not using the registry) and re-test the performance through Citrix.  Once you have the right combination of settings that work, then you should record the values of these registry keys to use for your other Reader installations.  This is important as the value of the iAntialiasThreshold key can differ (0, 1, or 12) depending on which of the other options are deactiviated.

Note: These settings will improve the display performance on low-bandwidth connections, however, they can adversely affect the display performance on LAN connections.  You will need to test these thoroughly.

Solution 2: Use an RDP compression tool to compress the data being sent “over-the-wire.”

RDP sends the entire set of image data each time the image is scrolled on the page.  Sending all the data at once can cause congestion on the network connection, especially with limited bandwidth.  Some customers have had success using the following tool to improve the display performance on Terminal Server for low-bandwidth connections:

Additional information

There are no general solutions in Acrobat or Reader to improve performance problems in Terminal Server. Performance issues are often based on the bandwidth limitations of the network connection, or the RDP protocol itself.

The RDP protocol does not always handle image data well.  A terminal server on Windows 2003 Server uses RDP version 5.2.  A terminal server on Windows 2008 Server uses RDP version 7.0, which does improve display performance for images.  Therefore, an upgrade to a later operating system can also improve the performance if it uses a more recent RDP version like 7.0.

Here is an article from Citrix referring to the same issue:

and an entry in ourn forums discussing the same:

reference: (181990819)

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

LiveCycle ES: Error 500 in the AdminUI when searching for tasks


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 and  You should contact enterprise support if you require one of these patches.  The issue has been fixed in ES2 SP2 and later versions.

 reference: (181590010/2633888)

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

LiveCycle Workbench: which URLs are used for communication with LC server


 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.

reference: (181300310)

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