3 Replies Latest reply on Oct 21, 2011 2:54 PM by Jeremy Denegar

    Adobe Reader 9 crashes on terminal servers

    htrtde

      We are using Adobe Reader 9 (9.4.4) on Windows Server 2008 R2 SP1 with the Remotedesktop Services role (formerly called terminal server).

       

      Usually Adobe Reader is working fine. But sometimes when users want to open a PDF-file, the Reader crashes. The user will see a message saying that Adobe Reader 9.4 ist not working any more.

       

      The logfiles show errors like this one:

       

      Protokollname: Application
      Quelle:        Application Error
      Datum:         01.06.2011 10:53:26
      Ereignis-ID:   1000
      Aufgabenkategorie:(100)
      Ebene:         Fehler
      Schlüsselwörter:Klassisch
      Benutzer:      Nicht zutreffend
      Computer:      server.domain.de
      Beschreibung:
      Name der fehlerhaften Anwendung: AcroRd32.exe, Version: 9.4.2.220, Zeitstempel: 0x4d467676
      Name des fehlerhaften Moduls: CFGMGR32.dll, Version: 6.1.7601.17514, Zeitstempel: 0x4ce7b787
      Ausnahmecode: 0xc0000005
      Fehleroffset: 0x00001295
      ID des fehlerhaften Prozesses: 0x14cc
      Startzeit der fehlerhaften Anwendung: 0x01cc20395e2ac989
      Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Adobe\Reader 9.0\Reader\AcroRd32.exe
      Pfad des fehlerhaften Moduls: C:\Windows\syswow64\CFGMGR32.dll
      Berichtskennung: 9cc0504f-8c2c-11e0-bde4-00155d01da03

      This application crash is not associated with a special file. The file will open later.

       

      There is a nice workaround: Open Adobe Reader first. Then open the document. Everything is fine.

       

      Does anyone have any suggestions or the same problem?

       

      Harald

        • 1. Re: Adobe Reader 9 crashes on terminal servers
          Jeremy Denegar

          We are experiencing exactly the same issue. We'd upgrade to Adobe Reader X but it can't handle mapped network drives that contain mounted volumes (it says's access denied when trying to open files in mounted drives), so we're stuck using Reader 9. Our plan is to find an alternative to Adobe's crappy software.

          • 2. Re: Adobe Reader 9 crashes on terminal servers
            htrtde Level 1

            In the meantime, we abandoned Adobe Reader 9 and upgraded to Adobe Reader X. That's doing much better. But there is another issue instead: We have unclosed processes of the acrord32.exe, which are using much CPU ...

            I hope this will be fixed in 10.1.2.

             

            Harald

            • 3. Re: Adobe Reader 9 crashes on terminal servers
              Jeremy Denegar Level 1

              So now we're trying Foxit Reader... so far, so good. The isntallation can be customized with a transform file (.mst) and everything else can be controlled though simple registry tweaks, specifically:

               

              ------------------------------------------------------------------------------------------ -----------------------------------------------------------------------------

              Windows Registry Editor Version 5.00

               

              [HKEY_CURRENT_USER\Software\Foxit Software\Foxit Reader 5.0\plugins\Updater]
              "IsAutoUpdater"="0"
              "LastDay"=-

               

              [HKEY_CURRENT_USER\Software\Foxit Software\Foxit Reader 5.0\Preferences\General]
              "bShowStartPage"="0"

               

              [HKEY_CURRENT_USER\Software\Foxit Software\Foxit Reader 5.0\Preferences\Others]
              "bShowWelcomeDlg"="0"

              ------------------------------------------------------------------------------------------ -----------------------------------------------------------------------------

               

              In order:

              Disable the auto-update checks (since users wouldn't be able to install the updates without admin permissions)

              Get rid of the last check date (as it's removed when the autoupdater is disabled via the GUI)

              Don't show the start page (which shows mostly advertisements)

              Don't launch the welcome screen at first use, as users can't change some of the settings without admin permissions

               

              Cheers!