|
After Effects Error Code Database
| If you
want to support this site, you may make a donation
via PayPal.The pages will come up in
German, so if you're a foreign user, please refer
to this help
page for correct procedures. |
|
|
July 26th, 2010
Message text:
After Effects error: AE_OpenGL: Unexpected Condition: No active gl context for line drawing (due to interrupt during N-up frame render?)
Message interpretation:
The view could not be drawn due to an OpenGL problem.
Possible causes:
The error would indicate an issue with internal resource management which terminates OpenGL based drawing prematurely, if multiple 3D views are used. No further details are available.
Resolution or workaround:
Not applicable.
July 26th, 2010
Message text:
After Effects error: AE_OpenGL: Failed to load shader.
Message interpretation:
A specific code fragment could not be loaded and executed on your graphics card.
Possible causes:
This error indicates that your graphics card is either incapable of supporting the required shader features or you have a misconfiguration. More likely it’s the latter, as After Effects should disable these features, if no suitable card is detected. Outdated drivers or unusual configurations may have prevented that.
Resolution or workaround:
Check your graphics driver settings. If you have customized them, reset to factory defaults. Also choosing a different application profile may improve things. Always make sure to install a reasonably new driver which may already fix the issue. if that is not possible, turn off OpenGL in the preferences.
July 26th, 2010
26 :: 170
Message text:
After effects error: Didn’t delete empty file " " because it was larger than
expected.
Message interpretation:
A temporary file could not be deleted.
Possible causes:
This error was noted in the render log of a user and is related to multiprocessing (Render Multiple Frames Simultanously) and possibly the use of specific formats handled through MediaCore. In both cases After Effects uses temporary files. They are either duplicates of source footage files to allow multiple render instances to access the same data without causing trouble with the operating system’s file handling routines or they are uncompressed conform files associated with compressed audio footage sources, e.g. embedded audio in AVCHD and otehr MPEG derivative files. When the program does no longer need them, it will attempt to delete unnecessary duplicates but may not always succeed. Because of the nature of the method of using multiple program instances, this error may also apply to network rendering.
Resolution or workaround:
File I/O errors can best be resolved by keeping your drives healthy and clean. Tips on how to do that can be found on this page. Any leftover temporary files can be deleted manually without risk once the render has been completed successfully. For the location of the individual directories, refer to this page.
July 26th, 2010
Message text:
After Effects error: Not enough storage is available to complete this operation.
Message interpretation:
There is not enough drive space available to store a file.
Possible causes:
This is one of the classical cases of "The program gets it wrong!" and it was observed while attempting to save a layered PSD file to our company’s server. The file was a 4K document intended to be further modified for later printing, but could not be saved directly, even if there was enough free space. Only saving it locally resolved the issue.
Resolution or workaround:
Save the file to a local drive and then copy it to the server.
July 26th, 2010
Message text:
After Effects error: CT bad param:invalid translator.
Message interpretation:
The code page range for a given character could not be converted to be compatible with the present system settings.
Possible causes:
See this error
Resolution or workaround:
See this error
July 26th, 2010
Message text:
After Effects error: Not enough memory to initialize PSL.
Message interpretation:
After Effects is unable to initialize a specific core component.
Possible causes:
There is no clear cause for this error, but since it was noted for CS5 on a Mac, it may relate to compatibility issues between 32bit and 64bit components.
Resolution or workaround:
Reinstall the program along with specific critical operating system components such as Quicktime from the original discs.
July 26th, 2010
Message text:
After Effects error: Writing to file “$filename” (1450)
Message interpretation:
The host program failed in writing a file to disk.
Possible causes:
This error regularly occurs with image sequences. The most common source of trouble seem to be delays caused by large files in compressed formats or formats that require color space conversion (Cineon, DPX, YUV-encoded TIFF). Of course simply slow disks, problems with RAID drivers and others might also be the cause for trouble.
Resolution or workaround:
In the particular case the problem could be solved by disabling asynchronous read/ write in the After Effects prefs. This can be done manually following the steps laid out below:
- go to your application preferences directory as explained on this page
- open the Adobe After Effects x.0 Prefs.txt file in a text editor (Notepad)
- look for a paragraph called ["Misc Section"]
- find the line that says “Asynchronous file reading and writing” = 01 and change the value to 00
The next time you launch After Effects, the change will be in effect. The downside to this approach is that the program will now wait until all files necessary for rendering a given frame before writing the last rendered frame. If you are using many footage sources, this might considerably prolong the rendering process. Another solution to consider is simply choosing a different target drive.
July 26th, 2010
Message text:
After Effects error: Error creating file “Workspace.xml” (5).
Message interpretation:
Upon launching the program, the file mentioned could not be found. An attempt to create it based on After Effects‘ default settings has also failed.
Possible causes:
The directory where the file is supposed to be placed is either not in place, cannot be found or it is locked somehow. This can happen if you install with insufficient user privileges or do not have the correct attributes and permissions set on your directories.
Resolution or workaround:
Manually check your permissions. Re-install the program with administrative rights and make sure to grant yourself the correct user privileges to write to system directories. For information on the proper default directory locations, refer to this page.
July 26th, 2010
Message text:
After Effects error: Finding preferences folder – no such directory.
Message interpretation:
The preferences folder could not be found.
Possible causes:
In most cases this will be caused by an permission issue, where the user cannot access his configuration directory. On rare occasions, the folder will not be found because it has accidentally been deleted or renamed.
Resolution or workaround:
Make sure that your user has full access to his user directory and it actually exists. The locations of the folders are explained on this page. Once there, right-click the folder and call up the Information panel (Mac OS X) or the Properties dialog (Windows) and check the security permissions and user privileges.
July 17th, 2010
Message text:
After Effects warning: Failed to create mediacore preference paths.
Message interpretation:
The configuration for advanced media file handling using MediaCore could not be written.
Possible causes:
The user permissions on the directories in question are not set correctly or the directories cannot be found because you installed in a different path.
Resolution or workaround:
Make sure to grant the right user privileges for all directories. Information on the location of these directories can be found on this page. A more comprehensive description of recommended procedures before and during installations can be found here and here.
|
|