PP 2017 BUG (Mac OS) - Saved Projects will not open under user account other than the one it was created by

[Cinemasters]

We installed PP 2017 last week and worked a few projects through it with no problem. Unfortunately, all of those projects are un-openable under any other user account with the error:

"The project could not be loaded, it may be damaged or contain outdated elements"

Even after a complete clean install of the machine (2010 Mac Pro 8-core, 32GB GTX980TI, ATTO R680 RAID) with OS X 10.12.1, the latest NVIDIA Drivers etc. we have the same result. When we used time machine to bring the original user back, the files are openable under that user only. Any attempt to open the project under other new users created after the clean install result in the same error.

Additionally, we created a brand new project with nothing in it under a certain user. This file was able to be opened by other users accounts. Once a single piece of media was imported (simple HD h.264 file) and the project saved, that project file became un-openable by all other users. Further testing revealed that projects created under the new 'clean installed' users exhibited the same activity.

Any project (except a empty one) created under any user becomes completely un-openable by any other user and displays the error above. This renders PP 2017 completely useless in our multi-editor machines and forces us to open the few projects we did save only under one user account. Attempts to set the file privileges to 'read & write' for everyone in the finder did not help. We will test this on another machine when we get a chance to install PP 2017 as well as trying to move projects between machines.

[Cinemasters]

Confirmed. This bug seems to be software related as it occurs on all our machines. Any project created with one user account reports:

"The project could not be loaded, it may be damaged or contain outdated elements" when trying to open it with another user account under OS X 10.12.1. We were able to recreate this on a Macbook Pro 2014 as well as a Mac Pro 2010.

[aRTLeSS_baSTaRDo]

Having exactly the same problem here! Any help Adobe?

[aRTLeSS_baSTaRDo]

We have two editors sharing one computer (Mac Pro running macOS Sierra v10.12) each with their own mac user account, each also editing under their own Adobe username on the same team account.

I found that I can open the project with another username from the same creative cloud team account, however, we need to be logged into the same mac user account that the original project was created. If we try opening the project from another computer or even another mac username on the same computer, we get the error message

"The project could not be loaded, it may be damaged or contain outdated elements"

[randym80358675]

@ aRTLeSS_baSTaRDo - That seems to be the case on our end as well.  We even just tried creating a new Team Project and importing the sequence.  It imports fine on the original machine (although it immediately offline everything in the timeline) and we are able to invite collaborators and share the project, but trying to open it on the other end as a collaborator totally fails.  It gets to the point where it is importing the assets and hangs.

We are currently exporting EDLs of the timeline and are going to see if we can do it the "old fashioned" way.  As a last resort, we are considering porting the user to our Mac Pro via migration manager so we can do our color pass and finishing work to meet our deadline.

Thanks for posting your experience in here.  Hopefully they find a fix for this soon, this is a BIG HICCUP!

[randym80358675]

We are having the same issue on our machines here at work where a PP2017 project that was created on a MacBook Pro off-site won't open on our Mac Pros or on our other MacBook Pro here in the office.  We have tried just about everything, minus a clean install.  We tried Digital Rebellion Project Rescue, creating a new project and importing, compiling and exporting the sequence, signing out of CC and back in under the original creator's CC account, renaming the files, copying to the desktop, painting a cat red and feeding it cheetos...no love.

We were able to create a new empty project on the original MacBook Pro and open that on our Mac Pros no problem, but it didn't have any media attached to it.

We are going to try to create a Team Project, import the project into that and then invite me to collaborate.  We'll report back here if we figure something out. 

PLEASE LET US KNOW IF YOU GUYS FIND ANY MAGIC SOLUTIONS HERE!

Thanks,

Randy

[petergaraway]

[Edited] Skip to post #10 for possible solutions.

Hi All,

We're aware of this issue and are working on a fix ASAP.

Please try the following method and let us know if you're still blocked.

Issue: After upgrading to the latest release, you are unable to open projects on macOS 10.12(Sierra)

Workaround: Install the previous version of Premiere Pro and save the project using the older version using the Find Previous Versions button in the CC App. If you can't see this option, you can also choose to click the Settings tab in the upper right corner and click Search for updates. The App now restarts and displays the Find Previous Versions button.

Known issues in Premiere Pro CC 2017 (November 2016)

Peter Garaway

[randym80358675]

Thanks Peter, we will give this a shot.  However, none of our machines are currently on MacOS 10.12(Sierra), they are all running El Capitan 10.11.6.  FYI

[Kevin-Monahan]

Hi RandyM, are you in a SAN environment?

Thanks,
Kevin

[randym80358675]

Hey Kevin, we aren't in a SAN environment.  I have multiple RAIDS attached directly to my Mac Pro via thunderbolt and I'm not networked to them via a server, nor is anyone else.

[randym80358675]

Hey Peter, if our project is a PP2017 project, how would we be able to save it as a PP2015 project?  Is that even possible?  As expected, the PP2017 project file doesn't open in PP2015.

[petergaraway]

Hi Randy,

Sorry for the confusion. That help doc is not accurate and I'll make sure it gets updated.

Here's 3 things that you can try that have helped others. Again, we're still working on the fix and hope to get it out to you guys soon.

Solutions:

#1

1. Open the project as the original owner

2. Offline all files

3. Save the project with the files offlined

4. The project will now open for other users.

Note: You can't hide the files. That doesn't work. You have the offline the project and save it that way.

#2

1. Use terminal to change the ownership

2. chown -R username /path/to/project changes the ownership

3. Possible solution:

Note: This last one hasn't been fully tested so your mileage may vary.

1. Create a new ROOT user 

2. Log in as ROOT 

3. Open the project and save the project

4. All other users should be able to open the project now

Please let me know if any these solutions worked for you.

Thanks! And sorry for the troubles.

Peter Garaway

[randym80358675]

@petergaraway - I tried each of the suggested solutions and unfortunately none of them have worked.  Please let us know ASAP if you have any other suggestions.  We appreciate any help here, we are under deadline for this project.

[petergaraway]

Hi Randy. Hmmm I'm not sure why now of those solutions would work. Let me reach out to the folks who are directly working on this and see what I can find out. I'll report back as soon as I get any additional information.

Peter Garaway

[witkobay]

For the love of GOD, what an incredibly huge bug to release an update with.  We've lost a good part of the day of editing to both of our editors with this today. 

Luckily the "make everything offline and save" seems to be working for now, but please please please get this one fixed asap and get that update out to the masses.

ALL HANDS ON DECK!!!!!!!

[randym80358675]

witkobay​ - we couldn't get the "make everything offline and save" to work.  would you mind walking through the exact steps you did to get that working?  we have tried just about everything at this point and this is killing our deadline.

thanks for speaking up and letting adobe know this is a problem!  it's a BIG DEAL for us as well.

[witkobay]

@randym80358675 I just followed what petergaraway​ posted earlier in the thread...

- opened project with user that created project

- select all folders in the project bin, cmd+click > make offline

- save project

- logout user, log in new user

- open project

- select all folders in project bin, cmd+click > link media

Should be good to go.

[randym80358675]

witkobay​ - just tried and although the progress bar did something different when attempting to open the OFFLINE file, we still got the dreaded message "The project could not be loaded, it may be damaged or contain outdated elements"

Thanks for taking the time to help us out.

[witkobay]

Ah man.... sorry to hear that.  Hate that when it works for some but not others. I'd be lying if I said I don't miss tape-to-tape with crap like this.

[randym80358675]

witkobay​ - thanks to your comment!  I was able to create a new project, import the desired sequence, offline all media, save the project, bring it over to our other computer and open it.  I'm currently relinking all the media now.  THANKS!

Doesn't negate the fact that this is a serious problem and needs to be fixed, but after 2 1/2 days of wrestling with this, I'll take what I can get!  Tape was fun while it lasted, but I'm awfully happy that it's nearly gone from my workflow altogether. 

[Seth Goldin]

For what it's worth, making all the files offline before trying to open on the other machine worked for me. This is a very goofy workaround, though. Please fix this soon, Adobe.

[atmospherical]

Peter/Adobe,

I support a couple editors that were also bit by this on 10.11.6. There were a bunch of other things in Creative Cloud that went wonky after running the latest Security Update from Apple. We had to uninstall some controller software, mod some permissions on folders in Library, etc... Perhaps there is a security change that was implemented in both Sierra and the Security Update for El Capitan that is causing this.

[witkobay]

It's fixed!!!!  Installed the 11.0.1 update this morning and all is good now.  All projects open with all users.

[david_parke]

Huzzah! I was going to do the update to see last night but was swamped. Glad to know it's working again!

[randym80358675]

Thanks for the update!  I did update Premiere yesterday and tried it, but it still wouldn't open.  We think there may be another issue (clips that are linked to the Downloads folder on the original user's computer), however, and I won't be able to get back to the project until Tuesday next week due to travel.  I'm happy to hear this fix is working for you guys!  Will definitely update on here when I get back in the office!  Thanks to everyone for being active in this and chiming in, we wouldn't have found the workaround without your help.  I feel like Adobe responded quickly to this, so kudos to them, even though I feel that it should have never been an issue in the first place.