Welcome!

Mylenium

Welcome to the After Effects Error Code Database. This site is the collected wisdom of working with the program ever since version 5.0 seasoned and flavored with some general computer knowledge dating back to the early 1990s and spiced with a dose of common sense. Many of the solutions apply to other commonly known problems with other Adobe programs as well and some of it is even relevant on a much broader, generic system level.

I’m trying to keep things as current and complete as I possibly can and provide help, but please understand that I don’t have the resources to buy a new computer every 3 months just to investigate compatibility issues nor do I always have the time and inclination. I have a day job just like everyone else, suffer from a chronic disease that requires lots of medical attention and have to run my household and so-called “normal” life just like you do. When I’m not busy with any of that, I enjoy dabbling around and creating projects just for the fun of it or playing around with cool new plug-ins as a Beta tester. I also do hang around on a couple of forums to answer questions.

I would like to thank all our supporters that have made it possible to keep this site alive for just that much longer, but due to the ongoing problems in financing the site’s running cost and ultimately my own life I feel no longer able to provide the information contained on my site for free. If you need access to the errors, you will have to make a notable donation via PayPal or Flattr for limited time access.

PayPal - The safer, easier way to pay online!

Our supporters:
mettle_logo_small

Mettle produce plug-ins for After Effects and provide a ton of content to go with them, some of it created by me. Other supporters:

Kevin Schires, Alan Eddie, John Urmann, Lourdes Siqueira, Klaus Brandenburg, Sébastien Périer

For updates on current events and other things around After Effects, please visit Mylenium’s Blog.

5070 :: 1

Message text:

After Effects error: Ray-traced 3D: Cannot create context for ray tracer.

Message interpretation:

A RAM preview cannot be generated because the range is supposedly too short.

Possible causes:

This error was only recently spotted and complements all the other Raytrace 3D warnings. The specific occurrence was recorded on a Windows 8.1 system with After Effects CC 2014. Similar to this OpenGL error it indicates that the graphics driver was unable to configure itself to handle the required memory allocation and processing. Since no further details were provided and the user had updated all drivers it can only be assumed that a specific configuration like using too many monitors exhausted all resources or a configuration error prevented the routines from correctly reverting to CPU-only mode, causing the issue.

Resolution or workaround:

First and most forward updating your graphics driver is key to fixing any such hardware acceleration issues. For Raytrace 3D it is further critical that you actually use a hardware that is supported and has enough power to provide these functions. Also make sure to configure your drivers properly so the pertinent bits for GPU mode can be initialized or the program falls back to the slower CPU mode.

RAM preview needs 2 or more frames to playback

Message text:

After effects error : RAM preview needs 2 or more frames to playback.

Message interpretation:

A RAM preview cannot be generated because the range is supposedly too short.

Possible causes:

This issue is specific to the Creative Cloud 2014 versions of After Effects on Mac OS X. It first appeared in the initial release (version 13.0) and is caused by a bug where the program fills the audio buffer until it is full. This seems to be caused by a compatibility issue with certain combinations of audio hardware and Quicktime. It does not occur on all systems and depends on the version of the operating system as well as what specific configuration is used. The specific bug was fixed in version 13.1, but users still report this issue a lot.

Resolution or workaround:

The only reliable way to fix the issue temporarily is a system restart to flush the audio device buffers.

Could not complete your request because of a program error.

Message text:

Could not complete your request because of a program error.

Message interpretation:

An unknown error prevented execution of a command or tool.

Possible causes:

This is perhaps the most generic and nondescript error you will ever come across and it really means nothing beyond the fact that an error was caught by the program because it wasn’t intercepted at an earlier point. This can cover anything from drivers for your scanner, printer or tablet breaking down to incompatible third-party plug-ins or even things like graphics hardware acceleration not cooperating with your graphics driver.

Resolution or workaround:

Since there is no real info in the error message, your only option is to retrace your steps until the error occurs again and then track down the culprit. If it’s hardware related you may need to update drivers, if it’s plug-ins and other stuff, getting updated versions and playing with configuration options may resolve the issues.

5027 :: 12

Message text:

AEGP Plugin MochaShapeConverter : Failed to build correct mocha shape data.

Message interpretation:

Shape data imported from mochaAE could not be interpreted.

Possible causes:

This warning comes up when due to issues with updating either After Effects or mochaAE the shape importer plug-in is a different version from the one required.

Resolution or workaround:

Reinstall the programs and/or manually copy over the correct plug-ins to your After Effects folder, especially when using mocha Pro in place of the version bundled with the default package.

29 :: 0

Message text:

After Effects error: Internal verification failure, sorry! {unexpected match name searched for in group}

Message interpretation:

The name of a property control could not be uniquely identified.

Possible causes:

This is identical to this error and a confirmed occurrence is the warning coming up with “dumb” effects that register no effects property streams like the popular Knoll UnMult in After Effects CC 2014.1 (version number 13.1). When you open existing projects that have the effect applied to a layer the warning comes up. A bug fix is expected in an update.

Resolution or workaround:

Enable capslock when opening the project. Remove the effect and substitute it with another effect like e.g. Channel Combiner or Shift Channels. This issue has been rectified in the 13.1.1 update, so make sure to let the Creative Cloud app check for new versions and update the program.

Unexpected match name searched for in group

Message text:

After Effects error: Internal verification failure, sorry! {unexpected match name searched for in group}

Message interpretation:

The name of a property control could not be uniquely identified.

Possible causes:

This error is related to property groups and the ability to re-arrange some of them. If you e.g. have a shape layer with multiple groups and fills, moving a fill above certain items will cause an error, as it always needs to be applied below (= after) other operators.

Resolution or workaround:

Restore the original stacking order or move your items to places in the hierarchy where they are allowed.