We have the same issue on 2 out of 3 workstations.
Any news on a fix?
I'm getting this too. I'd like to know if Adobe is aware of the problem and working on a fix or not.
FYI, I filed a bug report with Adobe at the previously-posted link. Whether it's a known problem or will receive any attention is impossible to say.
Someone on the Adobe Media Encoder team is looking at it.
We haven't seen this exact error, and are looking into it. I can share that we did run into a rare case where updater did not work the first time it ran. It would say that it updated AME, but if you run the updater again, it would want to update AME again. That happened to only one of our testers a few times and was random and not easy to reproduce.
The solution was to run the updater a 2nd time. That fixed it for him every time. I don't know why on some machines it required it to be ran a 2nd time, but in no case did we experience this problem after running the updater a 2nd time.
We are trying to get a downloadable patch posted as well. Once that's up, users can run the downloadable patch which should not have this problem.
For now, I would like to know if running the patcher a 2nd time solves the problem for you or not. If you continue to run into this problem, we should have a downloadable patch available for you run which should hopefully solve this issue.
AME QA team
I have the same problem.
Re running update again, it won't let me as it thinks all updates were done. If I try to run updater again it says "your applications are all up-to-date".
AME version number after the update is 184.108.40.206 (64-bit).
Running updater a 2nd time is not an option, unless there's some manual way to force the update.
On my machine the updater option is checked "Send reports to Adobe on success or failure of update application". You should be able to correlate failed updates to this problem, if there is any connection.
If there's an update log on PC which can be manually inspected, please post the specifics and those which have this problem can report.
Adobe simply needs to examine the AME source code to see what item (registry key, file, etc) it's inspecting to judge the version. Then determine why it didn't get updated, and whether the entire update failed or just the registry key, etc. didn't get updated. The corrective action needed will be based on knowning those details.
I have the same problem. Adobe Premiere Pro 5.0.2. I just do normaly, click EXPORT > Media.
I get that message that says an update is avaiable, I click ok. Then the normal window appears. I click Queue, the window disappears, I see the "exporting prject" loading windows and ... that's all. Adobe Media does not load.
I have some questions for everyone experiencing this problem:
- BigPET stated that when he tries to queue an export from Premiere Pro to Adobe Media Encoder, AME does not launch. Does anyone else experience this problem?
- In the list of Formats in the Export Settings dialog in Premiere Pro (File > Export > Media, click on Formats), is MPEG2 MXF listed? This is a new format provided by the Premiere Pro 5.0.2 update. The presence of this format tells us if particular files for Premiere Pro were updated.
- Same question as #2, but for AME.
- Are the applications installed at the default location? ( C:\Program Files ) If not, where are they installed at?
- How did you install Premiere Pro? Did you start with the trial version before getting a serial number? Did you download it or did you have the physical discs? Is a part of the Production Premium or Master Collection suites, or do you only have Premiere Pro?
Thanks for your patience while we untangle this problem.
-=Adobe After Effects/Adobe Media Encoder QE
The program is installed in E:\Program Files.
Don't have enough space on C.
I found a fix around this. I just manually open Media Encoder. I still get that "update is available message"... but when I click the QUEUE button to export the settings to Media Encoder, media encoder is already open and it recieves the "whatever is requied to recieve"... so I can start the encoding.
I'm experiencing the exact same issue.
2. MPEG2 MXF is available in Premiere Pro
3. MPEG2 MXF is available in AME
4. No, D:\Program\Grafik\Adobe
5. Never installed trial. Have the physical discs and updated to 5.0.1 and then 5.0.2 through update notifications. I have all of the Production Premium installed.
My results on Tim Kurkoski's questions:
1. AME fails to launch if queued from Premiere Pro?: No. Works OK after I dismiss the "Media Encoder Update is Available" message.
2. Is MPE2 MXF listed under Export Settings dialog (File > Export > Media, Formats): Yes. Also export to that format works OK after dismissing the "Update is Available" message.
3. Yes, MXF export option listed in AME.
4. Installed at default location? No, at e:\Program Files\Adobe
5. Installed by download. Production Premium.
Thank you for your patience and feedback as well as installation info.
We are still looking into this issue, but we do have a solution for you.
To solve this issue, you can put a shortcut of AME application in PPro folder and then PPro can find AME and launch it without errors reported in this thread. Follow these steps:
1. Using Explorer, go to the folder
C:\Program Files\Adobe\Adobe Media Encoder CS5\
2. In that folder, you should find the AME application called
“Adobe Media Encoder” or “Adobe Media Encoder.exe”
3. Right click on that file and select “Create Shortcut”.
A shortcut of that file will be placed in the same folder.
The shortcut file will be called “Shortcut to Adobe Media Encoder.exe”
4. Copy the shortcut to your PPro folder.
Most users who have this issue have installed PPro to a different folder rather than the default installation location. Example: copy the above shortcut you created to E:\Program Files\Adobe\Adobe Premiere Pro CS5\
5. Rename the shortcut from “Shortcut to Adobe Media Encoder.exe” to “Adobe Media Encoder”. If you have elected to show the file extension, it may have .lnk at the end of the file which should remain.
6. If PPro is open, close it and re-launch it. You should now be able to launch AME from within PPro without an update reminder or other errors.
That should do it.
Please do let us know if this solution does or does not work for you.
These specific steps worked; however, can you comment on why AME is installing in a different directory then I told that application to install it too? There are residuals of AME in the location I instructed it to install too. It is quite possible that a C:\.. path is hardcode in the installation file is the root of this issue, as the reference to the application in my registry is NOT pointing to the location it is actually installed.
I confirm this procedure worked for me, both from within PP CS5 and when running AME separately. Thanks for the solution.
This illustrates during QA the importance of testing to a non-default install location.
We did test patching with Premiere installed to a non-default path. We also tested exporting to AME with Premiere installed to a non-default path as well as exporting to AME after patching. The app passed all those tests.
The hole in our test plan was that we didn't install to an alternate path *and* patch *and* export from Premiere in the same test. Of course, the bug was hiding in the confluence of those two conditions. One of the great challenges of testing software is deciding which combinations of conditions to test--you don't have to go very deep before the number of tests mushrooms out of control. That said, this is one combination that should have been covered, and you can rest assured that it will be in the future.
Mark, thanks for that explanation. I was not affected by this, but like information about how such things come about. For me it builds credibility.
Mark - thanks for the explanation. I understand the challenges with QA efforts and appreciate the hard work you are doing on this.
the steps suggested in the article are not working .it doesn't happen until the product is not updated. after update the issue is there. premiere pro is installed in D drive. haven't tried installing it in default location yet. please suggest something.
All Adobe programs really like being on C:\, though the actual folder does not seem to matter.
Please doublecheck that the shortcut's name is simply "Adobe Media Encoder". When I create a shortcut in Windows 7, its default name is "Adobe Media Encoder.exe - Shortcut,", so I have to strip off ".exe - Shortcut".
If the shortcut name is correct and you're still running into this problem, a second partial workaround is to manually launch AME before exporting from PPRO. You will still encounter the prompt to update AME, but clicking OK in that dialog allows you to proceed. When you click Queue in the Export Settings dialog, your sequence should be added to AME's queue.
This is excellent to see all you Adobe people getting involved in sorting issues out via these forums.
I know this belongs on another thread, but I am just loving PPro CS5 especially after the 5.0.2 update fixed my speed and lag issues.
Great work - keep it up!
I tried the recommended ‘fix’ by creating a short cut of Adobe Media Encoder on my C: drive and copying to Premiere application folder on my D: drive per the instructions and I still receive the ‘warning message’ . An Adobe tech told me ‘ Adobe does not support applications that are not installed on the default folder(C: Drive)’ I responded then why did CS5 installer allow me to install on another drive.
Like an earlier post I believe something is left in the registry pointing to the C: drive. However even thought I receive the warning message The Media Encoder window is displayed after I click OK to the message and the Encoder exports my sequence.
The knowledgebase article steps worked for me to solve my problem.
I hope that a future bugfix will solve this behavior. My C drive is an SSD and not large enough to install all my apps -- that's what my 2T D drive is for. It is normal for people to choose a different install location than the C: drive.
> An Adobe tech told me ‘ Adobe does not support applications that are not installed on the default folder(C: Drive)’
Please send me the case number for your support case so that I can see who told you this and make sure that this technician is given proper information.
My email address is kopriva -at- adobe -dot- com.
Bad News. I still am getting the message. I followed this thread and tired each of the workarounds, make a shortcut and place in Premiere directory and pre-launch AME.
My Entire Production Premium is installed on C: in the default locations:C:\Program Files\Adobe\....
When the Support tech told me thant I asked if he had anything in writing that stated ' CS5 is not supported unless it is installed on the default drive'. He replied that it was an 'internal document and he could not send it'. I told him I did not believe him and that he was just making that up/
Thanks for looking into the mater
Inducted into The Southern Legends Entertainment & Performing Arts Hall of Fame 2002
AndyUrtu: If you have Production Premium installed to the default location, then you're running into a different issue. Please contact me directly (email@example.com) so we can troubleshoot what's going on in your case.
Using the case number that you gave, I was able to look up your case in our system. Looking at the notes for the case, it appears that the technical support agent that you talked to thinks that you're going to try to reinstall to the default location (C:\ drive) and then report back. Is that not your understanding?
We certainly do support installing to drives other than C:, but this particular issue sems to be about a bug that makes that not work properly without a workaround. So, I would also recommend trying to install to the default location if the workaround isn't working for you.
I do not enough room to install CS5 on my C: drive. I will await a fixed app.
Not having enough room on your C:\ can cause, or lead to, other problems. A good cleaning might solve a few other issues, or keep you from encountering them. Also, at about 70% of capacity, performance of a HDD begins to deteriorate, and can go way down quickly.
I have the same problem (no room on my C and the error). What does “about 70% of capacity, performance of a HDD begins to deteriorate” mean?
My C drive is about 75% present full. My G partition (on the same disc) is about 65% full. CS5 is on this drive. My D drive that has all previews and related Premiere files (a 150 gig raptor) is about 55% full. The E drive that has all raw video files (on a 500 gig SATA 2) is about 60% full, and the O drive (an older SATA) with older video files is about 30% full. Does this sound OK? Should I move more older files to the O drive? It "continues to decline to around 50% of the performance with a relatively empty disk" Is it actully better with a more full disc?
NEVER partition a disk. Partitioning is a practice from the last century, when prices for HDD's were € 1,800+ for a 36 GB disk, not with current € 44 prices for a 1 TB disk. Partitioning only causes wear-and-tear, earlier disk failure and decreased performance, none of which you want.
The fuller the disk, the worse the performance. If you approach anything over 50% fill rate, start considering adding disks to your system.
Thanks, I'll take your advice on the next computer build...and begin to move more files onto the comparatively free O drive.