The PProHeadless.exe Error

[Justin Parker]

This just happened to me today for the first time. I don’t know if this is just a coincidence, but my C drive (the one with Vista 64) just went into the red (the warning that tells you that you’re almost out of space)

Could there be a connection the PProHeadless error and system drive space?

For me, my Encore project (which was dynamic linked from Premiere) was making my disc with no audio (was set to ac3)

I also tried to export ac3s directly from premiere and the files ended up having no sound.

[Avelino Sotelo]

I’m having the same issue. I was able to encode about an hour worth of video that I edited. My second movie is where I started having a problem with my encoding.

PProHeadless.exe – Application Error

The instruction at “0x00ea197d” reference memory at “0x00000000”. The memory could not be “written”.

As recall back when I initially converted my MTS video file captured from Canon HD VIXIA camera, I noticed on the status of the clip that was captured had the symbol of a yellow triangle with an exclamation mark instead of a check mark indicating that the movie had problem compiling. I used it anyways to create my project because CS4 Premier Pro was able to view it on the source monitor. So I figure it was OK. I ignored the sign and pursue on working.

So I finished the project and saved. Went to Export to Media which brought me to CS4 Media Encoder. File was extracted, I press start Que. It went through 5 minutes of rendering then stop. Error message appears and had to send error report to Microsoft and I’m back to forums to search for answers.

I’ve contacted Adobe support and I was given the run around in India tech support. I spoke with Simon, Shawn 3 times and finally Sashana.
I was on hold for an hour and I’m not even kidding. So finally I got an answer from Adobe support and they said to download ActiveX. Because they read it in there Adobe forum that another person had suggested. Didn’t work for me.

So I raised my virtual memory to 5117MB

Total page file size for all drives: 5117 MB
Space available: 48981 MB

Initial size (MB) 3070
Maximum size (MB) 50135

Did it solved my problem of PProHeadless.exe Error? Nope…..

So now I went and opened up my last project that was successfully encoded with no problem and try to bring it up again to be encoded using CS4 Media Encoder and see what happens, if I get the same error. So far no problem…I’ll be back later for result and test your findings.

[Igor Ryabchuk]

I recently had this problem with HDV footage, not only PProHeadless.exe refused to work when encoding via Media Encoder, but also Premiere itself would hang a lot – the solution was surprisingly to kill the audio from the video files – it had problems conforming it somehow (because it was happening all the time during editing on the same files again and again). When I deleted audio tracks it exported just fine!

[Josep Marin]

Hi i have this problem when exporting Adobe Premiere I am desperate because I have not found anybody q. Solution to this problem can someone help with the export error pproheadless.Exe. Thank you very much, Josep.

[Gary Olsen]

I don’t get the problem much anymnore, and I think I know what causes it. The connection this application (proheadless) has with the program becomes disconnected somehow, perhaps a system conflict with Windows (that’s what I’m using). I find the problem disappears if I just reboot the system and try again. Sometimes if I’ve been editing for a long stretch, and then I go right to export, the error resurfaces. A simple reboot of the entire system should reconnect all of the necessary utilities that got lost or disconnected in software, and you should be back in business. Every system benefits from a reboot from time to time.

Anyway, it worked for me.

[Francisco jesus Gorrin garcia]

And how can you find corrupted spots/videos in Premiere CS4?

[Dennis Hannah]

Hi Gary Olsen if you have not resolved your problem I was getting the same thing but by including all the relavent files in the same directory on a local hard drive and nothing to do with my operating system. By the way which is (vista 64 bit service pack 2)
the slide show I was high definition 92 pictures music with sound effects, and it worked ok.

[Gary Olsen]

Thanks for your input. In the ensuing months I’ve learned a lot about this error, and you are likely correct in what causes it, however, I have had contiguous files on one drive on a particular project, and I still got the error. And I have a computer so powerful, I have to wear a lead jock just to operate it. So it isn’t necessarily a matter of operating off spec. I got speed, RAM and storage for days. What I discovered, however, is that if you’ve been working for a long period of time on the same project, and you go to make a movie through the Adobe Media Encoder program, the error is likely to appear. If I reboot the system, and try my project again, no error! I’ve become so good at anticipating the error, I can almost predict it will happen. My guess is that this important DLL or whatever it is may lose contact with the project when available scratch memory is in short supply, or it just loses its connection with the project being encoded. And, if a particular clip being rendered is on another disk, as you described, and the disk may have spun down or its connection was interrupted to the CPU (and therefor the project), then the headless error will appear. I’ve even stopped the encoding when the error appeared, waited a little while and and then resumed or restarted the encoding without quitting the application, and the encoding continued on its merry way without a reboot! Hmmmmmmm. Wild! This recovery doesn’t happen all the time, but it has a few times. It’s one of those errors that has become manageable.

[John Garcia]

I have 12 installed CS4 units and 2 CS3 and 1 CS2 all 12 CS4 units have this issue. Which makes me think it is more an application error than a hardware issue.

[Roberto Damiani]

I solved a very archaic.
immediately after starting the rendering process using encore, I open program management, (cntr + alt + del) and na section control how much memory consuming processes PProHeadless.exe. every time you get to high values break the process encore, he established and then continuously PProheadless PROGRASS in encore
By doing so, PProheadless starts emptying the memory.

Conclusion … not a hardware problem, but of PProeadless who can not manage the memory lock when engaged.

I hope it is understandable translation of google.

Roberto Damiani