When you use the Hewlett-Packard Universal Printer driver, Adobe Reader and Acrobat may crash. The following error may appear in the OS event log:
Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=083a8310 ebx=0701649c ecx=08431f30 edx=00000be8 esi=00000000 edi=0000002c eip=0700bf92 esp=0012cea4 bp=0012cef4 iopl=0
nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 fl=00210206
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\BIB.dll -BIB!BIBLockSmithAssertNoLocksImpl+0x4b7b:0700bf92 0fb772fe
movzx esi,word ptr [edx-2] s:0023:00000be6=????0:000> kb
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WTSRV\system32\ntdll.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\AGM.dll -
This issue occurs only after printing multiple times; sometimes only after the fourth or fifth print job. It is only reproducible in certain environments (for example, German Windows locale, with a German domain). This issue was thought to be an Adobe issue, based on the error message above pointing to an Adobe DLL.
After further investigation, Adobe discovered that strange results from the call to the Microsoft API “DeviceCapabilities” cause this error. When correct, this call returns the number of pages that were sent to the printer. For a document with 22 pages, it sometimes returns 39 sometimes 22 and sometimes -1, which means the function failed. Any result other than 22 is false and could result in the crash. If the function returns 39, then there is space for 39 pages reserved in memory when only 22 are written. Therefore, some other memory is overwritten by mistake, which would result in an application crash.
HP have developed an updated driver to fix this issue. Other customers experiencing this issue should contact HP to get the updated driver.
If you are using the spell checking tool with Adobe Reader 8.1.x you may experience an application crash and error message like the following:
The crash usually occurs when you enter text in a text field that is not already in the dictionary. You then right-click on the text field to bring up the spell checking context menu:
Without selecting any of the options in the spell checking menu, you click another field on the form. Then the crash occurs.
This crash has been fixed in Reader 8.2.x and in Reader 9. Upgrade to these, or later versions to solve this issue.
If you have upgraded from Adobe Reader 7 or earlier to Adobe Reader 8 or later, you notice some differences in the PDF behavior. For example,
- Form events not fired in the same order, or with the same frequency (particularly the layout:ready event). As a workaround, you can move the script to another event in Designer (for example, form:ready).
- Text is shifted or clipped
- PDF field values are modified (particularly checkbox and radio-button values)
- Tabbing order is different (read-only fields are included in the tabbing order). As a workaround, set the field property in Designer to “protected” instead of “read-only“.
These differences result from a change in the rendering engine in Adobe Reader 8 and later. The rendering engine was redeveloped to improve performance of large dynamic forms (100+ pages). The rendering engine in Adobe Reader 8 and later uses direct or AGM rendering. Some of the changes mentioned above (form events, tabbing order) are side-effects of the rendering engine modifications, and others (text-clipping, field values) are product issues. The side-effects have known workarounds as outlined above, whereas the product issues have been addressed in the subsequent versions of Reader (8.2, and 9.3).
If you encounter other issues not mentioned above, and you want to restore the behavior from Adobe Reader 7, you can use a compatibility flag. The flag instructs the rendering engine to use the legacy engine from version 7. Place the following flag in the XML source:
If you are deploying Reader or Acrobat across an enterprise to Windows clients or Terminal Servers and are encountering issues during the deployment, then this article will be useful for debugging such issues.
Adobe proivdes a tool called Tuner (Acrobat/Reader 7) or Customization Wizard (Acrobat/Reader 8+) to build transform files in MST format. These transform files can then be bundled with the standard MSI installer package from Adobe, and when the installer is run, it will apply the custom settings in the MST to the standard installation.
If you are encountering problems with your MSI and MST files, then here are some troubleshooting tips:
- use install mode on terminal servers:
- change user /install
- change user /execute
- check drive mappings for terminal servers:
- Very often some other drive like “M:” is used as the boot drive (it would be drive C: otherwise). This is so that users can still see their local drive C: when in the WTS session.
- put MST in same folder as MSI and run it using the command line:
- for example: msiexec /i AcroRead.msi /t Custom.mst
- check OS language versions as paths may differ i.e. C:\Programme instead of C:\Program Files
- rebuild the transform file on the same OS as the target OS you are trying to deploy to
- check the transform MST with ORCA as this will validate it and show the differences to the standard install
- use the msiexec UI and log files:
Interesting sites about deploying Reader in an enterprise and customizing with Customization Wizard:
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 the Acrobat SDK to control the print functionality in Acrobat/Reader, or to write a custom print plugin, you will need to use the function: AVDocPrintPagesWithParams(avDoc, &docPrintParamsRec);
The length of the input parameters in docPrintParamsRec, e.g. the printer names, are limited to 64 characters, or 32 Unicode characters. Windows however supports up to 240 characters for printer names.
Printing to a printer with a name longer than 64 characters, will not give an error message, the document will just not print.
This is a limitation in the Acrobat SDK as it still uses short printer names. In the Acrobat standard printer dialog, there is no limitation as the dialog uses internal methods which have already been extended for long printer name support.
The Acrobat 9 SDK will resolve this issue and add support for long printer names.
Please refer to the following link for the declaration of the AVDocPrintPagesWithParams function (pg: 1713):
it is discussed again here:
You should use the setTimeOut() method with the action defined as closeDoc(). The setTimeOut() method must be assigned to a variable in a top level object in the form, to prevent it from being garbage collected when a lower level variable goes out of scope.
In the form:ready event you should add the following script:
var discard = soUtils.closeDoc();
and then create a new Script object on the form with the following code:
var str = "This document will now close.";
return app.setTimeOut('this.closeDoc();', 1);
Then the PDF should automatically close itself when opened in Acrobat/Reader.
If you are trying to print a PDF with Reader/Acrobat you may receive the error message “Too few operands”.
You may need to strip down the original XDP file in Designer object-by-object, re-generate, and try to print the PDF to find the offending object. Drop-down list boxes that contain a blank entry in their lists has been known to cause this issue in previous versions.
Once you identify which object is causing the problem you should analyze this object and all related script to isolate the root cause of the issue.
Restart Acrobat to view the Debugger console when using the Preferences option.
- From Designer, save the form as PDF, open it in Acrobat, and press CTRL+J to open the debugger.
When Reader or Acrobat is installed, it creates a Setup Files folder:
- Reader: C:\Program Files\Adobe\Reader 9.0\Setup Files\…
- Acrobat: C:\Program Files\Adobe\Acrobat 9.0\Setup Files\…
This folder is used as an installer cache containing the actual installer file. The installer file is used to repair the Reader or Acrobat installation. However, some companies keep the installer available on a network share, and therefore do not want the installer cache created, as it takes up space.
You can disable this folder during installation by using the Adobe Customization wizard to transform the standard MSI installer file. Disable the option “Enable Caching of installer files on local hard drive” under Installation Options.
To download and get more information on the Customization wizard, visit this link:
You can use Acrobat 8 to apply usage rights to PDFs, in order to distribute the PDFs for Review and Commenting workflows to Reader 8 users. This includes the option to print comments. This is possible in Acrobat 8 using the “Document and Markup” option in the print dialog itself, and if the “Print notes and pop-ups” option in the Commenting preferences in Acrobat is enabled.
However, in Reader there are no Commenting preferences, so the users have no way to enable printing of comments even if they select the “Document and Markup” option from the print dialog.
There is a registry key in Acrobat that controls the “Print notes and pop-ups” option in the Commenting preferences. If you set the following key in the Reader registry, then the comments are printed:
If you are trying to install Acrobat/Reader 7.0.7 using the MSI you may receive the following error:
Action start 12:35:52: INSTALL.
DEBUG: Error 2235: Database: . Column ‘Action’ not present or ambiguous in SQL query:
SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence` WHERE `Sequence` > 0
ORDER BY `Sequence`
Internal Error 2235. , Action, SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence`
WHERE `Sequence` > 0 ORDER BY `Sequence`Action ended 12:36:50: INSTALL. Return value 3.
This is a problem with the InstallShield configuration. Such issues should be raised directly with InstallShield support, or in their forums.
This problem is described here:
If you have installed Reader/Acrobat and are having problems starting it, you may receive the following error message:
"Acrobat fail to load it's Core DLL"
Acrobat/Reader 6 or 7:
This error occurs if you are installing Acrobat/Reader to a Windows NT platform. There is a BIOS setting “limit CPUID Function” that should be enabled for NT machines and disabled for Windows XP/2000 machines.
Later Acrobat/Reader versions
This error has also been reported with later Acrobat/Reader versions when computers were infected with malware. The virus/malware can usually be detected and removed with the use of Kaspersky TDSSKiller tool. We would strongly recommend that you clean any infected systems immediately as this malware could be used to steal personal data from your computer.
Acrobat/Reader 6 or 7:
With this setting enabled on Windows NT in the BIOS the problem does not occur.
Later Acrobat/Reader versions:
If you are facing this issue, we recommend running the Kaspersky TDSSKiller tool on your system. For installation and usage instructions, please refer to “How to disinfect a compromised system” on http://support.kaspersky.com/5350?el=88446