Adobe Media Encoder won't open MPEG2 files

Hi All,
I'm hoping you can help me, I'm having some trouble with Adobe Media Encoder CS4, it won't open any MPEG2 files I throw at it.
They all open fine in Media Player Classic, MPC-HC and VideoLan, so I'm wondering what I'm doing wrong.
Any ideas greatfully appreciated.
Adobe Creative Suite 4 Design Premium
AME CS4 4.2.0.006
WinXP 64

Jim Simon, one came from a creative production house and a couple  came from a website that provides various videos in various formats for  testing video players.
Thanks for the information Colin Brougham.  Can any MPEG 2 importers/decoders be used?
I'm  new to AME so perhaps I don't understand how it works entirely but on  the AME information page on the Adobe website it says that MPEG2 files  can be imported, and there is no mention of only being able to do so  with certain Adobe products (unless I missed it).
However,  if I can open and play MPEG2 Files in various media players, surely  there is a way to use the decoders from those to work with AME?
All advice greatly appreciated.

Similar Messages

  • Adobe Media Encoder won't take mov. files!?

    My Adobe Media Encoder will not take mov. files! That should not be a problem, right? When I click the Add-button the mov. files is not listed up unless I choose to show all files. And when selecting the file, the program says the file could not be imported -_-
    Probably a stupid newbie mistake, but can anyone tell me what it is?
    I have downloaded the latest flash CS4 trial package, which include the encoder, and am trying to encode files provided with adobe's book "Adobe flash CS4 professional - Classroom in a book"

    I found the answer. I needed to install Quicktime lol

  • CS6 Media Encoder won't open at all...

    I installed CS6 Master Suite... Media Encoder won't open at all. No error message... nothing when I click on the icon.  I opened a project in Premiere... exported it to the Que... No media Encoder window..
    Help please... I'm dead in the water....

    Try holding down CTRL + ALT + SHIFT while launching AME, that's another way to clear prefs.  If that doesn't work, try deleting these two folders (NOTE: this will delete any custom presets or workspaces you've created):
    C:\Users\<username>\AppData\Roaming\Adobe\Adobe Media Encoder\6.0\
    C:\Users\<username>\AppData\Roaming\Adobe\Common\AME\6.0\

  • Adobe Media Encoder won't start

    Not OP, but I have the same problem. AME just won't run. Double click, it's loading, I can see the process in Windows Task Manager but it just goes away again. Tried deleting that watch folder .xml but not working. Here's my spec from the FAQ:
    What version of Adobe Media Encoder? Include the minor version number (e.g., Adobe Media Encoder CS6 with the 6.0.1 update).AME CC from premiere cc 7.0.1
    What other Adobe applications do you have installed, and what application are you using Adobe Media Encoder with?Premiere Pro. Premiere Pro
    Have you installed the recent updates? (If not, you should. They fix a lot of problems.)Used creative cloud to update to latest version
    What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".Windows 7. All update patch installed.
    Are you using Adobe Media Encoder through a Creative Cloud Membership subscription?Yeah
    What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".N/A. App won't launch
    If you are getting error message(s), what is the full text of the error message(s)?No error message
    Is the problem only occurring with a specific output format or encoding preset? If so, which one? If this is a custom preset not included with AME, then upload the preset file to a file-sharing site and provide a link.No.
    What were you doing when the problem occurred?Booted up the computer. Launch AME.
    Has this ever worked before?Yes.
    What other software are you running?Google Chrome
    Do you have any third-party codecs installed?Avid DNxHD, Cineform Studio
    Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).Regular desktop
    Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro?Yes.

    I have a problem like this:
    Anybody HELP?
    Process:         Adobe Media Encoder CC [16188]
    Path:            /Applications/Adobe CC/*/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
    Identifier:      com.adobe.ame.application
    Version:         7.2.0.43 (7.2.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [253]
    Responsible:     Adobe Media Encoder CC [16188]
    User ID:         501
    Date/Time:       2014-02-05 01:15:39.418 +0100
    OS Version:      Mac OS X 10.9.1 (13B3116)
    Report Version:  11
    Anonymous UUID:  7E5DC048-8DD8-5DA9-CFD0-539F29161D59
    Sleep/Wake UUID: D2BBCDCA-68C3-4C86-B34D-57E4C884FDD8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x00007fff8a1c2866 __pthread_kill + 10
    1   libsystem_pthread.dylib                 0x00007fff8998835c pthread_kill + 92
    2   libsystem_c.dylib                       0x00007fff8f10dbba abort + 125
    3   libc++abi.dylib                         0x00007fff95124141 abort_message + 257
    4   libc++abi.dylib                         0x00007fff95149aa4 default_terminate_handler() + 240
    5   libobjc.A.dylib                         0x00007fff9413c322 _objc_terminate() + 124
    6   libc++abi.dylib                         0x00007fff951473e1 std::__terminate(void (*)()) + 8
    7   libc++abi.dylib                         0x00007fff95146e6b __cxa_throw + 124
    8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
    9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
    10  com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
    11  com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
    12  com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
    13  com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
    14  com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
    15  com.adobe.ame.application               0x0000000100056a38 main + 424
    16  com.adobe.ame.application               0x0000000100003f74 start + 52
    Model: MacBookPro11,3, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f3
    Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
    Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.49)
    Bluetooth: Version 4.2.1f2 12982, 3 services, 23 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SM1024F, 1 TB
    USB Device: Internal Memory Card Reader
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

  • Why does Adobe Media Encoder fail to export Quicktime Files?

    I'm using Adobe Media Encoder CC 2014 on a Windows 7 Pro 64 bit PC.
    While exporting the Quicktime variant of H.264 for ATSC television broadcast files, Adobe Media Encoder fails.  Non-Quicktime H.264's render correctly, but some television stations require quicktime.
    Troubleshooting reveals the problem only occurs when attempting to make a 1920x1080 H.264 QuickTime file.
    Using the same original file (1920x1080), Adobe Media Encoder WILL export a 720x480/486 H.264 MOV file.
    More interesting still, it will ALSO export at 1280x720.
    Testing this information to it's limits, I found that the cutoff for a successful render is between a frame size of 1610x906 and 1609x905.
    Useless, random sizes, I know... but that's the breaking point for Adobe Media Encoder CS6 (6.0.3.1 to be precise) and H.264 Quicktime files.
    Others are having a similar problem:
    http://forums.creativecow.net/thread/3/934721#953485
    This information did not correct the problem:
    http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-warning-or.html
    Any help or ideas are greatly appreciated.
    OS:  Windows 7 Professional 64-bit SP1
    CPU: 41.6GHz (dual octo-core Intel Xeon E5-2670 @ 2.60GHz)
    RAM: 64GB
    GPU: NVIDIA Quadro 5000 v334.95 (2.5Gb GDDR5 RAM)
    VID: Blackmagic Design DeckLink HD Extreme 3D+/Desktop Video v10.1.1
    DRV: Facilis TerraBlock 16TB RAID/ATTO ExpressSAS R680 v2.19
    NLE: Adobe Premiere Pro CC 2014
    James Brady
    Senior Editor
    Results Video, Inc.
    El Paso, Texas
    http://www.resultsvideo.com

    I'm trying to make a file with the extension ".MOV" using AME's "HD 1080i 29.97, H.264, AAC 48kHz" preset.  AME fails every time with the following message:
    "Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error."
    Any other file extension (MP4, M4V, etc.) renders fine.  The issue seems only to happen when attempting to make an MOV file.  It doesn't seem to matter whether I use AME's built-in preset, or customize my own render settings--the problem always happens with any MOV larger than the size I mentioned above.
    All of this used to work just fine on the same machine 2 years back with Adobe CS5, previous version of windows and QuicTime.  I've been all through the Adobe and Windows possibilities, so I'm grabbing at straws here with QuickTime maybe having something to do with it.
    Interesting.
    Would you happen to know if Adobe has made any changes to its manner of muxing long-address MPEG-4 AVC data to the MOV file container? Since the MP4 and M4V files encode properly, have you tried opening these files in a media player and simply using the "Save As..." option to move the date to an MOV file container without transcoding audio or video data? I.e., is there any obvious relationship between the size of the MOV file encode (less than/greater than 4 GB) as a function of the resolution "break point" previously discovered?

  • Adobe Media Encoder Doesn't recognize .prproj files

    I am absolutely losing it here. I have read posts on various forums for hours, not only can I not find a solution, I can't find anyone who has this same problem. I'm running CS4 on a Mac and when I try to export from premiere, Adobe Media Encoder opens, then nothing happens. The file is never added to the queue, it just sits there. If I open Adobe Media Encoder manually then click add and try to select a premiere project, the file is grayed out. I changed the dropdown menu for file types to be "all types" and I click on a premiere file and it just pops up an error message saying the file cannot be imported. Same thing if I try to drag the file in. I can do absolutely nothing with AME.
    I've seen plenty of people saying AME crashes midway through rendering or people saying they get an error saying to check if the source has been moved or deleted. I don't get any of that. I have nothing. It doesn't show up in the log or errors in any way.
    The most annoying thing is that it used to work. I exported several files this way. I did not change any settings though, I even went and restored all the default settings. Still nothing. Its not just the one file, I've tried lots of different files, none work. I even reinstalled premiere, after effects, and AME and nothing changed.
    I'm at a complete loss and I need to get work done and I wish I could post lots and lots of curse words here...

    Hi,
    I use CS3 on a PC so I've no experience with mac problems...
    However, even if I had a mac I would ask you first a little more about your computer....
    I have heard of memory chips going bad on a computer and suddenly that causes things not to work...but there's no sense just guessing...
    Try to tell as much as you can about your computer and about the assets you are using.
    Since it used to work and now it doesn't , can you think of anything you added or changed on the computer ?
    Sometimes adding software or codec packs or hardware can sorta change things on your computer enough to make weird things happen...
    Anyway, give as much info as you can
    I think there's threads here about what sort of info would be best to supply if you don't know much about your computer ...
    Rod

  • Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

    I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine.  I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
    For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs.  When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs.  I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state.  The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were.  Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3. 
    Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great.  However I have noticed a huge speed increase in CS5 64bit AMC.  It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4.  It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
    How to replicate:
    If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import.  If I then add another file with a different resolution AMC will hang and become non-responsive.  It never crashed but I can't wait 12+ hours to see if it accepted a job or not.  As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow. 
    Software used:
    Adobe Media Encoder CS5 windows 64bit
    Adobe Media Encoder CS4 mac 32bit
    System specs:
    Windows 7 home:
    Core 2 quad 3Ghz
    8GB ram
    80GB SSD x25-m
    nVidia Quadro 580
    OSX 10.6.3:
    Dual Xeon 2.99Ghz
    32GB ram
    4 7200 disks in 4TB raid 0
    Radeon HD 2600
    Matrox MAX h.264 compressor card
    Any advice on this situation would be greatly appreciated.  Thank you for your time
    -Michael Emanuel

    Hi Michael,
    Sorry to hear you're having problems with Adobe Media Encoder.  I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem.  For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
    Apologies for the long list of questions; the small details can be important.
    -- After you import the first file, what else do you do in AME?  Change the preset?  Change the settings?  Change the output destination?
    -- What are the properties of the files that are causing the problem?  You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem?  Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate.  If you know more the bitrate, both video and audio, that would be nice, too.
    -- If any of the files are small enough, could you post a couple online that I could try on my machine?
    -- How were these files generated?  What application created them?
    -- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
    -- Which Adobe application or suite do you have installed?  AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
    -=TimK
    -=Adobe Media Encoder QE

  • Adobe Media Encoder won't run

    I can't seem to run my version of Adobe Media Encoder. I get an error which says C:\Program Files\Adobe\Adobe Media Encoder\ CC\MediaCoreUI.dll is either not designed to run on Windows or it contains an error. I have installed the latest update of this product but it still doesn't work. Is there any way of uninstalling it and reinstalling it or do I have to uninstall After Effects and start again?

    We need more information to help you. Please answer all of the questions here:
    http://forums.adobe.com/thread/1011883

  • Media Encoder won't import MXF files from Canon XF100

    I'm running Media Encoder CC on two laptops: a macbook pro and a macbook air. Both systems are running the most recent version of Media Encoder CC (including updates) but only one will import MXF files from a Canon XF100? The macbook air imports and encodes the files without issue, however the macbook pro won't import the same MXF files and kicks the following error:
    The file /Users/.../.../.../AA0106.MXF could not be imported. Could not read from source. Please check the settings and try again.
    I could understand if both computers errored but using the same file, one will import and the other will not. Any help would be greatly appreciated. Thanks.

    Just try this and see if it will work for you.
    Open iPhoto > Preferences > General and deselect 'Connecting camera opens: iPhoto'.
    Change it to 'No Application' and close iPhoto.
    Now connect your camera to your computer and turn it on or better still use a card reader.
    If iMovie tries to open, close it.
    Your camera/card should now appear as an external drive.
    Copy/paste your video files into a new folder on your desktop.
    Eject and disconnect your camera/card.
    Now open iMovie and go File > Import > Movies... and navigate to that folder.
    Z.

  • AE CS4 render engine / Adobe Media Encoder won't create a container for h.264 blu-ray

    here's the problem.
    First, I tried to render a comp using the render engine inside AE using h.264 blu-ray preset.
    It was supposed to create 1 file, but I ended up with 3 : audio track, video and a file with .xmpses extension.
    I then decided to render it in lossless .mov, which works fine, but 3:40 minutes is taking up over 8gb, which is of course, unacceptable.
    After that, I've put the .mov file into Media Encoder to try h.264 blu-ray there.
    Absolutely the same ********.
    I'm using the Mac version of AE CS4.
    Here is the screenshot of original .mov file and the result. As you see, it refuses to make a container. This is absolutely unacceptable

    It raises another question: what settings do I need to encode the comp in 720p resolution without taking up lots of space?
    Well, it depends on whether you need a production master (something for broadcast, for example, or to use as a source for other encoding tasks) or if you want a version for distribution. If it's the former, there's nothing wrong with "lots of space" - A Quicktime file with PNG or Animation codec is a good idea, but it will take a lot of space. If it's the latter, H264 is perfect but there's no built-in preset to take 720 material to the web.
    You could do this:
    * Pick the generic H264 template. You'll see that it will give an error if you attempt to render, because the default setting uses an H264 profile/level which doesn't let you use HD resolutions.
    * In the H264 video options, set the "Profile" menu to "Main" and "Level" to 4.0. That will keep it compatible to Quicktime and Flash player, while allowing larger frame sizes and higher bit rates.
    * Set Target Bitrate to 5-8 Mbps and Maximum Bitrate to 9-10 Mbps if you're targetting web delivery. That's a bit over what Apple uses for 720p content on the Apple TV, for example.
    The H264 original preset will instruct you in the comment field to stretch to 640x480 in Output Module. There's no need, since you are using a profile/level combination which allows higher frame sizes.

  • Adobe Reader XI won't open PDF Files

    I had Adobe Reader 9 and when I tried to open a PDF file or just the program it would open for a few secopnds and then the window closes.  The program doesn't stay open.  I installed Adobe Reader XI but got the same results.  The program window opens for a few seconds and then closes before the PDF file is open.  What should I do to?

    Go to: C/Program Files/Adobe/Reader 11/Reader
    Look for a file named eula.exe (or just eula)
    Double click it
    Accept the license agreement
    Run Adobe Reader.

  • Adobe Media Encoder creates corrupt H264 mp4 file

    I am using Premeire Pro CS5 and exporting an H264 mp4 file from a 720x480 timeline.  For one of the files I am exporting, AME completes the export, i.e. I see a green check mark.  But the file is corrupt.  When I try to open the file with Quicktime, I get the following error:
    "The operation couldn't be completed - (OSStatus Error - 12848)"
    The strange thing is that other timelines exported without any problem.  And this particular timeline I could export using different (but very similar) export settings.  The only thing I'm changing is the video bitrate.  I'm actually creating three different videos for adaptive bitrate streaming, 300k, 550k, and 800k, all from the same video.  The 300k version is the only one that won't work.  But again, what is strange is that other timelines export out fine using the same exact 300k export settings.  It's just this one timeline that won't export without getting the mentioned error.

    I having the same issue. 
    Any insight on a solution?

  • After Effects CC // Adobe Media Encoder won't export H.264 mp4 files

    It stops immediately after "Reading XMP", having exported a defective file (200 kb, about a second long). I've tried several presets in this category.
    Is it a codec problem? What could be the cause?

    Rick means composition,  not compensation.
    But he's right; we need that info.
    Also, is this a dynamically linked project? If so, what exact version number of AE are you using (down to the last decimal)? Also, what version of AME? If not, what format and codec are you rendering to out of AE that you're bringing into AME?

  • Adobe Reader 9 won't open some files -- jp2klib.dll

    I've had this problem for some time, and I think I've at least narrowed it down a bit. The problem is that some (but not all) PDF files cannot be opened in Adobe Reader 9.x on some computers, though they open fine on others. When you click on a problem file, or try to open it from within AR 9, the file may begin to display, but very quickly you get Windows' message "Adobe Reader 9.2 has encountered a problem and needs to close." AR then crashes; or rather, Windows shuts it down. The crash report gives the following basic information:
    AppName: acrord32.exe AppVer: 9.2.0.124 ModName: jp2klib.dll
    ModVer: 2.0.0.4526 Offset: 00032c0d
    I tried copying a different version of jp2klib.dll that was on my computer, but that did not help.
    This problem only occurs on my desktop, not on the laptop, so it seems to be due to some interaction between jp2klib.dll and a specific driver or piece of hardware.
    Does anyone know of a solution to this problem?

    There isn't any video acceleration. This is a pretty old computer. I've got a Samsung 912N flat-screen monitor, an HP DeskJet 6940 printer, an Epson Perfection 3170 scanner, an RCA cable modem, and a U.S. Robotics MAXg wireless router attached to it, as well as an ancient Compaq mouse and a Fellowes Glidepoint touchpad.
    Here's the system information generated by Adobe Reader's Help - Online Support -Generate System Report:
    System Parameters:
    Available Physical Memory: 159908 KB
    Available Virtual Memory: 2007740 KB
    BIOS Version: COMPAQ - 10216
    Default Browser:
    Default Mail: Microsoft Outlook
        mapi32.dll
        Version: 1.0.2536.0 (XPClient.010817-1148)
    Graphics Card: NVIDIA Vanta LT
        Version: 6.14.10.4523
        Check: Not Supported
    Installed Acrobat:
    Installed Acrobat: C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe
        Version: 9.2.0.124
        Creation Date: 2009/10/03
        Creation Time: 4:07:50 AM
    Locale: English (United States)
    Monitor:
        Name: NVIDIA Vanta LT
        Resolution: 1024 x 768 x 60
        Bits per pixel: 32
    OS Manufacturer: Microsoft Corporation
    OS Name: Microsoft Windows XP Home
    OS Version: 5.1.2600  Service Pack 3
    Page File Space: 1208244 KB
    Processor: x86 Family 6 Model 4 Stepping 2  AuthenticAMD  ~901  Mhz
    System Name: MAIN-STUDY
    Temporary Directory: C:\WINDOWS\Temp\
    Time Zone: Eastern Standard Time
    Total Physical Memory: 654896 KB
    Total Virtual Memory: 2097024 KB
    User Name: Dave & Sharon
    Windows Directory: C:\WINDOWS
    Installed Plug-ins:
    C:\Program Files\Adobe\Reader 9.0\Reader\plug_ins\Annots.api
        Version: 9.2.0.124
        Creation Date: 2009/10/03
        Creation Time: 2:39:28 AM
    C:\Program Files\Adobe\Reader 9.0\Reader\plug_ins\EScript.api
        Version: 9.2.0.124
        Creation Date: 2009/10/03
        Creation Time: 2:46:46 AM
    C:\Program Files\Adobe\Reader 9.0\Reader\plug_ins\Updater.api
        Version: 9.2.0.124
        Creation Date: 2009/10/03
        Creation Time: 2:45:18 AM

  • Adobe 9.2 won't open pdf file in Firefox 3.5.3.

    No error message, just blank screen. Adobe plug-in is Enabled in Firefox, and Adobe Reader Internet preferences set to display pdf in browser.  Adobe 9.2 does open in IE 8.  I did not have any issues in Firefox until the Adobe upgrade, so I don't believe it is entirely a Firefox issue.

    - Try checking the settings in Mozilla  (Tools --> Options --> Applications --> Adobe Acrobat Document) and make sure it's set to " Use Adobe Acrobat (In FireFox)"
    - You can also try setting to 'Use Adobe Acrobat 3.5.3' instead of Use Adobe Acrobat (In FireFox). This will open the PDF in the actual program instead of in the web browser. It will use a new window but this is a workaround if nothing else. We prefer this as it opens the in the full program with all features, not just the limited plugin. Since we edit alot of PDF's, we do not have to open them in the plugin, save them, then re-open in the real Adobe program.

Maybe you are looking for