Skip to main content
Participant
August 21, 2017
Answered

Project manager "unknown error"

  • August 21, 2017
  • 32 replies
  • 64858 views

   Hi,

After 2 years of using project manager to consolidate and back up my projects, it is now giving me constant grief.

On almost every project (mainly promos) it is unable to calculate project size og unable to back up my projects.

Every time giving me "unknown error", asking me to try again.  Not even once, has this improved anything.  I keep getting "unknown error"

It does not work and I've tried many combination of settings.

I will have to stop using Premiere as my editor if this keeps up.  I cannot keep backing up by copying 100s of GB of assets for a each 30 sec. spot.

What is going on?

Has a bug been introduced in the last few versions?

Does anybody else have these issues?

What could be the possible cause? 

Thank you

//Stig A.

Correct answer Guy Burns

Hi Kevin,

It was probably 3 hours of HD (1080p) footage, about half from from a Canon 5D and half from a Panasonic HC-V770, one main 7-minute sequence, two nested sequences, if that's what you're asking. It was definitely not a new project, and I'm not sure what you mean by updated. It was a CC 2017 project, and I had opened a copy in 2018 to archive it — and I forgot to mention that after the backup kept failing, I went back to the original and opened it in CC 2017 — and it was then that I also unchecked the "Save preview files" box. And then it worked. (So, the bottom line is, I have not yet gotten this to work in CC 2018.)

Is this a known bug?


Had the same problem and came across this thread. My project has about a dozen sequences, and the Project Manager wouldn't "Collect files and copy to new location". It came back with an "Unknown Error" message.

I narrowed it down to Sequence #4. That sequence was causing the problems.

I narrowed it down further: one of my music files from iTunes had special characters in the name: colons and commas. Got rid of those and the problem was fixed.

I'm running CS6.

32 replies

Participant
September 20, 2019

What I finally did was create a new project, copy just the seq I want and then project manage. That worked for me. 🙂

Participant
September 28, 2019
To everybody complaining about this issue... The tip from wiliness works perfectly. Just create a new project, then in import media, import the sequence of your final project (the one you worked on). A window will appear, select import sequence + create a folder, then use Project manager, and it should work perfectly.
Participant
October 2, 2019
It works indeed 🙂 Thank you
GLPVIDEO
Participating Frequently
August 2, 2019

Yep same problem here, should at least be able to tell you where the problem lies.

Time to go back to Final Cut.....

Inspiring
August 2, 2019

I find it difficult to believe that Adobe hasn't spent the time to rectified this problem – or the unsharp-text problem, or the lost-render problem. I remember going through several weeks of research back in 2013, deciding between Premiere and Final Cut. Asking questions on both forums, reading the manuals, going through forum posts, very carefully weighing the pros and cons of each. I finally decided on Premiere because of its easy interactions with other programs in the Adobe suite (PS, Encore, AE and Audition in my case).

I fixed the unknown-error problem by removing special characters, and the problem has never returned, but the other two problems remain. Given what I now know about Premiere, and given that FC is a one-off cost of $299, I'm almost certain I made the wrong decision to go with Premiere. But at least I'm not on subscription. I bought CS6 outright. And I won't be upgrading.

Participating Frequently
August 15, 2019

Once Adobe puts out a new version of Premiere Elements or Photoshop Elements, they just don't want to go back and fix the bugs!!  I, too, cannot get the Project Archiver to work in Premiere because of the "unknown error" message. And others have reported problems with the Shake Reduction feature which apparently isn't going to be fixed by Adobe either. And when I was using an earlier version of Photoshop, the "recently used files" list never updated or cleared out, and was another bug that Adobe just refused to do anything about. If Adobe was smart, they might realize that it's going to be difficult to sell new products in the future if they can't even take time to fix the bugs in the products that they've already put out!

Participant
June 8, 2019

Just to say I've had this on a substantial project today and it's beyond maddening. It takes well over an hour for Premiere to come up with the unknown error right at the end of the copy process. It's impossible to move work around effectively without this and make me think very seriously about looking at other editing options....

... come on Adobe. Thought you were better than this... 4 years and no solution??

Participating Frequently
April 17, 2019

Yup - I've come against this so often, I don't even try to use the project manager anymore.

This is 2019, mind you.  At least 4 years after this problem started being reported to Adobe.

If they haven't fixed it in 4 years, I don't like the chances that they ever will, to be honest. 

And yes, that's ridiculous.

I don't even want to transcode most of the time - just looking for all the media files to be copied to another directory.  If it is special characters that are the hiccup - it shouldn't take 4 years to fix that shortcoming in the code.  And it certainly shouldn't take 4 years to return a more useful error than 'UNKNOWN ERROR'.  If they had the courtesy to tell you which file the problem occurred with, which should not be rocket science, you'd save people dredging through thousands of media files on a feature, looking for the culprit.

Folks-  I'm self-taught with python, and it isn't even part of my job to code, and I've written scripts that can correctly handle special characters in copy operations.  Adobe should be ashamed of themselves.

JONSTNR
Participant
May 20, 2019

This is marked as answered but clearly isn't, an ongoing issue of 4 years - Adobe are you planning on even addressing this??

Marcial Reiley
Inspiring
November 19, 2018

Transcoding files fixed my problem.

Participant
November 2, 2018

I had the same problem. After removing all special characters ( _ * `; ) it worked fine.

Participant
October 20, 2018

I did the uncheck save previews thingy and it worked for me.

Participant
February 8, 2021

This worked well for me too! Thanks (Premier Pro 2020)

Participant
October 19, 2018

I have the same problem and still no solution. It already occurred from version cs 5.5 now with CC 2018 again in the same embarrassing problem. For those who work with other colleagues is a very serious problem.

ColbyFulton
Known Participant
October 15, 2018

I'm having the same issue. Makes it hard to do professional work on schedule when I can't easily output my project for color correction. Now I have to manage the files manually? It would be great if you guys could do a little more testing on this before you release the software.

laurlau
Inspiring
August 1, 2018

same issue here. no fix. no workaround. so? what shall we do next?

laurlau
Inspiring
August 1, 2018

1. delete all your proxies

2. check if you have special characters in your video/photo/work files naming like + # $ or whatever ( I found to have a Spanish character in one mov file)

3. delete adobe premiere cache

4. it should work.