Error: missing data in file. (33::4) when trying to open file in After Effects
Copy link to clipboard
Copied
I am unbelievably frustrated with my luck today in After Effects.
I currently have After Effects CC 2020 and Adobe Media Encoder 2020. Last night, I had finished a project and was ready to send it over to AME, yet, when I tried to do so, I was greeted with the message "Error: missing data in file. (33::4)." After receiving this message, I immediately turned to the community for help.
The first thing I tried to do was reinstall an older version, however, my older versions of AE auto-uninstall, so I don't have any of them available anymore.
The next thing I tried to do was just drag the project file into AME. I was hopeful when the Dynamic Link began to load, however, it was unable to open the file. I then tried to repair the Dynamic Link's connection to AE by altering some Preference settings, but still no luck.
Lastly, I tried recovering any Auto-Saves of the project so I could try importing them into a new composition, but was unable to find any of them, even when using search.
I have spent all day watching tutorials, reading threads, and even remaking the entire project all over again, just to be greeted by the same message. I am so fed-up and frustrated. I want to reinstall 17.0, but I have no idea where to find that. If I should get an older version of AE, I need to know that. If there is no possible way for me to ever open those files, I need to know that, ASAP please. I cannot waste any more time on this crap.
Title edited by Mod.
Copy link to clipboard
Copied
Hi there,
Sorry for your issue. I see that you are not able to open your file created in After Effects. The issue that you are getting is a known issue with the release and the After Effects engineering team is working on a fix. You can install the previous version of After Effects (17.0.0) and try to open your file in it. Here's how to install previous version: https://helpx.adobe.com/in/download-install/using/install-previous-version.html
Let us know if it helps.
Thanks,
Nishu
Copy link to clipboard
Copied
I'm seeing the same thing in 17.0.2 and I have reverted back to 17.0.0 and 17.0.1 with no success.

