Designed and documented for the: U.S. Department of Labor Employment & Training Administration Office of Workforce Security Division of Foreign Labor Certification

Quick Reference Guide

to Adobe Acrobat Reader

for Versions 4.0 and 5.0

Published: March 15, 2005 For system support, email: PLC.Help@dol.gov

CONTENTS

INTRODUCTION....3 Document Conventions....3 Acronyms.....3 GETTING STARTED WITH ACROBAT READER...4 Downloading Acrobat Reader....4 VIEWING A PDF....5 Opening and Closing a PDF....5 Displaying a PDF in Full Screen View...6 Setting a Default Page View...6 NAVIGATING A PDF...8 Zooming In and Out....8 Finding Text in a PDF....8 SAVING A PDF....9 PRINTING A PDF....10 TROUBLESHOOTING TIPS...11
Problem 1: PDF Does Not Display...11 Problem 2: Printer Out of Memory...11 Problem 3: PDF Does Not Print....11

INTRODUCTION

This Quick Reference Guide was prepared for Division of Foreign Labor Certification (DFLC) employees who are responsible for providing customer support to Permanent Online System (PLC) end-users. It was prepared to serve both as an instructional guide for training purposes, and as a handy desk reference. This Quick Reference Guide provides helpful information on how to install Adobe Acrobat Reader versions 4.0 and 5.0, and how to use some of its basic features: opening and closing Acrobat-readable Portable Document Format (PDF) documents; viewing, navigating, and searching PDF documents; and saving and printing PDF documents. This guide does not describe all of the features of Acrobat Reader, nor is it intended to replace Acrobat Readers product documentation. For additional information about Acrobat Readers features, refer to the online help [accessible from the Help | Acrobat Guide (4.0) or Help | Reader Help (5.0) menus] in the Acrobat Reader product.

Document Conventions

The following conventions are used in this Quick Reference Guide:

ITEM CONVENTION EXAMPLE

Buttons, tabs, icons Hyperlink Page, menu, dialog box, key and field names Data that you enter by typing on your keyboard System messages
Graphic representation Color text and underlined Bold type Courier New font In quotation marks and bold type

PLC.Help@dol.gov

File | Open, Open dialog box, Ctrl+O Password You are now a registered user.

Acronyms

The following acronyms are used in this Quick Reference Guide:

ACRONYM DEFINITION

DFLC DOL Permanent Online System
Division of Foreign Labor Certification Department of Labor Labor Condition Application Online System Web site
Quick Reference Guide to Adobe Acrobat Reader

Page 3

GETTING STARTED WITH ACROBAT READER
Adobe Acrobat Reader is free software that you can obtain via the Web. Once installed on your PC, it allows you to view documents saved in Adobe Acrobat-readable Portable Document Format (PDF). Generally, documents that you can view using Acrobat Reader have a.pdf extension to their filenames. In this section, you will learn how to download Adobe Acrobat Reader from the Web to your PC.
Downloading Acrobat Reader
1. From your desktop, start Internet Explorer or Netscape. 2. To download Acrobat Reader from the Permanent Online Systems web site, type in the following Address for Internet Explorer or Location for Netscape: http://www.plc.doleta.gov. The Permanent Online System Welcome page is displayed. 3. Click the Get Acrobat Reader icon or the Click here hyperlink.

The File Download dialog box is displayed. 4. Make sure that the option is selected, and click Download message box. The Save As dialog box displays. on the File
5. Browse to the location on your PCs hard drive where you want the Acrobat Readers installation files to reside, and click minutes to download. Depending on the speed of your network, these files may take several
6. When the download is complete, click Acrobat Readers setup program launches.
. The downloaded files are unpacked, and the
7. Follow the prompts and instructions on the setup programs screens to install Acrobat Reader.
Note: If you want to install the latest version of Acrobat Reader, go to Adobes website at www.adobe.com and follow the appropriate hyperlinks, or click http://www.adobe.com/products/acrobat/readstep2.html and follow the online instructions there to download the software.

Page 4

VIEWING A PDF
To view a PDF document that resides on your computer, launch Adobe Acrobat on your computer and open the PDF to view it (see Opening and Closing a PDF below.) If the PDF that you want to view resides on the Web, then your Web browser will launch Adobe Acrobat automatically for you when you attempt to open the PDF. You must have at least Netscape 4.0 or Internet Explorer 4.5 to do this. There is no difference between viewing a PDF on the Web or opening it directly using Acrobat Reader. The tools described in this guide for viewing PDF documents are available in either configuration.
Opening and Closing a PDF
1. Launch Acrobat Reader by double-clicking the Acrobat Reader 4.0 or 5.0 icon on your desktop, or from Windows Start menu, select Start | Programs | Acrobat Reader 4.0 (or 5.0). Acrobat Reader launches, displaying the menu bar, the toolbar, and a blank screen.
2. Select File | Open from the menu bar, or click The Open dialog box displays.
on the toolbar, or press Ctrl+O on your keyboard.

Page 5

3. Browse to and select the filename of the PDF you want to open, and click displayed in Acrobat Reader.

. The file is

Note: If the author of the PDF you are opening set the document view to Full Screen, you will be unable to see Acrobat Readers menu bar or toolbar. If that is the case, press the Escape key or press Ctrl+L on your keyboard.
4. When you are done viewing the file, select File | Close from the menu bar or press Ctrl+W on your keyboard to close the displayed PDF.
Displaying a PDF in Full Screen View
With a PDF document open in Acrobat Reader: 1. Select View | Full Screen from the Acrobat Reader menu. The document fills the entire viewable area of your screen.
Note: Since you dont have a menu bar in Full Screen view, you need to use the Return key or the Page Down Page Up buttons on your keyboard to browse through the document.

2. To exit Full Screen view, press the ESC key. 3. Press CTRL+L to toggle back and forth between normal view and Full Screen view.
Setting a Default Page View
You can set a default magnification level for the page you wish to view. This means that every time you open a document it will display at the same viewing size. 1. If you are using Acrobat Reader 4.0, choose File | Preferences | General. The General Preferences dialog box is displayed. If you are using Acrobat Reader 5.0, choose Edit | Preferences. The Preferences dialog box is displayed.

Page 6

2. From the Default Zoom drop-down menu, select the appropriate magnification value. 3. Choose OK to accept the page view settings.

Page 7

NAVIGATING A PDF
With a PDF document open in Acrobat Reader: Scroll through the document using the Page Up and Page Down keys on your keyboard, or the scroll bar on the right. Scroll through the document page-by-page using the buttons. To go to the end of the document, click the button. To go to the beginning of the document, click the button. If the document has bookmarks, click on a particular topics title to jump to that section in the document.

Zooming In and Out

With a PDF document open in Acrobat Reader: 1. Press Ctrl + + (plus) to zoom in (or magnify) the view, and press Ctrl + - (minus) to zoom out (or reduce) the view. icon, and while holding the left mouse button down, drag the magnifying 2. You can also click the tool over the text you want to magnify then release the mouse button. 3. Click the hand tool icon to return to normal view when you are done magnifying the page.

Finding Text in a PDF

The Find feature in Adobe Acrobat Reader makes it easy for you to locate a specific section of a PDF without having to scroll through numerous pages to get to that particular section. Simply search the PDF for a specific word or phrase that you know appears in the section that you want to view, and Acrobat Reader will take you there. 1. Select Edit | Find from the menu bar, or press CTRL+F, or click the Find button dialog box is displayed. The Find
2. Enter the word or phrase in the Find What field, and click. You may also elect to select options to match the whole word, match the case (upper/lowercase characters in the search string), or to go backward in the document to find a particular word or short phrase. Acrobat Reader moves through the document, stopping at each instance of the search text that it finds.

Page 8

SAVING A PDF
1. To save a copy of the PDF currently displayed in Acrobat Reader, choose File | Save A Copy. The Save a Copy dialog box displays.
2. From the Save in drop-down list, choose the directory where you would like to save a copy of this PDF file. 3. Enter a filename, and click Save. The PDF is now saved in the directory you specified. You can retrieve this file later by following the steps outlined in the Opening and Closing a PDF section in this guide.

Page 9

PRINTING A PDF
1. To print a copy of the PDF currently displayed in Acrobat Reader, choose File | Print, or click the button on the toolbar. The Print dialog box is displayed.
2. Select a print range (print the whole document, only the current page, or define page numbers to be printed). You can also elect to print the document with annotations or without. 3. If you wish to change the printer, click on the drop-down arrow from the Name box, and select a printer from the list. 4. Enter the number of copies you would like to print in the Number of Copies box. 5. Click OK to print the displayed PDF document on the selected printer.

Page 10

TROUBLESHOOTING TIPS
This section of the guide describes some common problems that Acrobat Reader users may experience when working with PDF documents. It also provides possible solutions that may resolve the problems. If a problem is not listed in this guide, please email the Help Desk at PLC.Help@dol.gov to obtain further technical assistance.
Problem 1: PDF Does Not Display
When using Acrobat Reader, the PDF that I wanted to view did not display. For example, I clicked the hyperlink to load the Online Help instructions, and the document did not display on my screen. Solution: There are several reasons why this could happen. You should first check to make sure Acrobat Reader is installed on your PC. Sometimes the document you are trying to view is hiding behind another window. Try pressing Alt+Tab to scroll through your windows, or maximize the window to display the document.
Problem 2: Printer Out of Memory
My printer runs out of memory when I attempt to print a PDF. Solution: This may be due to insufficient or low Random Access Memory (RAM) on the printer. Upgrade the memory in the printer. Or try selecting Properties from the Acrobat Readers Print dialog box, and changing the print resolution to a lower setting such as 300 x 600 dpi. Or use the Print as Image setting in Acrobat Readers Print dialog box.

Problem 3: PDF Does Not Print
When using Acrobat Reader, the PDF that I wanted to print did not print correctly. Solution: Select the Print as Image option in Acrobat Readers Print dialog box. The Print as Image feature tells Acrobat Reader to send a 300 dpi raster image to the printer rather than vector art. Caution! By selecting the Print as Image option, it may take longer for the PDF to print. Therefore, you should use this option only when needed.

Page 11

Intended audience

This document is intended for administrators, IT personnel, and others who need an understanding of how the new Updater functions in tandem with systems that are configured with locked down settings, disk compression, user privileges, and so on. It provides details about configuring and troubleshooting the Updater. While the user interface (UI) details may be of interest to end users, the majority of the content here describes registry-level configuration and log-level troubleshooting and will likely only be of interest to administrators. Adobe recognizes that most deployment workflows in enterprise settings will not use the Updater, but will rather use 3rd party tools or scripts.

1.1 Best practices

Updates are essential for upgraded functionality, fixed bugs, and security. For example, new and critical security features and protections were released with 9.2 and 9.3. Adobe recommends that updates and patches always be applied when released. The default configuration settings are designed to keep the application updated on a regular basis.

1.2 Available features

The user interface and many of the available application-level preferences remain unchanged. Some of the available registry/plist-level configuration options include: 5
History and changes across releases
Setting the update mode: Set to Automatic (unavailable on Mac), semi-automatic, or manual. Locking the update mode: Administrators can lock the update mode so that users cant change them via the user interface. (Not available on Macintosh) Disabling updates: Preventing automatic download and update by setting the mode to manual. Updater invocation at user logon: Invoking the Updater when a user logs on. Logging: Configuring logging (brief vs. verbose) and troubleshooting. Tip: Application preferences are described in subsequent chapters. A complete Preference Reference is also available to administrators via the AIR application Administrators Information Manager on the enterprise documentation portal.
1.3 History and changes across releases
Past versions of the Acrobat family products used the Adobe Update Manager (AUM) for updates. Other Adobe products, such as the Creative Suite products, will continue to use AUM. However, all versions of the Acrobat family of products beginning with 9.2 and 8.1.7 will use the Acrobat Updater. This is true even when those products are included with the Creative Suite package. The difference between AUM and the new Updater will be similar to many users. Both share the UI item and Help > Check for Updates. Some differences include:

AUM: Acrobat versions prior to 9.2 and 8.1.7:
Update preferences controlled by a file on disk. Log settings controlled by a file on disk; log name and location is different. No automatic setting. Preference set by going to Edit > Preferences > General > Check for updates. Checks for updates every week or month. Update preferences controlled at the registry level. Log settings controlled at the registry level; log name and location is different. Improved security. Since Updater settings are stored in HKLM, access requires administrator privileges and are therefore less susceptible to malicious attacks. Preference set by going to Preferences > Updater. Checks for updates every 3 days. Less intrusive workflows that are less likely to interfere with a users work. Updates that arent tied to other Adobe products, so they are smaller.
Acrobat and Reader Updater: Acrobat versions 9.2 and 8.1.7 and later:
Enterprise Administration for the Acrobat Family of Products. Adobe Systems Inc.
Checking for updates manually
Table 1 Changes across releases

Version

Description
9.2 and 8.1.7 Acrobat Updater is enabled in April, 2010 and AUM is disabled for Acrobat and Reader. AUM will continue to work for other Creative Suite products.
1.4 Checking for updates manually
When an application is configured so that the Updater does not check for updates even when the Updater is invoked (the mode is set to manual for example), then the Updater will not check for updates on application launch. If it is invoked via the applications Run key, (on login, for example), it exits immediately. While there are other mechanisms that initiate a check by the Updater, all of these can be overridden by end users via the UI. Users can start the Updater and a check manually via Help > Check for Updates.
Figure 1 Manual update check
1.5 Notification during automatic updates
For users that have configured the application to automatically install updates, the application notifies them when the update begins. In this case, a notification balloon pops up for 15 or more seconds stating that the Updater has initiated the update process.

Introduction to the Acrobat-Reader Updater Figure 2 Notification bubble
Differences between Windows and Macintosh
1.6 Differences between Windows and Macintosh
For the most part, the Updater on Windows and Macintosh is similar. The major differences are shown below.
Table 2 Windows vs Macintosh differences

Feature

Preference location Invoked by Updates checked for

Windows

Registry (some keynames vary)

Macintosh

plist files (some keynames vary)
User logon Every 3 days. Application launch Check for updates menu item

User logon Same

Modes Preference locking Logging
Manual, semi-automatic, and automatic Yes The mechanisms are similar but the error codes and messages vary by OS. Actions are logged.
No automatic mode, only manual and semi-automatic No The mechanisms are similar but the error codes and messages vary by OS. Actions are not logged.

Updater for Windows

2.1 User roles, permissions and Updater behavior
The Updater behavior on versions 8 and 9 is identical. Unlike most application preferences which reside in HKEY_CURRENT_USER, the Updater preferences are machine level settings shared by all users in HKLM. As such, they require administrative privileges to change, as well as elevated privileges if UAC is enabled. Some HKLM duplicates reside in HKCU.
Behavior based on existing AUM settings: The Opt-in dialog does not appear if bUpdater has been locked to disable updates.
If the existing AUM update setting is manual (Check for updates at startup is unchecked), then updating to a product version that supports the new Updater invokes the Opt-in dialog. If the user does not select automatic, then the setting remains manual. If the existing AUM update setting is semi-automatic, an Opt in dialog appears and the Updater preference is set as follows:
If users press the Enter key or choose OK the preference is set to automatic. If users choose Preferences, the Preferences panel appears and allows changing the setting.
Automatic mode is not available
Silent installs as well as the Automatic preference in the Preferences > Updater settings panel is disabled under the following conditions:
The user does not have administrator privileges on XP. The user does not have administrator privileges on Vista or Windows 7 with UAC turned off. 8.x only: Vista and Windows 7 with UAC turned on. When the install is from an MSI or executable file.
2.1.1 Update type and sequence
How the Updater operates with respect to user privileges is depends on the update type and update sequence. Thus, the following concepts are central to understanding the end user experience:

%\ XVHU ORJRQ UHDG 5XQ$GREH$50 %\ DSS VWDUWXS UHDG L&KHFN LI E8SGDWHU LV QRW
&KHFN HYHU\ GD\V UHDG L/DVW &KHFN IRU 8SGDWHV PHQX DSSOLFDWLRQ VWDUWXS
7KH ODVW FKHFN WLPH LV UHFRUGHG LQ L/DVW< DQG L/DVW'
8SGDWHV IRXQG" <HV 'RZQORDG SD\ORDG <HV
$XWKHQWLFLW\ FKHFNV 7KH VLJQHG SD\ORDG VLJQDWXUH PXVW EH YDOLG $ KDVK RI WKH GRZQORDGHG SD\ORDG LV FRPSDUHG WR WKH YDOXH LQ WKH PDQLIHVW
3D\ORDG LQWHJULW\ YHULILHG" <HV
/RJJLQJ &DQQRW EH GLVDEOHG )LOH VL]H LV OLPLWHG WR 0% 1HZ ORJ ILOHV DUH FUHDWHG LI WKH ODVW ORJ LV ELJJHU WKDQ 0% 2QO\ ROG ORJ LV EDFNHG XS 9LVWD:LQ XVHU!?$SS'DWD?/RFDO?7HPS? $GREH$50ORJ ;3 XVHU!?/RFDO 6HWWLQJV?7HPS?$GREH$50ORJ 6HW L/RJ/HYHO WR HLWKHU %ULHI RU 9HUERVH 'HIDXOW LV EULHI 0DQXDOO\ FUHDWH WKH NH\ WR FKDQJH
$XWRPDWLF L&KHFN <HV

0DQXDO L&KHFN

6HPLDXWR L&KHFN
,QVWDOODWLRQ EHJLQV <HV

<HV

8VHU 2NV LQVWDOO"
,Q VRPH FDVHV LQVWDOODWLRQ PD\ QRW UHTXLUH WKH UHOHDVH RI VKDUHG ILOHV WKHUHE\ UHTXLULQJ UHERRW ODWHU
6KDUHG ILOHV LQ XVH" 1R

<HV DOHUW XVHU

5HERRW UHTXLUHG LI 26 UHWXUQV FHUWDLQ HUURUV

5HERRW UHTXLUHG"

8SGDWHV LQVWDOOHG

)LOHV UHOHDVHG"

Updater configuration
2.4 Updater configuration
2.4.1 Setting the update mode
The Updater checks for updates based on the mode settings as follows:
Automatic: Updates are automatically downloaded and installed silently. Maps to Automatically install updates. Semi-automatic: Updates are automatically downloaded but users are asked whether they want to install them. Maps to Automatically download updates, but let user choose when to install updates. Manual: No updates are downloaded automatically. The user can manually check for updates by choosing Help > Check for Updates. Maps to Do not download or install updates automatically.
2.4.1.1 User interface configuration
Updater settings can be set by the user as follows: 1. Choose Edit > Preferences. 2. Choose Updater. 3. Configure the setting and choose OK. Tip: Administrators can lock the setting in the Automatic or Manual mode and disable the user interface via bUpdater.
Figure 5 Preferences panel: Update mode settings
2.4.1.2 Registry configuration
The update mode is a machine level setting that cannot be set on a per user basis. To set the update mode: 1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM.

Changing the interval time is not recommended as Adobe may reset the value during a future date or a security fix could be missed.
2.4.4 Logging configuration
The log file is a file generated and appended to at runtime with status, operational, and error information describing what the Updater is doing. This information helps diagnose runtime problems and a log set to verbose should be included with any support requests.
Example 2.4: Log file [2010-05-19 13:48:52] InstallProductMsp. [2010-05-19 13:48:52] file - C:\Documents and Settings\All Users\Application Data\Adobe\Reader\9.3\ARM\AdbeRdrUpd932_all_incr.msp [2010-05-19 13:48:52] args [2010-05-19 13:49:23] ExecuteInstalls() [2010-05-19 13:49:23] Error Code: 0x643 [2010-05-19 13:49:23] ExecuteInstalls failed. [2010-05-19 13:49:23] ** Setting Error Condition: [2010-05-19 13:49:23] Error Code: 0x5DC [2010-05-19 13:49:23] Failed to read UAC setting, defaulting to Enabled. [2010-05-19 13:50:01] Failed to read UAC setting, defaulting to Enabled. [2010-05-19 13:50:01] Delete file: C:\DOCUME~1\brogers\LOCALS~1\Temp\ArmUI.ini [2010-05-19 13:50:01] Error Code: 0x2 [2010-05-19 13:50:01] C:\Documents and Settings\All Users\Application Data\ Adobe\Reader\9.3\ARM\ [2010-05-19 13:50:01] GetLastError(): 0x91 - The directory is not empty. [2010-05-19 13:50:01] ARM returns ERROR_SUCCESS [2010-05-19 13:50:01] Adobe ARM 1.1.7.0 logging finished.
Versions prior to 9.3.3 do not show specific log errors in the UI. Log errors are grouped into broad categories, and only a generic category error appears in the error dialog. With 9.3.3, the log errors are converted from Hex to Decimal and displayed to end users in order to facilitate troubleshooting. Log file size is not limited during an update. However, since log files are appended to each time the Updater runs, there is a 1MB limit on old logs. Size limit behavior is as follows: If an existing log size is bigger than 1 MB, the Updater creates a new log file. The old log file is backed up once as AdobeARM-backup. There can never be more than one backup log. Note: Logging cannot be disabled.

Table 3 Log locations

Vista XP

Log location

%USERPROFILE%\AppData\Local\Temp\AdobeARM.log %USERPROFILE%\Local Settings\Temp\AdobeARM.log
There are 2 log levels available: Brief and Verbose. The default is Brief. The default setting is brief. To change it: 1. Go to HKEY_LOCAL_MACHINE\Software\Adobe\Adobe ARM\1.0\ARM\
Updater invocation at user logon
2. Create the key iLogLevel. 3. Set iLogLevel:

0: Brief 1: Verbose

2.4.5 Updater invocation at user logon
By default, the Updater is invoked by every time a user logs on. At logon, the OS reads the application preference below. Note: This value is not customizable and is provided for troubleshooting purposes only.
Example 2.5: Preference: Win: Run key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "Adobe ARM"="\"C:\\Program Files\\Common Files\\Adobe\\ARM\\1.0\\AdobeARM.exe\""
2.4.6 Viewing the last checked for update time
By default, the Updater performs an update check every 3 days and records the year and day of that check in iLastY and iLastD. If 3 days have not passed, the Updater exits. If more than 3 days have elapsed, the Updater looks for updates. The last and most current value may be written to HKLM or HKCU. Because the Updater doesnt need elevated privileges to start and check or download updates, it will write to HKCU. However, when elevated privileges are required for any action, it write to HKLM. Therefore, when checking and troubleshooting the last check date always verify the values in both locations. Note: This value is not customizable as the value is written at runtime. Also, the rule is actually has 3 days passed? Thus, a check may happen on the fourth day.
Example 2.6: Registry key: for setting the update mode [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM] "iLastY"=dword:000007da "iLastD"=dword:0000000a

2.5 Troubleshooting

2.5.1 Watchdog dialog
When the application obtains a manifest the Acrobat Updater records the download date. If the time interval that is allowed to pass from that download date to a a successful update been exceeded (see Setting the Watchdog dialog invocation time) a dialog appears suggesting the user might want to manually get an update from adobe.com. For example, users who cannot obtain the Acrobat Updater manifest due to no internet connection or who are behind authenticating proxies will likely see the dialog in Figure 6. After the dialog appears, the

Table 5 Updater errors: Miscellaneous
1000 None None None None None
Use the last error. Failed to delete previous ARM update archive RevertToAUM property found set in manifest. WaitForSingleObject failed in WaitFilesInUse. WaitForSingleObject failed
Varies. There are no previous ARM files to delete. The manifest specifies that AUM rather than ARM should be used. Some files were in use. The Updater should wait and then finish when they are no longer in use. TBD
Table 6 Updater errors: Application initialization
1100 Auto mode: An error occurred. Adobe Updater will try again later Manual mode: An error occurred. Please check for updates again later. 1113 Same as 1100. Same as 1100. Same as 1100.
Failed to create main dialog A required dialog failed to be created within the requisite amount of time.
InitUpdatedProductInfo failed. InitUpdateData failed. Command Line: Failed to create launcher path Failed to create command line
Could not identify the product to update. The user canceled the update while downloading the manifest. Tried to invoke Adobe Updater via empty command line. TBD TBD

1116 1117

Not used. Same as 1100. Same as 1100. Same as 1100.
Not used. InitDownloadManager failed LoadLibrary failed TBD Could not load the dll that is used to extract the Updater files
GetProcAddress(ExtractFile The extraction dll loaded successfully, but extraction sFromArchive) failed failed for some reason.
Table 7 Updater errors: User permissions and usage

1200 Not used.

Std User on XP - IsElevated returns 0. User is Guest -IsElevated returns 0. Std User on Vista with UAC off -IsElevated returns 0. Not enough privileges to run
The user does not have sufficient update privileges. The user is logged on as a guest does not have sufficient update privileges. UAC is off on Vista. The user does not have sufficient update privileges. N/A TBD

1201 1202

Not used. Not used.
None Found preference AUTO_OFF. Automatic updates preference is off - exiting {PRODUCT NAME}. Automatic updates preference is off - exiting ARM.
1203 Auto mode: An error occurred. {PRODUCT NAME} will try again later Manual mode: An error occurred. Please check for updates again later.
Time elapsed is less than time limit - exiting ARM.
Table 8 Updater errors: Manifest and payload
Cannot install the update. Please run {PRODUCT NAME} repair. Not used.

Create file failed Failed on unlocked Manifest file. Init Manifest Data failed Wait for MSI Mutex is not set in Manifest
TBD: problem with s7zArchiveFile. The Updater performed correctly by not using an unlocked and possibly invalid manifest. The manifest specifies that AUM should be used instead.
Auto mode: An error occurred. Adobe Updater will try again later Manual mode: An error occurred. Please check for updates again later.
IsSizeAndSignatureValid failed for: <some file>
The file size or signature is invalid on the downloaded manifest or installer.
ValidateSingleInstallFiles Updater tried to validate the msi file before returning FALSE for 0 file size installing by looking at the first file and verifying it has an msi extension. Missing file Validate file failed ARM Update signature validation failed ValidateFiles failed 1305 Cannot install the update. Please run Adobe Updater. Not used. Cannot install the update. Please run Adobe Updater. Error in ARM Update data Empty Update ID Empty Update URL TBD The file size or signature is invalid on the downloaded manifest or installer. The signature is invalid on the downloaded manifest or installer. The signature is invalid on the downloaded manifest or installer. TBD The update ID is blank. The update URL is blank. Check the ARM_server key.
Table 9 Updater errors: Network and download
1400 Cannot establish a connection. Please try again later.
HTTPS and HTTP connection failed
Protocol or port could be blocked or no internet connection. 21
Network too slow or no connection Port 443 Blocked: HTTPS:// BITS connection failed attempting HTTP:// connection
TBD Protocol or port could be blocked. The manifest is missing or the website is down.

1401 1402

Cannot download update files. DownloadArmUpdate failed. Please check for updates again later. Same as 1401. Missing file on server (HTTP Error 404): Accompanied by DownloadFiles:isComplete returns error. General Download File failure

TBD Downloading was stopped when a required file was not found. Downloading the update failed for some unknown reason.

Same as 1401.

TBD Failed to navigate to URL: http://www.adobe.com/support/downloa ds/product.jsp?product=10&platform=Win dows
Table 10 Updater errors: MSI windows installer
1500 Cannot install the update. Please run Adobe Updater.

ExecuteInstalls failed.

Deprecated with 9.3.3. and 8.2.3. MSI (Windows installer) errors formerly mapped to this generic UI error. Now, the MSI error is displayed in the dialog and 1500 no longer appears To troubleshoot MSI problems, see http://kb2.adobe.com/cps/849/cpsid_84935.html.
Table 11 Updater errors: OS-level
1600 Auto mode: An error occurred. Adobe Updater will try again later. Manual mode: An error occurred. Please check for updates again later. Same as 1600. Same as 1600.

CreateDirectory() failed

Could not create the extraction directory.
QueryServiceStatusEx failed ShellExecute failed in RelaunchARM. ShellExecute to relaunch ARM failed with SE_ERR_ACCESSDENIED.

TBD TBD

Same as 1600. Same as 1600. Same as 1600.
OpenSCManager failed OpenSCManager failed None
Could not get a handle on the SCM database. Could not open the SCM service. TBD 22

1606 Same as 1600.

Table 12 Updater errors: File IO
1701 Cannot save files to disk. Please check for updates again later. If you continue to have problems, see your system administrator. Same as 1701.
Failed to get current working directory. Failed to change cwd.
Could not find the directory where the 7z files reside to extract. Could not find the files to extract or could not change from the extract from to the extract to directories. Could not find the files to extract or extraction failed for some other reason. TBD

1703 1705

Same as 1701. Same as 1701.
ExtractFilesFromArchive failed. Delete file:
Table 13 Updater errors: Log only
GetCurrentUserSID():LookupAccountName() failed. GetCurrentUserSID():ConvertSidToStringSid() failed. No updates in Manifest for current product configuration. Manifest file not signed by Adobe Failed to lock Manifest file. Unknown file type in file object Failed to read UAC setting, defaulting to Enabled. EULA not yet accepted. ARMDownloader::BITS Error: There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected. Error Code: 0x80200010 BITS Error Context: The error occurred while the remote file was being processed. DownloadFileDirectly failed Files Total: 1 Files Transferred: 0. last line before next instance of {PRODUCT NAME} started (Rebooting system while {PRODUCT NAME} was in the process of downloading Updates)

3.4.6 Viewing the last checked for update time
By default, the Updater performs an update check every 3 days and records the year and day of that check in LastCheck in com.adobe.ARM.plist. If 3 days have not passed, the Updater exits. If more than 3 days have elapsed, the Updater looks for updates. Note: This value is not customizable as the value is written at runtime.
Example 3.9: Mac preference: Last checked time <dict> <key>LastCheck-925793fb327152fd34795896fa1fb9ffa268b2a852256fe56609efa3</key> <date>2010-04-27T20:50:40Z</date> </dict>

Troubleshooting

3.5 Troubleshooting

3.5.1 Watchdog dialog

When the application obtains a manifest the Acrobat Updater records the download date. The NoserverContactDays preference specifies the time interval that is allowed to pass from that download date to a a successful update. The default is 135 days. If the NoserverContactDays time has elapsed, a dialog appears suggesting the user might want to manually get an update from adobe.com. For example, users who cannot obtain the Acrobat Updater manifest due to no internet connection or who are behind authenticating proxies will likely see the dialog in Figure 15. After the dialog appears, the clock is reset and the dialog does not appear again until the NoserverContactDays time has once again elapsed.
Figure 15 Watchdog Dialog: Problem with updates
3.5.2 Dialog error reporting
User interface errors are designed to provide basic information about an updates status. Additional detail can be found in the logs; however, since those technical details are designed to help administrators and support troubleshoot any issues, that information is not displayed to end users in the Updater dialogs. The end user facing dialogs usually contain an error code and one or two sentences of text. For a listing of those messages, see Error codes and messages.
3.5.2.1 Error codes and messages
The table below lists the error strings that appear in the user interface.
Table 16 User interface error messages

Code Range

1001-1099 1101-1199

Message

Manual mode only: Cannot connect to Adobe update server. Please verify that you are connected to the Internet and check for updates again. Manual mode only: Cannot download update files. Please verify that you are connected to the Internet and check for updates again later.

Macintosh user experience
2010-04-30 14:39:32 +0530: Checking update to 8.2.2: AdbeRdrUpd822_all_i386.app.zip 2010-04-30 14:39:34 +0530: Command from ARMHammer: "percent" 2010-04-30 14:39:34 +0530: Command from ARMHammer: "done" 2010-04-30 14:39:34 +0530: Command from ARMHammer: "percent" 2010-04-30 14:39:34 +0530: Installing update to 8.2.2: AdbeRdrUpd822_all_i386.app 2010-04-30 14:41:41 +0530: Command from ARMHammer: "percent" 2010-04-30 14:41:41 +0530: Command from ARMHammer: "done" 2010-04-30 14:41:57 +0530: ***** Ending update to /Applications/Adobe Reader 8/ Adobe Reader.app
3.6 Macintosh user experience

3.6.1 Manual mode

In manual mode, open applications that interfere with the Updater are listed in several of the dialogs.
Figure 16 Mac manual mode dialog: Update available
Updater for Macintosh Figure 17 Mac manual mode dialog: Validating update

Manual mode

Figure 18 Mac manual mode dialog: Install now?
Updater for Macintosh Figure 19 Mac manual mode dialog: Hide updater
Figure 20 Mac manual mode dialog: Installing update
Updater for Macintosh Figure 21 Mac manual mode dialog: Downloading update
Figure 22 Mac manual mode dialog: Update successful

Semi-automatic mode

3.6.2 Semi-automatic mode
Figure 23 Mac semi-automatic mode dialog: Update available
Figure 24 Mac semi-automatic mode dialog: Install successful
%USERPROFILE%AppDataLocalTempAdobeARM.log 16 %USERPROFILE%Local SettingsTempAdobeARM.log 16
AdobeARM-backup. 16 adobeARMOverrides.plist 31 Automatic 14, 15 Automatic mode is not available 9 Available features 5
${HOME}/Library/Logs/Adobe/Adobe Acrobat Updater.log 31 ${HOME}/Library/Logs/Adobe/Adobe Reader Updater.log 31
Basic operation 11, 27 Best practices 5 bEULAAcceptedForBrowser 23 bUpdater 9, 14, 15
Changes across releases 7 CheckForUpdatesAtStartup 30 Checking for updates manually 7 com.adobe.ARM.plist 31
Default settings and permissions 27 Dialog Problem with updates 33 Differences between Windows and Macintosh 8 Disabling Updater invocation on application startup 30
Error code and message 18 Error codes and messages 18, 33 Errors Application configuration 19 Application initialization 20 File IO 23 Installer 22 Log only 23 Manifest and payload 21 Miscellaneous 19 Network and download 21 OS-level 22 User permissions and usage 20 EULA 11, 23 EULAAcceptedForBrowser 11
History and changes across releases 6
iCheck 15 iInterval 15, 16, 17, 18 iLastD 17
iLastY 17 iLogLevel 17 Introduction to the Acrobat-Reader Updater 5 Registry configuration 14 Registry key for invoking the unable to Watchdog dialog 15 for setting the update mode 17

launchd 32 Locking the update mode 15 Log locations 16, 31 log size 16 Logging configuration 16, 31 LogLevel 32
Semi automatic 15, 30 Semi-automatic 14, 30 Semi-automatic mode 39 Setting the check-for-update interval 31 Setting the update mode 14, 30 Setting the Watchdog dialog invocation time 15, 31 Size limit behavior is 16
Mac download locations 27 Mac manual mode dialog Downloading update 38 Hide updater 37 Install now? 36 Installing update 37 Update available 35 Update successful 38 Validating update 36 Mac semi-automatic mode dialog Install successful 39 Update available 39 Macintosh log size limit 31 Macintosh user experience 35 Manual 14, 15, 30 Manual mode 35 Manual update check 7
Troubleshooting 17, 33 Typical workflow 24
Unable to check for updates dialog 33 Updater Configuration 30 Updater configuration 14 Updater for Macintosh 27 Updater for Windows 9 Updater invocation at user logon 17, 32 Updater settings Macintosh 27 Updater-old.log 31 User interface configuration 14, 30 User interface error reporting 18, 33
Need screen shot 33 NoserverContactDays 33 Notification bubble 8 Notification during automatic updates 7
Viewing the last checked for update time 17, 32
Watchdog Dialog Problem with updates 18 Watchdog dialog 17 Windows dialogs (manual mode) Checking for updates 24 Installing update 25 Ready to install 25 Update is available 24 Update successful 26 Validating update 25 Windows user experience 24 Windows vs Macintosh differences 8 Windows workflow configuration 13 Workflow configuration (Macintosh) 29
Opt-in dialog behavior 11
plist configuration 30 Preference Mac launchd 32 LogLevel settings 32 Win for locking the update mode 15 Run key 17 Setting the update mode 15 Preferences panel Update mode settings 14, 30

Reader Updater.app 28