Posts tagged "acrobat"

The document has been changed since it was created and these rights are no longer valid.

As a viewing program, Adobe Reader cannot make any changes to plain PDFs – it is not made for file creation or editing.

However, if you have Adobe Acrobat or Adobe LiveCycle Reader Extensions ES/ES2, you can activate functionality in a PDF that allows even Adobe Reader to handle that given PDF with advanced features, such as filling in forms, saving data into forms, commenting and annotating. These PDFs are known as “Reader-Extended PDFs”.

Sometimes when opening such PDFs, you will see the following warning:

This document contained certain rights to enable special features in Adobe Reader. The document has been changed since it was created and these rights are no longer valid. Please contact the author for the original version of this document

This means one thing: some program opened the PDF and made changes to the structure of the PDF itself – this is different from form-filling or annotating.

The change could have been made by an Adobe program (although Reader 8.1.0 displayed the message erroneously until 8.1.2 fixed it), another program (typically other PDF writers), or even automated programs that analyze and modify files.

At this point, only Adobe Acrobat can read the file, and re-apply the special features. If Reader has detected structural change however, it is advised to obtain a fresh copy of the form, as the changed version might not behave properly. Acrobat can export data from the damaged form, which can then be imported (by Acrobat) into the fresh form.

The fresh form can then be saved with this data in it, after which the special features can be applied to it.
The extended PDF can be returned then to the user to be used in Adobe Reader.

Internet Explorer crashes when using the Reader or Acrobat plug-in

Sometimes Internet Explorer (32-bit) will crash when using the Reader or Acrobat plug-in to display a PDF in a browser window.

The reason is that some third-party PDF creators use Acrobat’s DLLs, but rather than keep them in their own folders, copy them to system32/ which causes Acrobat to open defunct DLLs – and fall over as a consequence.

To resolve the issue, do the following:

Open C:\Windows\system32

Move the following files somewhere else (for example, create a folder C:\bad_dlls):


Of course, this means that whatever application installed those DLLs in system32 will stop working.
Identify it, and contact the software’s publisher to check if they have a solution.

If you’re feeling adventurous: You could tentatively open the Acrobat/Reader folder under Program Files\Adobe\Acrobat\Acrobat 9.0\ , and COPY the corresponding DLLs to system32 – but that is of the “dirty hack” class and would be generally disadvisable. The third party PDF application would not necessarily be able to use these DLLs anyway.

What’s this PDF ?

[This is not an official Adobe publication. This article may contain errors or omissions, and is subject to change without warning.]

While troubleshooting PDF-related problems, a number of tests come back again and again, and I intend with this article to give a brief overview of basic techniques and considerations on troubleshooting PDF problems.

Note that Reader is the free PDF reading software by Adobe. Acrobat has many more functions including PDF creation, manipulation, analysis, peer-reviewing, tracking, securing…. the list goes on.

Also note that sections referring to browser environments apply to Windows only, as browser plug-ins for Acrobat and Reader are not issued by Adobe for non-Windows operating systems (excpetion: on Mac OS X, browser integration exists only for Safari, but not other browsers)

1) Who’s Driving ?

When in a web browser in Windows, to check what plug-in is rendering the file, you can simply click somewhere in the PDF, and then use the key combo [Ctrl K]

If it is Reader or Acrobat, it will bring up a Reader or Acrobat dialog box.
If it is Acrobat, one of the sets of preferences will be “Convert to PDF”
If you’re in Reader, the PDF conversion preference set will be absent.

Otherwise, anything could happen – within the scope of the PDF reading application. If nothing happens, or a dialog for non-Adobe software appears, then you’re not displaying in Reader or Acrobat.

2) What Are My Rights ?

Through Acrobat, and some other Adobe software, it is possible to restrict how a user uses a PDF: whether they can print, save copies, modify, fill-in forms etc.

To determine this, right-click on a page in the PDF, and select “Document Properties” (available both in Acrobat and Reader)

The Security tab will show you what you are allowed to do with the PDF – whether you can print; add or remove pages, and a few more restrictions.

The Description tab will show you some useful information, of which the “PDF Producer”. Typical Adobe PDF producers are Acrobat, LiveCycle Designer, InDesign, PhotoShop, PDF Maker, PDF Library, Distiller and Adobe Central Output Server Print Agent 5.x.

If your PDF was not created with an Adobe product (in which case, it is not an “Adobe PDF”), and you are having PDF-related problems, then Adobe’s technical support may only be able to provide limited assistance (see ). This also applies when you modify a PDF with a non-Adobe product; this will sometimes leave the PDF producer intact, depending on the software you use.

To test whether an issue occurs with a real Adobe PDF, and you have Acrobat (not Reader) installed, you can try printing the PDF to the “Adobe PDF” printer (available from the “Print…” dialog). This is commonly known as “re-frying” a PDF. This will create a static PDF, whose producer will then be “Adobe Distiller”. You can only do this if you have printing rights on the PDF. Use this new PDF to try to replicate the issue.

3) What Type of Form is my PDF ?

There are two main types of PDF forms that Adobe software produces: forms created directly in Acrobat (not Reader) through the menu item [Forms: Add or Edit Fields]; and those created in LiveCycle Designer (formerly “Adobe Designer”).

The first, created by Acrobat, are known as “AcroForms”. They have static (don’t move) form fields layered on top of static (non-changing) PDF pages.

The other, created by LiveCycle Designer, are called “Dynamic XFA Forms”, or “XFA’s”, whose structure are part encoded in XML, and partly in a native binary format. These have fields that are objects within the rendered PDF, as are nearly all other elements on the pages (with some exceptions, not discussed here). XFA forms can have items that repeat depending on the data entered, have areas of text that change depending on what data is in the form, etc, etc.

This is not to be confused with embedded Flash, which may also be used as a form, and constitutes neither an AcroForm or XFA Form. That would then be a PDF with “embedded content”. You can check this by right-clicking in the form: if you get the contextual menu for FlashPlayer, then you’re in an embedded content PDF.

In Reader, there is no sure-fire way of determining whether you have a dynamic XFA form. Even if the PDF Producer is LiveCycle Designer, you may have a static form that Designer produced.

4) Does My PDF Have a Problem ?

As far as software is concerned, there is only one thing that is certain: either data is badly formatted, or we hope it is well formatted.

There is a functionality in Acrobat (not Reader) that allows you to analyse a PDF, called “Preflight”, available through [menu Advanced: Preflight]

Preflight will analyse the current PDF for any defects, and if you choose, attempt to repair the issues.

A good rule of thumb is: if Preflight says there’s a problem, there’s definitely a problem. If Preflight reports no problems however, there’s no guarantee: it just means Preflight hasn’t been able to detect any problems. If you see a spider, there’s a spider. If you don’t see a spider, maybe there isn’t one – but maybe there’s one behind you.

So if Preflight reports issues with your PDF, and you have problems with that PDF, then it will be considered that the PDF is not compatible with Adobe software. Re-fry the PDF, and try again.

What is the maximum number of tabs Reader can have in a browser?

Answer-in-theory: as many as you want

Answer-in-practise: as many as the machine can handle

Full answer:

In Windows, in Firefox, IE7 and IE8, you can opt to view PDFs linked from web pages in your browser. If you start opening a large number of these however, you’ll find that your browser will have a tendancy to complain…

This is due to depletion of desktop heap space. For every tab with a Reader (or Acrobat) plugin, a new Rdr/Acro process is launched, and it uses some heap space resources. So whilst your overall memory (RAM) is not running out, you’ll still find Firefox complaining at you with a dialog saying you have reached the maximum number of documents you can open.

On IE7/IE8 however, you may not see this. IE will merrily open as many PDFs as you tell it to, until it chokes, croaks and crashes. This has been recognized as an IE limitation – Rdr/Acro does not get a chance to display the dialog that prevents you from opening that one-too-many documents.

You can however do the following to prevent the crash (the usual CAVEATS concerning editing the Registry apply):

To correct this problem, increase the size of the desktop heap: Run Registry Editor (Regedt32.exe).
From the HKEY_LOCAL_MACHINE subtree, go to the following key: \System\CurrentControlSet\Control\Session Manager\SubSystems
Select the Windows value.
From the Edit menu, choose String.
Increase the SharedSection parameter.

For Windows NT:
SharedSection specifies the system and desktop heaps using the following format:
Add “,256” or “,512” after the yyyy number.

For Windows 2000, Windows XP, and Windows Server 2003:
SharedSection uses the following format to specify the system and desktop heaps:
Increase the zzz number to “256” or “512.”

With that you should start seeing the dialog pop up when you open too many PDFs.

Of course, you should also question why you are opening so many PDFs at the same time in the first place. It’s just inherently not safe.

How to create an Acrobat 9.x.n Admin Install Point (AIP) – integrate MSP patches to a MSI installer

NOTA: this article is not an Adobe publication, and carries no guarantees of accuracy. This article may be subject to change at any time.

The technique described here can be applied to patch all the way to 9.4.x and beyond. It can also be applied to other MSI+MSP’s in general :-)

Normally to get your Acrobat to version 9.2, you must first install v9.0, then install 9.1.0, then proceed to 9.1.2, before applying 9.2 – applying each manually, instalelr after installer. If you are administering multiple computers, you may wish to create a standalone installer, that includes all the patches up to 9.2 for example.

Here’s how to do just that, refined from a procedure sent to me by a colleague, Steve. All together now: “Thank you Steve!!” :-)

To determine exactly which patch files you need (and which you should not install as part of the AIP chain) please refer to

The patch files can be downloaded from

  1. Copy the media Setup files to a location (i.e. C:\Acrobat9\) on your hard drive.
  2. Create a folder to a location on your hard drive (i.e. C:\A920aip\). This will be the AIP folder.
  3. Open the command prompt.
  4. Navigate to the media Setup files that you copied to your hard drive.
    $> cd C:\Acrobat9\
  5. Run the setup.exe to confirm the installer files are volume, by checking if there’s an option to install as trial.
    • If install as trial has been greyed out, then the files are volume and you can go ahead with the next steps.
    • If the trial option is available, first check that the full qualified path of the location to the installer files does not contain any Unicode characters (Cyrillic, Greek, etc).
    • If it doesn’t then it is necessary to obtain the correct installer files before continuing with the next steps
  6. Once the above preparation is done, you can either perform the full-interactive steps as follows, or run the silent method as described further down.

  7. Run administrative installation from the command prompt.
    $> msiexec.exe /a AcroPro.msi
  8. When prompted point it to the AIP folder (i.e. C:\A920aip\).
  9. Place the following Acrobat MSP update files into the AIP folder:
    { AcroProStdUpd910_T1_T2_incr.msp ,
    AcrobatUpd912_all_incr.msp ,
    AcrobatUpd920_all_incr.msp }
  10. At the command prompt, navigate to the newly created folder that has the AIP files.
    $> cd C:\A920aip\
  11. At the command prompt run the Acrobat 9.1 Update, specifying the fully qualified path to the MSP file
    $> msiexec.exe /a AcroPro.msi /p C:\A920aip\AcroProStdUpd910_T1_T2_incr.msp
  12. When prompted by the Acrobat installer, point the patch installation to the folder that you are running the installation from (i.e. C:\A920aip\ , the AIP folder). Let the installer run, and terminate.
  13. At the command prompt run the Acrobat 9.1.2 Update, specifying the fully qualified path to the MSP file
    $> msiexec.exe /a AcroPro.msi /p C:\A920aip\AcrobatUpd912_all_incr.msp
  14. When prompted by the Acrobat installer, point the patch installation to the AIP folder. Let the installer run, and terminate.
  15. At the command prompt run the Acrobat 9.2 Update, specifying the fully qualified path to the MSP file
    $> msiexec.exe /a AcroPro.msi /p C:\A920aip\AcrobatUpd920_all_incr.msp
  16. When prompted by the Acrobat installer, point the patch installation to the AIP folder. Let the installer run, and terminate.
  17. You should now have a complete Acrobat 9.2 MSI and administrative install point set of files

The following script is the silent equivalent of the steps above. Write it to a BAT file and run it.

cd C:\Acrobat9
mkdir C:\A920aip
msiexec.exe /a AcroPro.msi TARGETDIR=C:\A920aip /passive

cd \A920aip
msiexec.exe /a AcroPro.msi /p C:\A920aip\AcroProStdUpd910_T1_T2_incr.msp TARGETDIR=C:\A920aip /passive
msiexec.exe /a AcroPro.msi /p C:\A920aip\AcrobatUpd912_all_incr.msp TARGETDIR=C:\A920aip /passive
msiexec.exe /a AcroPro.msi /p C:\A920aip\AcrobatUpd920_all_incr.msp TARGETDIR=C:\A920aip /passive