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.

83 :: 2

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: CT bad param: invalid glyphID

Message interpretation:

The program generated an ID for an (Unicode) glyph that doesn’t exist.

Possible causes:

This actually pretty clearly points to a bug – the program or one of the plug-ins should not even be able to calculate a glyph ID that isn’t defined in the Unicode/ OpenType specifications. The exact source of the problem could not be verified, since the user did not provide more info, but it’s reasonable to assume that the issue has long been fixed.

Resolution or workaround:

Always keep your software updated and use the latest certified compatible versions of third-party plug-ins.

83 :: 2

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text

After Effects error: CT generic: not ASCII

Message interpretation:

Text rendering failed because the character was not in the ASCII range.

Possible causes:

Just another weird font error. That’s pretty much all one can say about this one. in the given case the user was running the original After Effects CC with the first update (version 12.1) on a Spanish language Windows system, which should not be a problem at all since the program supports Unicode and OpenType just fine, even if it doesn’t use any of the more refined features. Therefore the error remains a mystery mostly. The only reasonable hypothesis is that a specific character was requested by some routine that is not part of the system’s default language region encoding (for most Western European languages this would be Western/ Latin).

Resolution or workaround:

The only advise here is to check the system’s language settings and adjust them.

83 :: 2

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: invalid table address

Message interpretation:

A font did not return a valid character.

Possible causes:

Similar to many other font errors this one remains obscure in that the specific cause never became clear. In human language the error means that a program routine requested a character code from the glyph table of a font, but this request came up empty because nothing existed at the given address. Aside from usual suspects like language conflicts and damaged fonts this could also indicate problems with symbol fonts that are used to render arrows, dingbats, window and panel header elements and that sort of thing, which often is not clear to the user.

Resolution or workaround:

Start following standard procedures – use your system’s font management tools to inspect and verify all fonts are intact and accessible. If you use third-party font managers, turn them off (temporarily) and see if the issue goes away. When you have huge numbers of fonts on the system, strip them down to only what you really need. Not only will this get rid of potentially damaged fonts, but also helps system performance. If you use a custom interface theme on Windows, switch back to the default themes, so customized UI font elements may no longer be referenced. Finally, check your language and region settings to ensure that you don’t use specific character sets from a different region for which you may have no suitable font on the system.

After Effects warning: Could not find the user documents directory.

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects warning: Could not find the user documents directory.

Message interpretation:

The program cannot find the documents folder in order to store files.

Possible causes:

This error can occur when you are running older versions of After Effects on contemporary operating systems and have (not yet) saved the project to a specific location while at the same time using auto-save or rendering out bits of your work. In such a situation the program will use the global default Documents/ My Documents folders to store log files and the backup files. Since modern systems use different default user permissions, this can go wrong just as it may not work when security tools may block access to those system folders.

Resolution or workaround:

Start by making sure you run as a user with adequate permissions and always make sure to save your project. That way any log files or auto-saves are placed in sub-folders relative to the project, not the system folders. To avoid those issues in the future, verify your folder permissions and configure your security tools to exclude these folders or at least After Effects files from surveillance. Some basic guidance on this can be found here.

After Effects warning: Can´t write to font cache directory.

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects warning: Can´t write to font cache directory.

Message interpretation:

The program cannot access the font cache.

Possible causes:

This is a quite generic issue that may come up every now and then. In the given example the application refused to launch because it could not buffer some menu or panel text used on the interface. This can have all sorts of causes from normal file permissions and user privileges issues to other tools interfering with access to these folders.

Resolution or workaround:

Verify that you have proper access to all font directories on your system. Some info about their location can be found on this page. Check the permissions and change them if necessary as explained in this article. If external tools seem to be the issue, configure them suitably or disable them. Create an exception rule in your virus scanner and firewall and similarly tell any font management tools to not hide or block fonts. In addition check for damaged fonts and remove them from your system. Some of those issues may also require to reinstall your Adobe application to put the right fonts and folders in place or straighten out version conflicts between different products. Some more info can also be found on this Adobe help page.

10 :: 48

Englische Version des ArtikelsFranzösische Version nicht verfügbarDieser Artikel ist in DeutschSpanische Version nicht verfügbarItalienische Version nicht verfügbarChinesische Version nicht verfügbarJapanische Version nicht verfügbarKoreanische Version nicht verfügbar

Fehlermeldung:

After Effects Fehler: Eine Speicherzuweisung von 17179869176,0 GB überschreitet die internen Beschränkungen. Verringern sie die Speicheranforderungen für das Rendern dieses Frames. (12802).

Interpretation:

Es gibt nicht genug Speicher, um einen Frame zu rendern.

Mögliche Ursachen:

Dieser Fehler ist neu in Creative Cloud 2015 (Version 13.5.0). Aufgrund der Überarbeitung des Renderers gibt es Bugs, und das ist einer davon. Die spezifische Ursache bleibt ungeklärt, weil der Fehler nur in bestimmten Kombinationen von Quellmaterialien auf bestimmten Systemen auftritt. Wen nes passiert, landet das Programm in einer Endlosschleife und man muss es “abschießen”.

Problemlösung oder Workaround:

Da es ein Bug ist, muss er in entsprechenden Updates behoben werden.

10 :: 48

This article is in EnglishFrench version not availableGerman version of this articleSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: Memory allocation of 17179869176,0 GB exceeds internal limits. Decrease the memory requirements for the rendering of this frame (12802).

Message interpretation:

There is not enough memory to render a frame.

Possible causes:

This is a new error for Creative Cloud 2015 (version 13.5.0). Due to architectural changes in the render pipeline there are still bugs and this is one of them. The specific cause remains unresolved, as it appears to happen arbitrarily when using specific source file formats on systems with a certain configuration. When it happens, the user ends up in an infinite loop and can only forcibly terminate the program.

Resolution or workaround:

This will have to be addressed with updates. For the time being stick with CC 2014.