"The importer reported a generic error"

[Nathanjrb]

Whilst this is a useful error message, it still hasn't helped me resolve the issue.

I currently have 5 sequences, all containing the same file type - but when I load the premiere pro file it asks me the location of two of the files, both in seperate sequences - all the other files are located just fine. I pointed the "Where's this file..." process in the right direction and on two of the files (the two missing ones)  I got the above error message. Why? How can I fix it?

The file types are .MTS.

I did start the project in CS5.5 and then when I got CS6 I opened it up in that, and it converted everything just fine. It's only when I've re-opened the project the next day I got this problem. Could this be the reason? But why only two of the files and not the rest?

Thanks in advance for your responses!

[goforo]

Just had the same problem and discovered that it was the result of removing neat video noise reduction plugin for premiere. Once I reinstalled, everything linked up without a problem.

[Iris_F__Lin]

Try to copy+paste your original clip to another folder and import it again. But make sure the clip itself is good, not damaged.

[Siddharth5FCE]

Bro you are a genuis 

[Darik Datta]

I just had this exact problem. I sequence I had been working on for weeks suddenly had media file go offline for no reason at all. It was an MTS file.

Premiere caused the bug. The problem was the .xmp file that premiere had created next to the MTS file had gotten corrupted by Premiere at some point when I was editing the sequence. I deleted the .xmp file and used the "Replace Footage" command and selected the original MTS file and everything was restored. Prior to deleting the XMP file, the "Replace Footage" command would give me the "generic error" (thank you so much Adobe for your useful error messages).

Apparently from time to time Premiere will randomly whomp .xmp files when you are editing sequences that contain the clips they go with.

[HDV.DIVA]

I have been having problems with this message in CC and CC2014 for projects that have already successfully imported the clip.  Along with this message Adobe CC kept asking me to license the software each time I open an app, even after I have successfully done so.  So I contacted support and this is what I was asked to do.  So far it has resolved my issue.

"The importer reported a generic error" And/OR CC 2014 keeps asking me to license the software even after I successfully license it.

Adobe Tech Support: Please disable the firewall and antivirus temporarily for few minutes so that we can isolate the issue better.

Adobe Tech Support: Please press windows are R key to open the run search box.

Adobe Tech Support: Then type there below command and hit enter.

Adobe Tech Support: inetcpl.cpl

Adobe Tech Support: Please click on connections tab.

Adobe Tech Support: Then select LAN settings.

Adobe Tech Support: Then tell me which boxes are marked check.

Adobe User: none

Adobe Tech Support: Please mark check on automatically detect settings.

Adobe Tech Support: Uncheck all the other boxes.

Adobe Tech Support: Then click on OK.

Adobe Tech Support: Then apply and OK.

Adobe Tech Support: Then try to open the CC product sign in if ask.

Adobe Tech Support: Then after license close it and re-open to check the issue.

[UNHAPPY_ADOBE_USER]

"The importer reported a generic error"

Is adobe speak for: we have no idea why our unvetted programming didn't work yet again, so we're going to put up the idiotic error message that means nothing.

To wit: Trying to import a .psd file into Premiere. The file imports into After Effects with no problem. It opens in Photoshop with no problem.  But into Premiere, where the file is the last thing I need to add to a project to be done? NOPE. Will not import. No amount of works arounds (opening in a new project, etc.) works. And thus, Adobes answer to everything:

"The importer reported a generic error"

[Kevin-Monahan]

Hi UAU,

You may have an incompatibility in the PSD file that is compatible with the other apps you tried. Did you have any unrasterized layers perhaps?

Thanks,

Kevin

[danield12266448]

your new version of premier crashed during an export of my project and now every time i try to open it this is the message i receive as well. I expect you have a way of fixing this correct? how can i fix this corrupt file that your program created?

[Department4]

I was receiving this error NO MATTER WHAT I'D DO to my sequences in Premiere (problem was occuring when manually trying to round-trip from Premiere CC to Pluraleyes 5.3.8 and back). It was pretty infuriating.

I finally caved and decided to install the Pluraleyes Extension for PPCC just to try something new (I'd had bad experiences with it before) but amazingly, it worked! So now i'm on my way, but would still love to figure out what happened....

[Pat_Bravo]

We are having the same error,

"The importer reported a generic error"

resolved by renaming the file. No other steps to resolve the issue.

Importing and Drag and Drop would give us the error, on APPro 8.0.1 on Mac OS 10.9.4.

[knappjs]

Posted this in another thread, but 'll just throw this out there, should anyone else stumble upon this.

I, too, am plagued with 'generic error' issues. Specifically, Premiere CC 2014 suddenly won't recognize ProRes files. I've tried everything that I can find: preference & cache deleting, app reinstalling, killing the DVCProOutputThingamajiggy codec, etc.

Some weird tricks that I've found success with (note this is on a Mac):

1. Move the files up one folder level, and relink. I've had weird success occasionally with this. Screws up my organization, however.

2. Change the file name and relink. On a whim, I just changed the name of my file from "MonitorCam-Pt3_ProRes.mov" to "MonitorCam-Pt3-ProRes.mov"...essentially replacing the underscore with a dash. BOOM, clicked in. Why? Only the programming wizards will know.

3. Open files in AE, and bringing them into Premiere that way.

[vidarfreyr]

"Some weird tricks that I've found success with (note this is on a Mac):

1. Move the files up one folder level"

Oddly, this worked for me. Silly little bug.

[_Supaplex_]

Thanks. The first option works for me. This problem has a ridiculous solution but thats Premiere.
Thanks again.

[Digipez]

It seems that placing the audio file in any folder that doesn't contain the project fixes the problem (can be a level higher or lower in the directory.

For example, my project sits in Folder/Project Folder/*project file*

Whereas my audio now sits in Folder/Project Folder/audio/*audio file*

[JakeGonzales]

Moving the file up in the directory worked a treat! It's not ideal but it's a life saver.

[Skydog70]

If this is helpful to anyone, I had the error on a Photoshop document. I created a new PSD, embedded the old PSD into the new one, resaved, reimported to Premiere, and it worked.

[tc97]

I am having trouble importing a PSD from Photoshop cc to primiere pro cc and it when i converted it to jpeg first it said the bit depth was "unsupported" and when i used the psd version of the same this it said there was a generic error

[rohanbodh1989]

well this was easy for me had this problem, i just changed the format of the file and it worked just fine. i.e file was xys.mov i renamed the file to xyz.mp4 and it worked for me.

[Guest]

This worked for me! Was already prepared for a huge video converting marathon, thanks for the save

[CCBain]

Premiere CC v9.2 suddenly can't locate my layered PSD files, even though they haven't moved. I batch changed the color profile on them from Adobe RGB to sRGB and now it won't relink them, giving the dreaded "importer reports a generic error message".  HELP!

[kenl81560584]

hi guys. I've downloaded some videos from rutube.ru, under the format MP4. I used MPC Classic and played those videos well. But when I imported them to Premiere Pro CC, the program said "importer reported a generic error message". Some one can help me?

[dineshb29241042]

"THE IMPORTER REPORTED A GENERIC ERROR "

it is happening with A after effects files which includes the Photoshop files as well as

tried opening the same Project file on After effects working fine with out any Problem

tried to save in XML format and checked still not able to open it on Premiere pro

tried to clear the cache and checked not working, tried to reset the Preferences and checked

tried to open a file form a Auto save folder of After effects still not working

does it might be a activation issue with Premiere pro ?

[dineshb29241042]

Tried to reinstall the application and then i have also  tried to clear the cache and checked

and also tried to reinstall the application and checked

not working

tried by importing in XML format as well as from After effects

but the file give generic error in Premiere pro is working fine on After effects without any Problem

?

[pviljo101]

1) Deactive and Reactive as suggested

2) Using the Alt + Shift option when I launch premiere worked for me.  I'm no able to work with the files again and didn't have to uninstall and reinstall

[Aabh]

Having the same problem: Had a .psd, client wanted me to change the text color and delete a part of a graphic on one layer,  The names of the layers did not change, though I had to merge two layers together, I made sure the NAME of that layer is the same.

I went into the psd to change the text color, and now Premiere is giving me this error.  I haven't changed anything in the original Photoshop file except the artwork in the layers.  Naturally, this is a core element of my 15 minute presentation video and it has animated layers... so reassigning everything will add a day, if not two to the job.  Client is very unimpressed.

Is there a fast way to fix this problem without having to relink everything (At best) or make a NEW psd (Identical to the old psd) and rebuild all elements from scratch (At worst)?

Premiere has updated twice since I started this project... Photoshop three times (Once made it unusable to my large computer for a while I presume it was a video card conflict, because it went away with the next update) is there any reason this isn't fixable?  I am on Creative Cloud for the updates, but honestly this feels remarkably unstable... and it's rather embarrassing to be sitting with a client and have to explain that I'm going to need to stop working with them and add a day because Premiere has decided it doesn't like my psd for some unclear reason.