"The project contained a sequence that could not be opened..."

[NoMagnolia]

"...no sequence preview preset file or codec could be associated with this sequence type."

I updated recently to Premiere CC 2015.3. This morning, opening a project which I'd been working on all yesterday in Premiere, I got the above error. I can't open this project in earlier versions of AP, natch.

I created a new blank project (no. 2), tried to import the entire problem project into it, and got the same error. I then tried to import only the latest sequence into this new project; which worked fine.

However, when I save project no. 2 (with its one sequence), and try to reload it, I get the same error as above. The only solution is to create another blank project (no. 3), import the (single) sequence from project no.2 into it, and then I can work with this. Which is odd, because importing the whole of project 2 doesn't work; only the single sequence it contains - which comes to basically the same thing.

I also can't export via AME (to H.264; I haven't so far tried any other codecs). I have to export directly from Premiere.

I have uninstalled and reinstalled Premiere, with exactly the same results. I also get exactly the same problem on two other machines here.

Machine specifications:

#1: Windows 10 laptop, Adobe CC2013.3, 32GB RAM, twin SSDs, nVidia Quadro 5010M

#2: Windows 10 desktop, Adobe CC2015.3, 32GB RAM, SSD boot / spinning swap drive, nVidia GeForce GTX 770

#3: Windows 10 desktop, Adobe CC2015.3, 64GB RAM, SSD boot / spinning swap drive, nVidia Quadro K5000

[NoMagnolia]

Update: Going back to Premiere CC 2015, and opening projects saved with it, *none* of them can be opened: I get the same error on each one.

Could this be something installed by CC2015.3 which is corrupting the import process for previous versions of Premiere as well as the latest one perhaps?

[Tim Boknecht]

None.  Not a single project will open.  I can't even save a project in the UPDATED version and get it to open.

So much fail.

[claireb29389193]

I just copied the entire project onto a MAC with the latest update and it opened with no problems...

Running Yosemite on iMac (2011) i7.

Just means I have to re-edit all again as it did not save the sequence.

[claireb29389193]

I have the same problem after updating and now can't open a project I have been working on all morning.

I am running Windows 7

8 core Zeon 3.50 Ghz

32 Gb Ram

AMD Radeon HD 7700 series.

[Shane_P]

Whenever I upgrade to a new version of Premiere, I never "open" a prior version of  a project file and get subjected to the "the project has to be converted...blah, blah" dialogue box.

I think it's a far safer practice to create a new empty project from within the new version (in this case 2015.3) then use the Media Browser to import a previous versions entire project file. Works like a charm overtime for me going back to the beginning of CC.

[Bedri Pasin]

i have the same problem, i can not open any project, i have a problem with the mxf files during import

[NoMagnolia]

I've removed CC2015.3 and CC2015 on one of our machines. Ran CC Cleaner (Use the Adobe Creative Cloud Cleaner Tool to solve installation problems) and restarted. Still the same problem.

On a fourth machine, which has never had CC2015.3 installed, this problem doesn't happen.

Solution: don't install 2015.3 until Adobe fix this.

I thought we'd left this kind of problem behind ages ago. I remember either CS3 or CS4 being the buggiest, most unstable piece of software I'd ever used; it got better after then, but things seem to have taken a retrograde step.

[Shane_P]

I've learned through the years that I will NEVER install a new release of Premiere on my main editing machine. I always download the new version on an alternate machine for testing.

To me, it's painfully obvious that when Adobe rolls out a new version of PP that we are beta testing for them. Hence why I will only install  on a secondary machine. Ever notice how in the Premiere forum it's usually just Kevin Monahan and maybe a couple other Adobe staff lurking/replying to threads....but on release day of a new version there are Adobe Staff virtually everywhere responding to virtually every thread?

It just makes logical sense to me that Adobe's testing is limited to their own environment and the real testing begins with us when it's released. Do I think they intentionally release "buggy software"? No of course not. But I think the only way for the bugs to get worked out if for us as users to find them.

I always wait until the "dot 1" versions of a major new release comes out with the bug patches before I will consider updating my main workstation. 

Until then I am editing as smooth as butter on my main workstation (Yosemite 10.10.5 Mac) while my 10.11.5 Mac is the guinea pig for 2015.3

[NoMagnolia]

Great advice, Shane - unfortunately we don't have spare machines we can use as guinea pigs, and spare editors to test new installations. Our editors need to be able to work uninterrupted on (paid-for) projects. The other solution, I suppose, is never to install new releases until they've been out for a year or so and everyone else has tripped over all the bugs.

It's mightily annoying, though, that Premiere projects are so locked in to the version of Premiere you created them with. On AE you can save in the previous version's file format, which would be a useful feature here.

[Tim Boknecht]

I've held the same opinion for years - but I would posit that putting the beta testing on us is essentially purposely releasing buggy software.  We lose so much time.  Time is money.  Yet, Adobe never suffers.  We do.

God help them if anyone ever comes out with a viable alternative to CC.  I'd pay more just to stick it up their ass.

[Tim Boknecht]

I was getting this problem BEFORE I even updated.  Adobe won't even RECOGNIZE any of my old Premiere files as Premiere files.

Why is EVERY SINGLE ADOBE UPDATE EVER A GIANT CLUSTERFUCK?!!!!!

[JLP2018]

Same here... 

[inêsa16413259]

Hello,

I am having the same problem, I tried everything! How did you fix it?

[amokphoto]

I have got the same problem......

[JLP2018]

Ok so I just opened it on a Mas as well, opens on a Mac not on my Windows PC. 

[Vinay Dwivedi · Accepted solution]

Hi,

We apologize for the inconvenience. There are some issues related to the Activation of Premiere Pro which is giving error " The project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type”.

The team is aware of this issue and it will be fixed ASAP.

Please sign out and sign in from your CC application to turn the application in the trial mode so that projects can be opened.

Features and sequence presets missing | Adobe Premiere Pro CS6, Premiere Pro CC

//Vinay

[NoMagnolia]

Thanks Vinay - however, Premiere is insisting on a sign-in if I sign out. It won't run in trial mode.

[Vinay Dwivedi]

Hi,

Try to clear the SLcache and Sl store folders in "Reset licensing information" sections and check if it helps.

Features and sequence presets missing | Adobe Premiere Pro CS6, Premiere Pro CC

//vinay

[jbarbphoto]

Where I find sections to "Reset licensing information" and clear SLcache and Sl store folders or whats te path on Windows ?

[Vinay Dwivedi]

Hi,

These are the location of the folders needed to be removed to reset licensing information.

• SLCache
  • Windows: /Program Files (x86)/Common Files/Adobe
  • Mac OS: Library/Application Support/Adobe
• SLStore
  • Windows: /ProgramData/Adobe
  • Mac OS: Library/Application Support/Adobe
• OOBE
  • Windows: /Users/AppData/Local/Adobe
  • Mac OS: /User/Library/Application Support/Adobe

//Vinay

[gehughes40]

I can confirm on Windows 7 Pro that Uninstalling (through the Windows control panel) and following Vinay's directions of deleting those folders worked for me...so far.

[fabianw22986079]

This solution worked for me!

[JMGibson]

Hi, Vinay. I'm having the same problem, also on Windows 7. I tried your suggestion, but I'm still getting the message that sign in is required. Have people had this problem when using Windows 10?

[Vinay Dwivedi]

Hi,

This issue is been reported on Windows only platform (7, 8.1 and 10) .

//Vinay