Crash on Output Module

Hi,
Seem to have an ongoing issue.
When i go to render on an existing or indeed brand new project regardless of content my AE crashes.
I choose render, then go to output module settings. Click format options and it crashes.
A copy of your project was saved at: /After Effects Crash_1.aep.
Last log message was: <140735166022416> <ae.blitpipe> <2> Making New Context
Generating crash log, which may take a few minutes.
I then get this message - and the report crash window.
Apple Mac Pro (late 2013)
10.9.5

Wow that's quite a list of requirements.
Adobe After Effects CC 2014.0.2 release 13.0.2.3
Apple OSX 10.9.5
All adobe and apple updates are complete
Error message:
A copy of your project was saved at: /Documents/After Effects Crash_3.aep.
Last log message was: <140735207072528> <ae.blitpipe> <2> Making New Context
Generating crash log, which may take a few minutes.
Workflow to get error: Render, output module settings. Click format options and it crashes.
No idea what has changed on the computer but this is only a recent thing as i had been working on a project a few weeks ago and all was fine.
Multiprocessing is switched off
OpenGL is not supported on my graphics card
Processor  2.7 GHz 12-Core Intel Xeon E5
Memory  64 GB 1867 MHz DDR3 ECC
Graphics  AMD FirePro D700 6144 MB
Quicktime is installed Version 10.3 (727.4)
Am just in the process of uninstalling the application and will reinstall clean with no plugins. Hopefully this will fix the issue.

Similar Messages

  • AfterEffects CS4 Crash on Output Module Windows Media

    After sitting on hold for 2:15:00 yesterday, I have yet to discover humans working support, so I turn to this forum....
    I own CS4 Production Premium, on a HP Z800 with XP64, sp2 and 16gb, nvidia quadro fx 3700.
    Since installing it several months ago, I have not been able to use the render que in After Effects CS4. When an item is in the render que, selecting the "Output Module", and then selecting the "Format" drop down, as soon as I release the mouse on the "Windows Media" option, AE begins a predictable crash routine.
    No matter what the project is, this is the same result.
    What is remarkable is the fact that I can run Adobe Media Encoder and render perfectly fine to this format. But this is an awkward middle man, when I'd really like-and should be able to, to encode the project directly from AE, not AME. Premiere also renders perfectly to this format as well. Only AE appears to crash when activating the Format->Windows Media drop down.
    I've installed the latest 9.0.2 update. I've installed various WME packages from MS. I've uninstalled and reinstalled the entire suite several times. The last alternative is to surrender the machine to the IT guys to set up a clean installation of XP64 again.
    Sure would be lovely if I could speak to a support technician or get some help solving this problem ;-)

    Here's a thread that might help:
    http://forums.adobe.com/thread/429333
    There appear to be some problems with some Windows Media presets.
    Here's a thread about CS3 that seems to indicate the same thing:
    http://forums.creativecow.net/thread/2/971962
    I found these threads with this search.
    BTW, I'm not saying that this is related to this problem, but note that 64-bit Windows XP is not one of the operating systems that we recommend for After Effects. Here is the system requirements page.

  • CS4 Output module crashes with Snow Leopard

    I have had many problems with Snow Leopard in my Mac Pro (1,1), which all seem to have been resolved by erase installing, with one exception.
    The one exception is trying to make contact sheets with the Bridge output module.
    It is particularly prone to spinning beachball then crash while entering settings, eg header footer etc.
    It doesn't crash every time, but often enough to be a real trial.
    The behaviour has been the same between my initial SL upgrade of my "dirty" Leopard, and a cleaner-than-clean fresh erase/install of SL and CS4 only, with all the usual troubleshooting in between.
    Is anyone else getting this problem?
    I would also really like to hear from anyone who is successfully using CS4 output module with Snow Leopard.
    Thanks

    I have a RIP on a PC creating 1-bit TIFF files. They open just fine in Photoshop or other 3rd party programs. However when I try and open them in preview they immediately crash the program. Now I have also noticed that when I select the item and try to get info (to change the default program to open with) the FINDER crashes too!
    Getting info on a file can actually crash the Finder? C'mon Apple gimme a break here... a 1-bit TIFF should be no problem.

  • CS4 AE output module crash (0::42)

    PROBLEM
    selecting F4V, FLV, MPEG2, MPEG2-DVD, or Windows Media in the Output Module immediately causes 0::42 message to pop-up:
       "After Effects can't continue: sorry, After Effects has crashed... ( 0  :: 42 ) "
    after which AE exits to desktop.
    SETUP
    Intel Xeon CPU E544 dualcore 2.83GHz, 4G RAM
    NVIDIA Quadro FX 1700
    WinXP Pro X64 SP2
    WRONG ANSWERS
    1) updating AE 9.0.0 to 9.0.1
    2) quicktime safe-mode... QT version is 7.6 (472): tried Preferences > Advanced > Safe mode (GDI only)
    3) turning off Hardware Acceleration (Desktop > Properties > Settings > Advanced > Troubleshoot)
    4) remove OpenGL plugin (renamed file to AE_OpenGL.AEX.hide)
    5) rebuilt AE preference file (ctrl-alt-shift after starting)
    tried all these with no improvement.
    rendering to QuickTime and AVI hasn't been a problem (at least not with the codecs i've tested so far)
    i'm surprised i haven't found more postings on this glitch so i'm hoping i've missed something obvious i should check.
    any suggestions?
    -rob

    Actually your attempt to launch AME gives it away - if a preset is referring to a non-existant CoDec or missing template, it will crash. I don't think this has ever been any different even in the past, but usually the advise then was to re-install everything. The question in your case is, why it would frown on the preset. Did you modify it in any way and save it under the same name? Was it perhaps damaged by a previous crash? Another Thing: did you perhaps install something in a different language? Unlike AE, AME cannot be forced to use a different lanuage and may not see any presets at all, if they are in a different language...
    Mylenium

  • "...an Output Module failed" error screen...

    Greetings AE Peeps!!
    Long time - no see - been stupid busy. My Studio has just ponied up and upgraded our 5 Edit Stations to AE CS5. I personally am a huge advocate of not upgrading software while in the middle of a project, but this was out of my control. I am having a lot of crashing (app just quits for no reason while scrubbing) and other weirdness...like today. I am rendering a 3 minute piece in ProRes 4:2:2 (1280x720p) to my RAID (no special plug-ins or anything) and I get the following error at the very end of every render:
    After Effects Error: Rendering error while writing to file (insert my RAID path here). An output module failed. The file may be damaged or corrupted (-1610153464)
    I have never in 11 years got a "failed Output Module error". Can anyone speak to this and tell me how to get rid of it short of reinstalling AE?
    Grazie! Ciao!
    Joey

    First, make sure that you've installed the After Effects CS5 (10.0.1) update.
    Regarding the output module failure: It may be that this is because you have an output module created in a previous version of After Effects that refers to a codec or set of settings that isn't working in After Effects CS5. The best thing to do is to remove the output modules from the render items and then rebuild them in After Effects CS5. That may sound tedious, but you only need to do it once, and then you can save output module templates that you know work with After Effects CS5.
    As Mylenium suggested, there are some challenges associated with the fact that there is no 64-bit QuickTime, so we had to create our own 32-bit-to-64-bit QuickTime conversion layer (QT32 Server). QuickTime does work with After Effects CS5, but there are some hiccups in some cases on first use.
    If this doesn't help, answer back and we'll help you through.
    Oh, this might be useful, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • AE CC Render error output module failed

    Hi, I tried my best to find this answer on the forums but couldn't find anything current.
    I have isolated two issues in AE CC where I can duplicate a failed render with this message:
    After Effects error: Rendering error while writing file "xxx". An output module failed. The file may be damaged or corrupted. (-1610153464)
    This happens when opening an AE CS6 project and trying to render a simple comp with only one text layer and a moving mask. It also just happened after my first round trip test with Cinema 4D. I could RAM preview the c4d layer but the output to Quicktime h.264 failed.
    I have even tried a full reinstall of AE CC. I have the basic FxFactory Pro plugins and MagicBullet Looks installed, but neither are being used since this is a single 1280x720 comp with a single C4D layer. Plus like I said it failed with the same error in past CS6 files.
    I don't know how to force disable a plugin to test that, but I can't see how an unused plugin could cause a render to fail like this.
    I'm on a new (late 2012) 27" iMac
    3.4 GHz Intel Core i7
    8GB RAM
    NVIDIA GeForce GTX 680MX with 2GB VRAM
    OS X 10.8.4
    AE CC 12.0.0.404
    CUDA driver 5.0.59
    Thanks for any suggestions!
    Matt

    Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
    http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime- errors-with-after-effects.html
    There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
    The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
    The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
    If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
    In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
    To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
    Hope that helps!
    Matt

  • 2 error messages - failed to install extention 2.1 and output module 2.1

    I just tried to update my Encore CS4 from the Master Suite. I have two error messages " failed to install extention Mgr. CS4 2.1 and failed to install output module update 2.1
    Encore will load a new project and save but I can't do anything else like add files before it crashes.  Any help please. - Art

    This might not apply with En CS4, but there were some issues on install, and on updates in Photoshop. It seems that MS had a bum MSI (Installer) version, and it caused a lot of PS installs and updates to fail. Do not recall any specific error messages. The cure there was to download and install the revised MSI module from the MS site. I would imagine that any MSI module would be heavily Windows version-specific. Take that as a warning to check any very carefully, before downloading and installing. MS is pretty good at having a ReadMe with installation instructions for each such download. It almost always contains the exact versions of Windows, that the file is for. Please read any installation instructions carefully.
    This might be worth a look. I do not have a link to the exact page, but a search of the MS site should yield something. I'd search for "MSI," to start.
    I just do not recall any issues with En and either installation (on proper systems with updated OS's) or with any updates.
    Good luck, and please report your success.
    Hunt

  • Output module, missing plug-in error message

    Hi there
    I'm running AE CS5 on my macbook pro and until yesterday it's been working fine. Now when I open it it comes up with this output module, missing plug-in message:
    And then this one:
    Then it crashes completely.
    I researched it a bit online and discovered it could be some security software interfering so I tried logging in with another user account and AE ran fine.
    I need to run it from my main user account. Does anyone know how I can fix this?
    Many thanks!

    Hi there, so I have tried to repair permissions. I did this while logged into my main account (the one AE keeps crashing in) and selected 'repair permissions' for the Mac HD. I'm not sure if I was supposed to select specifically the Applications file but this wasn't an option. I restarted but AE still crashes.
    I also tried copying the AE folder to my desktop and starting it from there and installing all software updates.
    The firewall is off and it works from the other user account. I'm not sure any of the other things on the list apply. There were a few suggestions involving files and RAM around but I wouldn't want to mess around with that as I'm not sure what's supposed to go where.
    Any more ideas would be much apreciated!
    Thanks again.

  • Automationdirect P3000 Modbus Communication Lookout 6.5 for +/- 10V Output Module

    Here is an iquiry I sent to Automationdirect tech support last week.
    I have not had a response from them yet so I thought I would throw it up here.
    Hello,
    I am starting a new project with the P3K and I am using Lookout 6.5.
    This is my fourth installation with this combination and I have learned a bit more about the Modbus communication each time.
    I use the Modbus serial object in Lookout to communicate via RS-232.
    With my first project, I learned to set the "Modbus Server Settings" in the P3000 software to map to a single 16 bit Modbus register to get the communications working with Lookout and making sense with the analog registers.
    For a 10V input I would linear scale in the PAC 0 to 65535 = 0 to 10000 then in Lookout I simply divide by 1000 to get the decimal in the right place.
    On the most recent project, I discovered I could map/scale my analog inputs to 32 bit foats, select the "map to two consecutive integers" in the P300 software properties and then in Lookout, I could read the register properly with an "F"
    like "modbus1.F400001".
    Now I have a P3-16DA-2, ±10V output module.
    I can't get the float to work and it crashes the communication repetitively.
    It will communicate properly if I stick to 16 bit Modbus register for the "Analog Output, Integer, 32 bit" on the Modbus server settings.
    However, I have the register swap issue reminiscent of the DL205 bi-polar input. It outputs 0 to 10V from 0 to 32767 and -10 to 0 from 32768 to 65535.
    I remember having to add logic in the DL260 PLC and then in Lookout I would use the numerical IF;
    "(nif(DL3.C102,DL3.V2102*-1,DL3.V2102))*-1"
    What a pain that was.
    Is there an easy solution?
    Thanks in advance.
    John B

    Bipolar setups are a pain, it seems your if() is similar to what we did as well.  Added a rung and set a coil...
    Only have a few and have not used the P3000 myself, 
    Forshock - Consult.Develop.Solve.

  • Quicktime Export Error: "An output module stopped responding."

    I'm experiencing an odd export error whenever I use any Quicktime codecs:
    "After Effects error: An output module stopped responding. The file may be damaged or corrupted. You may need to restart After Effects."
    Similarly, Adobe Media Encoder hangs when outputting to Quicktime codecs. Neither program makes any progress at all before the hang occurs. At that point, I have to manually "end task" to exit. Also, it doesn't seem to matter what I try to export. In AME, for example, I can simply try to convert one video format to another and have it hang, so I don't think the problem is due to a problem with the source settings or effects. Also, I'm not attempting any multiprocessing since I don't really have enough RAM for that. Other output modules work, so I'm just exporting image sequences for the time being.
    System specs:
    Windows 7 64-bit
    Intel i7-2600k processor
    8 GB RAM
    GTX 580 GPU
    Software:
    Adobe CS6
    AE Plugins include Tracode Suite 12 and Optical Flares
    Quicktime 7.7.3
    Any thoughts on this? I've seen very few references to this error in other places, and not really found a solution that seems to apply to my situation. Thanks in advance for your help.
    Josh

    Thanks for setting me in the right direction. Clicking through to the 25 :: 101 error page (http://myleniumerrors.com/2013/01/06/25-101-4/) led me to a reference about other software, such as remote access software, using the same ports that AE needs for communication with its various processes. In my case, LogMeIn was the culprit. I had no idea that AE even used TCP for these types of operations, so that's very helpful to know.
    *EDIT*
    That worked temporarily, and now it doesn't work. I ran into a similar effect when I first disabled the Windows Firewall. But of course, as I type this and piddle around, it works again. It SEEMS like if I open AME and click into the output settings and scrub through the video preview, it makes everything work when I go to actually export. That's exactly the type of thing I would say is completely unrelated under normal circumstances, but at the moment all I know is that it is currently working and I don't want to test anything else until I finish the rendering I need to accomplish today. I'll work on it more later and post an update at that time.
    Thanks,
    Josh

  • An output module failed. The file may be damaged or corrupted.

    Whenever I try to render something in After Effects CC 13.1.1, an error message pops up, saying "After Effects error: Rendering error while writing to file '[not going to disclose]' An output module failed. The file may be damaged or corrupted (-1610153464)."
    Screenshot of the error message:
    I tried reinstalling QuickTime (7), repaired it, updated After Effects to the latest version(as I am writing this), checked firewall software, and used other formats such as AVI.
    Adobe Media Encoder (CC 2014-latest version) won't work with me, either.
    I sent the composition to Adobe Media Encoder, and this is what I got, no progress here.
    Screenshot:
    It took a while to connect to the dynamic link server, and failed.
    This is a log of what has happened in Adobe Media Encoder.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\tmpAEtoAMEProject-Pink Intro1.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\Pink Intro.mp4
    - Preset Used: YouTube HD 720p 29.97
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: AAC, 320 kbps, 48 kHz, Stereo
    - Bitrate: VBR, 2 pass, Target 5.00 Mbps, Max 5.00 Mbps
    - Encoding Time: 00:00:12
    06/29/2014 02:29:14 PM : Encoding Failed
    The Operation was interrupted by user
    (no need to worry about the above part)
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.wmv
    - Preset Used: Custom
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: Windows Media Audio 10 Professional, 96000 Hz, Stereo, 24 bit
    - Bitrate: CBR, 2 pass, Max 10000.00 kbps
    - Encoding Time: 00:01:42
    11/22/2014 12:24:39 AM : Encoding Failed
    The Operation was interrupted by user
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.mpg
    - Preset Used: Custom
    - Video: 1280x720, 29.97 fps, Progressive, Quality 75
    - Audio: MPEG Audio, 384 kbps, 48 kHz, Stereo, 16 bit
    - Bitrate: VBR, 1 Pass, Min 4.00, Target 15.00, Max 18.50 Mbps
    - Encoding Time: 00:00:11
    11/22/2014 12:52:11 AM : Encoding Failed
    The Operation was interrupted by user
    - Encoding Time: 00:00:51
    11/22/2014 12:53:51 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Encoding Time: 00:00:46
    11/22/2014 08:39:46 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage4.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\montage.mpg
    - Preset Used: Match Source - High bitrate
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 00:00:00
    11/22/2014 10:06:45 AM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    I need some help! Any solutions?.
    Computer Specs:
    AMD FX-6300
    8GB 1600MHz DDR3 RAM
    NVIDIA GeForce GTX 650 Ti BOOST
    1TB 7200RPM Hard Drive
    Windows 8.1 Update 1(with latest updates)
    EDIT(11/23/2014 8:31PM PST): For some reason, other projects work for me just fine. I am not sure why it is not working on one project.
    Screenshot of a new project other than this I am rendering at the time of writing this edit:

    Can other projects can output to the same output location? Yes
    Can other projects render with the same render settings (codec, format, etc.)? Yes.
    If you create a new composition and just add a solid layer to it with no effects in the same project does it render? No. I still get the error.
    Can you render that brand new comp with the same render settings, output settings, output location etc.? Yes.
    If so, what effects are present in the offending comp? Twixtor Pro in all the cinematics/clips, Motion Tile and Transform for pan/crop & wiggle, Magic Bullet Looks and Bad TV Warping preset with just Wave Warp & Venetian Blinds for color correction, Gradient Ramp for text, Bad TV Warping preset with everything for effect, Transform for fade in/out, and ReelSmart Motion Blur v4.1.2 for motion blur.
    Also, what scripts are you using? Just the Move Anchor Point script I found from one of Mt. Mograph's videos, Summit 16 - 2.5D Minecraft Steve - After Effects - YouTube.
    Have you ever installed any third-party codec packs? (I've heard of some codec packs causing weird issues like this.) Yes, (not everything I have, just everything I can think of and find) I have K-Lite codec pack, Fraps, x264vfw, and Xvid MPEG-4 codec.

  • Need help adobe bridge cc output module

    I need help. I have an assignment I'm held up on completing because the adobe cc bridge does not have the output modue I need. I followed the adobe instructions page to the letter. I copied and pasted the output module folder to the adobe bridge cc extensions folder in programs/commonfiles/adobe. The only thing is the instructions then say to paste the workspace file into the workspace folder located below the bridge extensions folder. I don't have a workspaces folder there or anywhere. I even tried must making one and adding the file to it, but no go. can someone PLEASE help me with this?    I have an assignment due like now that requires the use of the output modue.thanks!

    oh,my system is windows 8.1. sorry, lol.

  • Adobe output module in Bridge CC gives Failure at processing

    The output module in Bridge CC isn't standard installt any more, so you have tot do it you self!!!!!!
    After instaling it is visseble and it seemed to work, but during processing it gives the error " 1/0- fout ( = failure in dutch)
    Who know an answer.

    Hello, gooie Dag! Since The output module is an additional module, your question is not exactly one for beginners, I'm moving this discussion to the Bridge forum.

  • Bridge Help /  Install Adobe Output Module is Not working

    New computer so switched to the Maverick OS and moved my CS6 over. Lost my Output Module in Bridge. Went through the all of the resets and downloads recommended by Adobe and I still have not had any success in getting the module back. Would prefer not to reinstall. Any ideas

    What do you mean by "moved 'my' CS6 over" ? ???
    Always install applications from scratch, from the original media.  No exceptions, ever.
    "Migrating", "transferring", Copying, "moving", etc., are GUARANTEED to bring you nothing but grief.

  • After Effects CC Output Modules on Render Only Machines

    Hi there, I'm having an issue with custom Output Module Templates and my renderfarm:
    After Effects CC 12.0.0.404 (showing as up to date in Creative Cloud)
    Mac OS X 10.8.4 (Latest Mountain Lion version)
    Mac Pro 2.93 GHz 8-Core, Radeon 5870, 32GB RAM and with Blackmagic Decklink Extreme 3D+
    Remote Machines (there are four) are Mac Pros as well (Quad-core, running 10.7.2 with 16GB RAM), using the ae_render_only_node.txt file in their user Documents folder.
    The exact error:
    aerender ERROR: No output module template was found with the given name.
    I am trying to get a renderfarm working with After Effects CC (see exact version above). Unfortunately, I need custom output modules and I can't seem to get the render slaves to recognize them. I found older threads on this exact issue, but no solution was found.
    I am using commandline aerender in OS X terminal to start a render with a basic test scene.
    To simplify things, I have tried testing this on one render slave machine at a time... Same result everywhere.
    Here's what I've tried:
    I exported a .aom file from my main machine (where I have my desired custom Output Modules) and attempted to bring it in on the render slaves. However, because the render slaves are render only, (they have ae_render_only_node.txt in their Documents folder), the ability to import Output Modules is disabled in After Effects (it opens as the After Effects Render Engine, and the Edit>Templates menu is greyed out).
    Next, I thought I'd try copying the main machine's /Users/(user)/Library/Preferences/Adobe/After Effects/12.0 folder over to the render slaves, thinking that would get whatever preference file to them that's needed to define the output modules. No luck. Launched After Effects (which loads as After Effects Render Engine) and reset my disk cache preferences (so they weren't still the main machine's). Tried aerender again... no luck. Same error:
    aerender ERROR: No output module template was found with the given name.
    After that, I thought it would be a good idea to sign out of Adobe Creative Cloud on the main machine, and try logging into the render slave machine with my full UserID and Password and temporarily remove the ae_render_only_node.txt file. Then, I'd import the .aom file in the full version of AE... I tried this and success! The renders work... they find the Output Modules no problem. Only issue is, as soon as I sign out, and switch to using the ae_render_only_node.txt file, the Output Modules are not found. Not sure what's going on-- if the Output Modules are being disabled by the ae_render_only_node.txt file? Or maybe signing out of my Adobe ID is removing the preferences that determine Output Modules? Don't know where the Output Module preferences are stored to be able to tell.
    Next attempt: I thought I'd try syncing my preferences with Creative Cloud. I made sure to check After Effects Sync Preferences to ensure that Output Modules are set to sync. I did a sync where I uploaded my preferences from the main machine. Then, on the render slaves, I ran Sync Preferences, and chose to download preferences. Works when signed in, but not when used as a render only node. When it's a render only node, it still prompts me to Download the Sync Preferences and Quit the Application, which I do, but nothing seems to happen. I try aerender again, and still the same error:
    aerender ERROR: No output module template was found with the given name.
    I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?). Are render only nodes not allowed to have custom Output Modules? Not even for something as simple as the Multi-Machine Sequence with a post-render action of Set Proxy enabled?
    Any help is greatly appreciated!
    Thank You.

    I've verified this problem and filed a bug. Sorry about the hiccup.
    I've trying to pin down why this happens, and while I don't have a full explanation yet I think I've stumbled onto a workaround:
    Trash the prefs on the render machine.
    Enable the ae_render_only_node.txt file.
    Launch AE and then quit. <- This is a critical step. More on this later.
    Disable ae_render_only_node.txt file.
    Launch AE.
    Add your Output Module template.
    Quit AE.
    Enable the ae_render_only_node.txt file.
    After you do this, I highly recommend making a backup copy of the Adobe After Effects 12.0 Prefs-indep-output.txt file. Just in case. I've had the failure reappear.
    Now test with aerender and let me know if that works. It has on my machine.
    Why does this matter? When you run AE with the ae_render_only_node.txt file enabled, it appears to add a new section to the preferences: "Output Module Preference Section v28-TRIAL". It's the TRIAL part that is important. Without it, AE doesn't seem to be able to keep track of the OM's when in render_only_node mode. And if you disable the ae_render_only_node.txt file, AE has a tendency to destroy the TRIAL section (I'm still tracing why that happens).
    Now, should this not work for you, I recommend you work around the problem by adding your comps to the render queue in each project. When you do that, and change your aerender flags appropriately, you can render to your desired settings without specifying OMtemplate parameter.
    > I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?).
    You probably already discovered this. In After Effects CC the OM data is stored in the Adobe After Effects 12.0 Prefs-indep-output.txt file. In older versions of AE, a single pref file such as Adobe After Effects 11.0-x64 Prefs.txt holds all of this data.
    Let me know if that workaround does the trick for you. If I get more information on the cause of the problem I'll update you.

Maybe you are looking for