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.

Die Voreinstellungen konnten nicht gespeichert werden, da… (…)

Englische Version nicht verfügbarFranzö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:

Die Voreinstellungen konnten nicht gespeichert werden, da die Datei gesperrt ist, Sie nicht über die notwendigen Zugriffsrechte verfügen bzw. ein anderes Programm auf die Datei zugreift. Heben Sie den Schutz der Datei mit Hilfe des Befehls “Information” im Finder auf, damit Sie die entsprechenden Zugriffsrechte erhalten. Sollte das Problem weiterhin bestehen, speichern Sie das Dokument als andere Datei ab bzw. duplizieren Sie es im Finder.

Interpretation:

Beim Beenden des Programms konnten die Voreinstellungen nicht gespeichert werden, weil kein Dateizugriff möglich war.

Mögliche Ursachen:

Fehler beim Dateizugriff können alle möglichen Ursachen haben, von unzureichenden Benutzerrrechten bis zu Hardwareproblemen. Meist ist es nicht möglich, einen genauen Grund herauszufinden, da diese Probleme oft nur temporär auftreten und sich scheinbar selbst reparieren. Manchmal reicht es schon, dass die Festplatte an ihre Leistungsgrenze kommt, wenn das System extrem ausgelastet ist und somit die Verzögerung beim physischen Zugriff zu so einer Fehlermeldung führt. Es kann natürlich auch bedeuten, dass andere Programme wie Virenscanner und Systemprozesse sich einmischen. Diese verändern unter Umständen auch die Benutzerrechte.

Problemlösung oder Workaround:

Als allererster Schritt sollte nach solchen Fehlermeldungen immer das System komplett neu gestartet werden. Das sorgt dafür, dass beim Hochfahren die eigenen Routinen des Betriebssystems die Festplatte überprüfen, kleinere Integritätsfehler beheben und beschädigte Bereiche umorganisieren. Sollte das nicht reichen, kann eine manuelle Überprüfung mit dem Festplatten Dienstprogramm weitere Hinweise liefern und Reparaturen ermöglichen.

Werden bestimmte Hilfsprogramme beim Systemstart geladen, sollten diese zu Testzecken deaktiviert/ unterdrückt werden, bis das Problem behoben ist. Dazu kann man im Apfelmenü die Startobjekte entsprechend entfernen oder im Aktivitätsmonitor den Prozess manuell beenden. Sollten wirklich die Benutzerrechte das Problem sein, müssen diese angepaßt werden. Dazu wird die Datei im entsprechenden Voreinstellungsordner (Preferences, Artikel in English) aufgerufen und mit Rechtsklick oder Datei –> Informationen im entsprechenden unteren Teil des auftauchenden Dialogs geändert. Es kann auch sinnvoll sein, die Datei einfach zu löschen. Dann wird eine neue mit Werkseinstellungen erstellt, die schon die korrekten Benutzerinformationen hat.

Photoshop hat nicht länger auf die Überprüfung des Grafiktreibers gewartet. (…)

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:

Photoshop hat nicht länger auf die Überprüfung des Grafiktreibers gewartet. Verbesserungen, die die Grafikhardware nutzen, wurden deaktiviert. Besuchen sie die Webseite des Herstellers, um nach aktueller Software zu suchen. Für weitere Informationen besuchen Sie: http://www.adobe.com/go/photoshop_gpu_cc_de.

Interpretation:

Die Hardwarebeschleunigung wurde aufgrund von Problemen mit dem Grafiktreiber deaktiviert.

Mögliche Ursachen:

Bei diesem Problem handelt es sich im Prinzip um die gleichen Ursachen, wie sie in diesem Beitrag (Englisch) erläutert werden. Der einzige Unterschied ist, dass anstatt nur Fehler zu produzieren, das Programm das Problem erkennt und die Funktionen zur eigenen Sicherheit ausschaltet.

Problemlösung oder Workaround:

Beachten sie die entsprechenden Empfehlungen im verlinkten Artikel.

Photoshop has encountered a problem with the display driver, and has temporarily disabled enhancements which use the graphics hardware. (…)

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:

Photoshop has encountered a problem with the display driver, and has temporarily disabled enhancements which use the graphics hardware. Check the manufacturer’s website for the latest software. For more information, visit: http://www.adobe.com/go/photoshop_gpu_cc_en.

Message interpretation:

Hardware acceleration was disabled due to compatibility issues with your graphics driver.

Possible causes:

This pretty much boils down to the same issues explained in this article in more detail. The only real difference really is that this time the program detects the issue and disables all related features for your own safety.

Resolution or workaround:

Refer to the guidelines provided in the article mentioned.

Could not apply the workspace because the file is locked, you do not have necessary access permissions, or another program is using the file.

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:

Could not apply the workspace because the file is locked, you do not have necessary access permissions, or another program is using the file.

alternate message text (older versions, Mac):

Could not apply the workspace because the file is locked or you do not have the necessary access privileges. Use the ‘Get Info’ command in the Finder to unlock the file or change permissions on the file or enclosing folders.

Message interpretation:

A workspace or one of its related files could not be loaded.

Possible causes:

Similar to other file access errors, first and foremost this problem could be caused by permissions and user privileges issues as well as security tools and settings blocking access to critical files. Likewise, any damage to these files may prevent them from being loaded properly. In addition to the workspace files themselves this can include secondary files such as action sets, brush presets, swatches and so on. When the layout is switched and a palette that wasn’t open before calls up one such file, the error may come up as well even if the actual workspace file exposes no problems. This may be even more so the case with additional panels such as various color picker tools that may also attempt to access files outside the actual Photoshop program file hierarchy.

Resolution or workaround:

First of all do the usual drill of checking your file and folder permissions, user privileges and security tools. Explanations on how to do that can be found here along with generic tips on how to keep your drives in good shape. Especially check your user home directories where your configuration files are stored. If you use additional panels, follow the instructions of the providers precisely and get the version that is compatible with your version of Photoshop. Incompatible versions may corrupt your workspaces. In addition you may need to check your security tools again. Many panels use port connections to invoke plug-ins, access files in remote folders and run the underlying Flash, Adobe AIR and ExtendScript functions and this stuff may be blocked. If you downloaded brushes, patterns and other content that was created in another version you may need to convert it by loading it in the respective panel manually and then saving/ exporting it again conformed to the version you use.

Could not complete your request because of a problem with the file-format module interface.

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:

Could not complete your request because of a problem with the file-format module interface.

Message interpretation:

A file could not be opened because it was not found or of an unknown format.

Possible causes:

The most common cause are broken or screwy system level file associations and protocol handlers that tell your computer which programs to use to actually open a file when you use a double-click, drag & drop or other system methods to invoke a file operation. Since this is not controlled by anyone, it can happen that multiple programs register the same file extension like for instance *.psd. That can mean that the file opens in a different image viewer or editing program and not in Photoshop if it is actually a PhotoShop Document. On the other hand it may not open at all if someone simply used the same extension for his file format, but it actually means Popular Survey Data or similar. Naturally then it will not contain any image data and Photoshop can’t work with it. This applies even more so to auxiliary file types like the ones used to save brushes, actions and swatches that may never correctly import by just double-clicking on them.

Related to the previous, files may not be possible to open when those handlers are blocked by security tools or the hand-off chain from the double-click registered by your operating system to the actual opening of the file is interrupted otherwise. This can include hardware problems like fragmented drives, bad connections to external storage devices and interruptions in network connections just as well. Sometimes they are genuine issues with cables or connections, sometimes performance issues because a disk is already being used a lot. Also time-outs from drives that have gone to sleep needing to spin up or network connections being too slow can cause Photoshop to simply give up on opening the file.

Another critical issue is of course missing or messed up file parser plug-ins. There is basically two standard scenarios here: The user has copied his beloved filter plug-ins from an older version of Photoshop to a newer one and inadvertently also copied incompatible or redundant file format plug-ins or in the other case uses an incompatible third-party plug-in e.g. for creating icons.

Finally, a very specialized case that is sort of a combination of all the above points are Smart Objects and Smart Filters that attempt to use dynamic data directly from the source of a placed file. Handling Raw files from your camera via Lightroom and/ or Adobe Camera Raw would be one such example, but this may also affect Illustrator files or other types. When going from one program to the other, communication could be blocked or due to differences in versions, which even could have been caused by a failed update of one of the programs, the file format is not understood.

Resolution or workaround:

To begin with, most issues can be rectified by just reinstalling the program. This will reinstate default file associations, place compatible versions of the plug-ins and give you a chance to straighten out potential hardware issues beforehand and optimize your set-up by e.g. choosing a different install location. To avoid remnants and invalid configuration data of the previous install to be left in place and get in the way, it is necessary to try and uninstall the program using the uninstallers and clean out any folders. You may also need to run the Creative Cloud/ Creative Suite Cleaner Tool as explained here.

If you are reasonably versed in computer stuff and know your way around, you can also try to manually fix file associations and all that stuff. This is explained on this page. Some guidance on straightening out potential hardware and performance problems is provided on this page. Of particular not should be fitting up your drives by defragmenting and reorganizing file structures as well as making sure that things like USB connections actually work reliably without dropping out or the external drive going into idle modes prematurely. When you use double-clicks or drag & drop, try to open the files using the relevant menu functions instead and see if it makes a difference.

When using specific plug-ins, obtain the correct version from the vendor/ supplier and do not use outdated ones. It may cost a few bucks to upgrade your plug-in suites, but it can save you a lot of trouble. Similarly, if you use plug-ins across multiple programs, make sure you have the same version. This explicitly also includes verifying the update status of Camera Raw and your Adobe programs in general. Even things like unwittingly installing the latest Adobe Reader and it introducing new file versions of the shared PDF libraries that then could prevent you from opening those files in your older version of Photoshop need to be considered. Going back to an older version to undo the damage may then be your only option.

Could not initialize Photoshop because the preferences file was invalid (it has been deleted).

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:

Could not initialize Photoshop because the preferences file was invalid (it has been deleted).

Message interpretation:

Photoshop could not access its preferences file.

Possible causes:

While it boldly states that the preferences file has been deleted, most of the time this is actually not the case and the file is merely inaccessible. This is then exacerbated by the fact that due to the problem also no new prefs can be created with factory defaults.

Resolution or workaround:

The only way to fix the issue is to adjust your file and folder permissions and make sure no security tools block file access as explained here. Once you have resolved those issues, you may need to reinstall the program, regardless.

Could not complete the Render Video command because the settings in the file are invalid.

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:

Could not complete the Render Video command because the settings in the file are invalid.

Message interpretation:

Media files (video, audio) could not be opened or imported because the required system service is not accessible.

Possible causes:

This issue seems to point to a conflict with how the rendering has changed in Photoshop CC 2014 and on. Since it relies exclusively on Adobe Media Encoder it would appear that the program more often than not does not compensate for mismatches between the video timeline settings and the stored settings in a render preset. It could also be that specific information in the source files like metadata or specific MPEG stream flags can cause the issue when the program attempts to retain that data and pass it through or makes wrong automatic assumptions about this and that. The specifics remain unclear as the people experiencing the problem never provided enough info to make sense of it.

Resolution or workaround:

Not applicable.