Skip to main content
Cat_Schwartz
Known Participant
November 8, 2016
Answered

Premiere cc2017 will not open projects from other mac users

  • November 8, 2016
  • 39 replies
  • 39880 views

This morning I found a serious bug with Premiere 2017.  I have two iMacs running Premiere with two different licenses.  Everything was working fine until we decided to have the editors swap projects and then we got an error message saying "The project could not be loaded, it may be damaged or contain outdated elements."  This happened on both machines with both projects.  Both projects open up fine with their original user.   We are at this point stopping any further use of P2017 until this bug is solved. 

    This topic has been closed for replies.
    Correct answer Trent Happel

    Hi Philipp,

    I'm sorry that the fix has taken so long to be released publicly, but our hands have been bound by the update release dates for all the other products. Hold tight. Your pain will be over soon.


    Sorry that it has taken some time and we were not allowed to comment on the fix date, but this issue should now be resolved in the 11.0.2 update that was just posted today.

    39 replies

    slowrider
    New Participant
    August 11, 2018

    I am having this same issue, I've tried the following with no success:

    1) Tried different PCs and Mac - Error occurred.

    2) Media offline - Error occurred.

    3) Last 5 Autosaves are corrupt, but the 6th one isn't.

    4) Tried importing sequences - No result, froze.

    I need this project out the door by tomorrow, and there is not time to redo the work and can't not call adobe support.

    Anyone have a solution? I will transfer you money.

    spidervideo
    Inspiring
    September 15, 2017

    BTW, I just had the same issue and what seemed to be the problem was using linked library files (PSD in fact). Once I cleared them from the original project (albeit losing those graphics) and resaving, it opened no problem on my other machines, aside from the usual re-linking.

    nickmichael
    Known Participant
    September 19, 2017

    So one of the selling points of the suite, using files between programs such as PSDs in Premiere, broke the project.  Hilarious.  It just keeps getting better.  Adobe: "Here's this awesome feature, don't actually use it though, it might make the program not work." 

    New Participant
    June 12, 2017

    I have the same issue now... 

    1 mac pro tower (original file created on this, ) 1 mac air and 1 macbook pro, all running PPro 11.1.1 (15 build). I cannot open the edit file on the mac air or macbook pro...

    Files are on a local HD with me.. Added them to drop box, used to go my pc to get into the original mac pro tower to try and open, and cannot open the original file there either now.. Nor, a duplicate of the edit... convention video due in the AM.. Wonderful update 11.1.1 (15 build). All worked fine before this last update...

    Community Manager
    June 13, 2017

    I would suggest contacting support to help with this issue. FAQ: How do I contact Adobe Support?

    SilviaLozzaVideos
    Participating Frequently
    April 27, 2017

    Hello!

    We've had a similar problem. 

    We are a small team that works often on the same project file. We have different hard drives where we mirror the files, but when we try to open the project from a hard drive\machine that is different than the original one, we can't. We get the dreaded error.

    We then tried to delete the library we were sharing from the Creative Cloud, and that seems to have solved the problem.

    The project I couldn't open before now opens without problems, and all I have to do is relink the file and, of course, source those library assets from somewhere else.

    A bit of food for thoughts for you guys, let me know if you experienced the same and if this solution works for you!

    New Participant
    January 20, 2017

    Finally in Argentina is Fixed the problem. Updated 11.0.2 (47) Build

    Participating Frequently
    January 20, 2017

    Unfortunately this didn't fix the issue for me.  I still can't open any file from my macbook pro 2016 on my macpro, even though all plugins and apps are the same versions.

    nathanb73638423
    Participating Frequently
    January 18, 2017

    We've been having the same issues here at Fabler Studios since upgrading to CC17.  We'll be super happy once this is fixed.... it's a time consuming (i.e. costly) work around.

    nickmichael
    Known Participant
    January 16, 2017

    If Adobe is going to take over two months (and counting) to fix this, the least they could do is educate their support staff on what is an official entry on the known issue list.  Just got off a chat with a rep who didn't seem to believe me when I told him I'd run into several project with this issue and that it was solved by me sending the file into support, having them open it (all media automatically going offline) then re-saving and sending back to me.  Took two minutes each time.  This last chat took over 15 minutes because he wanted to do a screen share "so that I can view what you are seeing, via remote access,  and then I can provide the appropriate advice/assistance?" before he agreed to open my project file, and I ultimately never received a new project back from him. 

    Final Cut Pro X - Apple

    Media Composer | Avid

    Sony Creative Software - Vegas video - ACID & Sound Forge audio editing

    HitFilm Pro 2017 - Video effects software for Mac & PC - HitFilm.com

    MAGIX Movie Edit Pro – Video editing software

    Just a reminder to Adobe that there is indeed still competition in the video editing world.

    New Participant
    January 13, 2017

    Having the same problems here too. I'm just adding my 2 cents to help motivate those people to send out the update. Work at a university with a lot of students and sharing lots of project files. Sticking with cc15 until this gets fixed.

    New Participant
    January 13, 2017

    Not here to pile on, but we're having the same issue.

    I manage the Mac Pro's in our Creative Services dept.  

    All connect to a shared network raid via fiber. 

    The workaround for us has been opening the project on another machine, hit save, close.

    And, for some reason it will now open on the machine that was having trouble.

    Dan

    Participating Frequently
    January 13, 2017

    Mitch,

    I am also having this issue and find the fix time unacceptable.

    All the best,
    Dara

    New Participant
    January 13, 2017

    Frankly I am flabbergasted that we are almost halfway through January and this is still an outstanding issue. I know Adobe says the fix is coming "soon" in the next point update, but a showstopper like this ought to be given a hot fix rather than sit on the shelf until Adobe rolls out the next major point revision.

    Perhaps the timing around holidays slowed things down somewhat, but now it's the new year and still nothing. If Adobe wants to position Premiere as a truly professional NLE, bugs like this simply cannot be allowed to persist for so long. I'm a fan and a defender of Adobe but this is really not acceptable.