• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

AE crashes project which was working fine with message BEE_ThreadedRenderUpdateQueue::Render_DeserializeFullProject ZANZIBAR-2:

Explorer ,
Mar 12, 2019 Mar 12, 2019

Copy link to clipboard

Copied

Hello there,

I have two projects which crashes when playing them or when just loading them. These projects used to play correctly last year (May 2018). Meanwhile, AE have upgraded. However, when loading the project, I have a message saying that the project is being converted.

The crash error says the follow :

Last log message was: <123145502593024> <DBSync> <5> BEE_ThreadedRenderUpdateQueue::Render_DeserializeFullProject ZANZIBAR-2: old=00000000-0000-0000-0000-000000000000, new=7ba573c4-775a-40c9-b7ee-bc14e58dcf8d, new-ts=108702

I don't know what to do to resolve this issue.

The problem sometimes occurs when after loading the message it converts and while saving it into the new version it crashes or it opens and when i hit "play" to read, it crashes.

Any help?

Kind regards

Jean Jacques Fabien

Views

2.7K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Apr 01, 2019 Apr 01, 2019

Copy link to clipboard

Copied

Hi Jean Jacques Fabien,

Sorry to hear about this.

I wonder if you had any custom workspaces in those projects.

Let us know.

Rameez

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 01, 2019 Apr 01, 2019

Copy link to clipboard

Copied

Dear Rameezkhan,

Thanks for your reply. Since the matter was pretty urgent because I was working on a project to be delivered with a deadline, I contacted adobe via chat and a technician intervened via a teamviewer type software where he could access my computer and I saw him work. Basically he deleted all the "temp" files and reference in the library to all adobe products and changed the read / write authorisation for a number of directory.

After doing so, everything was working perfectly.

Thank you but problem resolved.

Kind regards

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 16, 2020 Sep 16, 2020

Copy link to clipboard

Copied

How did you manage to get them remotely connect to you. I'm in the chat for the last 2 hours, the guy said he had an issue with the remote connection and cant help me and cant transfer me to someone else. Made me render the corrupted file from Media Encoder and tried to import the mp4 file in a new AE project, restart my computer for several times, revert back to AE 17.0, deleted my keychains ?, renaming after effects folder to after effects.old. and none of them work.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 26, 2019 Apr 26, 2019

Copy link to clipboard

Copied

In AE v16.1.1

I turned on 'disable layer cache' in the secret preference menu which caused this error in a project that was working fine before I turned it on.

After a few crashes I opened AE V16.1.1, turned off 'disable layer cache' and the project works fine again.

I am able to repeat the error by checking the 'disable layer cache' on and off.

In AE v15.1.2 The same project works perfectly with 'disable layer cache' checked on or off.

The only thing I can think of that might be causing the issue in AE v16.1.1 for me is a text layer legacy expression conflicting with the layer cache being turned off. Not having the skills to re-write the expression for the new js expression engine, I have no idea if the fact that it's an old expression that's causing the issue.

Hopefully this helps point the engineers in the right direction to find the issue!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 19, 2024 Dec 19, 2024

Copy link to clipboard

Copied

LATEST

Cleaning up the chache it's what worked for me. Maybe that's enought in some cases

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines