Archive for January, 2012

Acrobat 10.1.2: “Adobe acrobat has stopped working” when using Preflight

Issue

If you are using the Preflight feature in Adobe Acrobat Pro 10.1.2 you may encounter an application crash accompanied by the following error:

“Adobe acrobat has stopped working”

Crash details:

Problem Event Name:    BEX
Application Name:    Acrobat.exe
Application Version:    10.1.2.45
Application Timestamp:    4f02e85c
Fault Module Name:    StackHash_0a9e
Fault Module Version:    0.0.0.0
Fault Module Timestamp:    00000000
Exception Offset:    00000001
Exception Code:    c0000005
Exception Data:    00000008
OS Version:    6.1.7600.2.0.0.256.4
Locale ID:    2057
Additional Information 1:    0a9e
Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
Additional Information 3:    0a9e
Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Reason

This is an issue with the Acrobat Pro 10.1.2 update on Windows only and has been fixed in the 10.1.3 update.  It does not occur on Acrobat Std or Reader editions, and does not occur on Mac OS.

Solution

1. Open Acrobat.

2. Choose Help > Check for Updates.

Acrobat will install the update automatically.

You may also download and install this update manually from the website below:

Acrobat updates (for Windows)

Workaround

  1. Log in to your computer as an Administrator.
  2. Click the link to download the AdobeAcrobatPatch10.1.2_cpsid_92893.zip  file.
  3. Unzip the file to extract the executable AdobeAcrobatPatch10.1.2_cpsid_92893.exe.
  4. Close Acrobat if it is running.
  5. Do one of the following to run the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file:
    1. Double-click the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file.
    2. Run the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.
      Example: <path to AdobeAcrobatPatch10.1.2_cpsid_92893.exe> -silent
  6. Once the process is completed, you receive a prompt stating the result of the operation.
    Note: When run in silent mode, all dialog boxes are suppressed. No success message or error message appear.
  7. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log. (The changes sometimes only take effect after you restart your computer)

reference: (3089118)

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

LiveCycle ES2: UnsupportedClassVersionError: (oracle/jdbc/OracleDriver) bad major version at offset=6

Issue

If you are attempting to configure Adobe LiveCycle server using the LiveCycle Configuration Manager (LCM) with an Oracle database, you may encounter the following exception during the DB configuration step:

Caused by: java.lang.UnsupportedClassVersionError:
(oracle/jdbc/OracleDriver) bad major version at offset=6
 at java.lang.ClassLoader.defineClassImpl(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:258)
 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151)
 at java.net.URLClassLoader.defineClass(URLClassLoader.java:589)
 at java.net.URLClassLoader.access$400(URLClassLoader.java:123)
 at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034)
 at java.security.AccessController.doPrivileged(AccessController.java:279)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:491)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:631)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
 at java.lang.Class.forNameImpl(Native Method)
 at java.lang.Class.forName(Class.java:130)
 at com.adobe.livecycle.cdv.validator.DBValidator.validateDB(DBValidator.java:174)

Reason

This error can occur if you are not using the correct Oracle DB driver, or the correct Java JDK for your platform.

Solution

You should check the Oracle DB driver and JDK version required in the relevant platform matrix.  With LiveCycle ES2 for example the platform matrix is located here:

http://help.adobe.com/en_US/LiveCycle/9.5/supported_platforms.html

So if you were to install LiveCycle ES2 on AIX 5.3 with WebSphere 7, you should be using the 64-bit JDK 1.6 SR7 provided by WebSphere (WAS_HOME/AppServer/java), and the ojdbc6.jar Oracle driver.

Be sure to set the JAVA_HOME and PATH environment variables as instructed in http://help.adobe.com/en_US/livecycle/9.0/prepareinstallsingle.pdf

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

Acrobat/Reader 10.1.2: printer blinking/paper tray messages caused by duplex print option

Issue

If you are using Acrobat/Reader 10.1.2 to print PDF documents, you may notice that the job is sent to the printer as a duplex job (print on both sides) and this may cause some issues like printer lights blinking, or errors about lack of paper in the paper trays.

Reason

With Acrobat/Reader 10.1.2 we have introduced the widely used print option “Print on both sides of paper” directly in the Acrobat/Reader print dialog.  This option is available in the printer settings, but it is not very convenient to have to open the printer settings and change it each time you wish to print differently (simplex/duplex).

This option in the Adobe print dialog is enabled by default, whereas the initial value should match what the user has specified in the printer properties.  This option can lead to the printing anomalies mentioned above.

Solution

This is a bug in Acrobat/Reader 10.1.2 and has been fixed in the 10.1.3 update so that the option has the same initial value as defined in the printer settings, and the printing anomalies should no longer occur.

1. Open Acrobat or Reader.

2. Choose Help > Check for Updates.

Acrobat or Reader will install the update automatically.

Workarounds

There are 3 options to workaround this issue.

Option1

To workaround this behaviour in the meantime simply disable this option in the Adobe print dialog.

Option 2

In an enterprise environment, you can use the following registry key to disable duplex mode automatically in Adobe Reader X:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\AVGeneral]

“iDuplexMode”=dword:00000001

or for Adobe Acrobat X:

HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\AVGeneral]

“iDuplexMode”=dword:00000001

For MacOS use the preferences file (com.adobe.Reader.plist / com.adobe.Acrobat.Pro.plist) which is located in [user]/Library/preferences/.  The name of the key is DuplexMode under AVGeneral and it has the datatype Number. You should set this value to “1″, for Simplex.

Option 3 (courtesy of the post from banyooo on http://forums.adobe.com/message/4147397)

If you are in a Windows domain controlled environment you can also roll out this registry key using a group policy as follows:

  1. Open your Windows Group Policy Editor
  2. Chose “New Group Policy”
  3. Ggo to UserConfiguration >Settings >Windows Settings >Registry
  4. Right click “Registry”
  5. Chose “New-> Registry assistent”, local computer
  6. Go to [HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\AVGeneral] “iDuplexMode”=dword:00000002
  7. Click “finish”
  8. Double-click that new entry and navigate down until you see “iDuplexMode”
  9. Double-click it too, and change the REG_DWORD value to “1″ (decimal)
  10. Chose “Replace” under the “Action” menu
  11. Close the GPO editor and link that newly created group policy to your domain or OU or whatever
  12. Perform a gpupdate /force at the client to see the reg entry changing from “2″ to “1″
  13. Reboot your clients or just wait for the gpupdate timeout period

reference: (3088596)

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

Reader 10.1.2: printing results in an application crash

Issue

If you are using Adobe Reader 10.1.2 you may experience some problems when attempting to print a PDF document.  The symptoms of this problem will be that either nothing will be printed, or, Reader may crash.

Reason

This is a bug in Reader 10.1.2 and is resolved with the 10.1.3 and later releases.  The problem is related to network printers that do not have a “Share name” defined.

If you cannot update to 10.1.3 immediately (in controlled enterprise environments) we have provided known workarounds to avoid the issue until you can install the update.

Solution

1. Open Reader

2. Choose Help > Check for Updates

Reader installs the update automatically.

If you prefer, you can download and install the update yourself. Click the link below and scroll down to the update section of the page.

Reader updates (for Windows)

Workarounds

Option 1: install patch for Adobe Reader 10.1.2

  1. Log in to your computer as an Administrator.
  2. Click the link to download the AdobeReaderPatch10.1.2_cpsid_92870.zip  file.
  3. Unzip the file to extract the executable AdobeReaderPatch10.1.2_cpsid_92870.exe.
  4. Close Adobe Reader if it is running.
  5. Do one of the following to run the AdobeReaderPatch10.1.2_cpsid_92870.exe file:
    1. Double-click the AdobeReaderPatch10.1.2_cpsid_92870.exe file.
    2. Run the AdobeReaderPatch10.1.2_cpsid_92870.exe file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.
      Example: <path to AdobeReaderPatch10.1.2_cpsid_92870.exe> -silent
  6. Once the process is completed, you receive a prompt stating the result of the operation.
    Note: When run in silent mode, all dialog boxes are suppressed. No success message or error message appear.
  7. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log. (The changes sometimes only take effect after you restart your computer)

Option 2: create share names for all network printers

  1. Go to Start > Devices and Printers.
  2. Access all Network Printers installed on your machine.
  3. Right click on each network printer to access the printer properties.
  4. Goto the Ports Tab and verify the printer is a network printer (i.e. it is using a “Standard TCP/IP Port”).
  5. You only need to continue if this is a network printer.
  6. Open the Sharing tab and give your printer a “Share name”.
  7. If you wish not to share your printer then you may choose to give it a “Share name” and then select the “Do not share this printer” checkbox.
  8. Please ensure that all Network printers have been assigned a Share name otherwise the problem will persist. Please find below a screenshot for your reference.

Option 3: disable protected mode

The second work around is to turn off the Protected Mode of Adobe Reader and the problem will be resolved right away. However, it is not advised to keep the application in non-protected mode for security reasons.  It is advisable to turn this setting ON once you are done with your printing task.

You can access this setting by going to Edit–>Preferences–>General, and un-check the option “Enable protected mode at start-up” at the bottom of the window. You will need to re-start the Adobe Reader after you have made changes to this setting.

reference: (3088576)

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