Skip to main content
E
eriswea
Participant
March 3, 2017
Question

"An unknown error occurred while opening the project" :o

  • March 3, 2017
  • 1 reply
  • 1690 views

Can someone save me!?

I've been working on this project for weeks.  After working earlier today, I shut down the program, and opened again a few hours later.  When I tried to reopen, I received the above message.  I closed the program, restarted the computer and am still getting the same message.

When I went to the auto-saved files, none of the versions from today would open either (had a ton of options as auto-save was set to every 3min, because it kept crashing when using image turbulence filter).  There were no auto-saved files from any other time in the last week (super strange, as I've been working daily, and watching it save every 3min--- where are all of those versions? no idea).  The next most recent auto-save file prior to today is from over a week ago, so would be losing a lot of work.

I tried importing the project into a new blank project to no avail.

I'm working on a brand new MacBook Pro 13" 2.4 GHz Intel i7, using Sierra 10.12.3

Premiere version 2017.0.2 v11.0, Tanq  (it appears that I am all updated)

Not running other software, and have no third-party effects.

Not sure, but I don't think I'm using Mercury Playback unless it comes loaded automatically.

Source footage is all from an iPhone.  Not sure of file-type or details... not a tech wiz, sorry. 

Please do help me if you can... I'm dying!

Thank you!

This topic has been closed for replies.

1 reply

Mohsen Aghaei
Mohsen Aghaei
Inspiring
March 5, 2017

Upload your project and share the link.

God loves you...

C
Cardamada
Participant
April 10, 2017

Did you figure this out.  It has just happened to me for no reason.  I have been working on this project for a year.  None of the versions saved today will open.  They were fine less than an hour ago.  This is a major bug.  I need to export videos for a deadline.  Has anyone figured out what is going on here?

Mohsen Aghaei
Mohsen Aghaei
Inspiring
April 11, 2017

We just know that the problem is within your project file, but the corruption of its XML core may vary from one or two lines bad characters to more than millions of garbage lines of data.

In my opinion the main reason for this killing bug is bad disk response while premiere trying to save the project. But unfortunately there is no efficient controller inside premiere to warn such a thing before closing the project. This is Adobe's fault.

However

If it helps I can take a look.

Upload your project file and send me the link. Usually I am able to recover the project.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices