12 Replies Latest reply on Oct 10, 2012 7:01 AM by Andyman_200

    PE2 "project appears to be damaged"

      Over the course of the past month, I occasionally get a message "The project appears to be damaged, it cannot be opened" about halfway through the project loading. I then go back to the prior day's version (I save each successive day's version as a different file) and redo a day's worth of edits and then move on. Is there any way to open and use a project which gives this error message, or have I lost that version?
        • 1. Re: PE2 "project appears to be damaged"
          Steve Grisetti Adobe Community Professional
          What are the source files you are working with and how did they get into your computer?

          Are your project and media files on your C drive or on an external drive?

          What version of the software are you using and have you modified the workspace in any way (i.e., undocking the panels, particularly the timeline) and moving them to other positions on your screen?
          • 2. Re: PE2 "project appears to be damaged"
            Level 1
            What are the source files you are working with and how did they get into your computer?
            Pictures, AV, songs and narrative. Pix and Video are home movies/oix. Songs are itunes or ripped from CD. Narrative is my recorded voice.

            Are your project and media files on your C drive or on an external drive?
            External, linked in through a USB

            What version of the software are you using and have you modified the workspace in any way (i.e., undocking the panels, particularly the timeline) and moving them to other positions on your screen?
            PE 2.0 (do you need some point version too?). I have not unlocked any panels or modified the work space. I merely expand and contract the work spaces when using them.

            My procedure is that I have been creating this 15 minute montage for about 2 months now, adding a bit each day. Each day I "save as" a new file so if there is a glitch, I have only lost a day's work. This problem happened about a month ago, and about 2 weeks ago, and this week, on different saved versions. Each time, I went back to the day before's version and just moved on from there. My first step after each failure was to recreate what I had done the day before -- so the same audio/video/AV are on the revised version as were on the corrupted version. The program works fine and loads fine for each day's new files after that (and I occasionally burn the work -- and am successful -- so I have a copy in case the whole thing blows up). But then the same (or is it new?)error happens a few days/weeks later.

            At this point, I am fine tuning, and not making significant daily changes; but it would be nice not to have to repeat steps, if there is a way to cure or avoid the issue.
            • 3. Re: PE2 "project appears to be damaged"
              Are you making a backup copy, too, and does the backup also behave the same way?
              • 4. Re: PE2 "project appears to be damaged"
                Steve Grisetti Adobe Community Professional
                First, check to see if your external drive is formatted as NTFS. Most come from the factory FAT32, which has a file size limit that will choke most video work.

                Second, optimize all your photo sizes to no larger than 1000x750 pixels, per the FAQs at the top of this forum. Oversized photos are the chief reason this program chokes.
                http://www.adobeforums.com/webx/.3bb8822c

                Finally, I still have no idea what kind of camcorder your video came from or how you got it into your computer, but there might be liabilities there too.

                Even still, the first two issues I noted should take care of about 95% of these types of problems.
                • 5. Re: PE2 "project appears to be damaged"
                  Level 1
                  I do not make a backup of each day's file, but already thought to do so from now on.

                  The video is mainly older VHS video converted through a digital camcorder. Don't know the exact specs of the cameras offhand.

                  Based on past instructions from you, the hard drive is formatted NTFS and most of the pix are small (in the 300kb range, as opposed to 1 .5 meg before conversion).

                  In addition to avoiding the problem, my real question is, is there a way to resuscitate a file that won't load, or is it lost and I have to go back to the day before?
                  • 6. Re: PE2 "project appears to be damaged"
                    Level 1
                    I do not make a backup of each day's file, but already thought to do so from now on.

                    The video is mainly older VHS video converted through a digital camcorder. Don't know the exact specs of the cameras offhand.

                    Based on past instructions from you, the hard drive is formatted NTFS and most of the pix are small (in the 300kb range, as opposed to 1 .5 meg before conversion).

                    In addition to avoiding the problem, my real question is, is there a way to resuscitate a file that won't load, or is it lost and I have to go back to the day before?
                    • 7. Re: PE2 "project appears to be damaged"
                      the_wine_snob Level 9
                      Ned,

                      In P-Pro, one can Import a Project into another Project. This often straightens out some minor glitches. Do not recall if PE will do this, but would be worth a look. Since PE uses Get Media, rather than Import, there might be limitations.

                      It is usually worth a look in the Project's AutoSave folder. There should be up to 5 AutoSave files in it. Go to Detail View, and choose the last one created. Note: Adobe programs will overwrite existing AutoSave files, using the same file name. Hence, #5 might not be the newest, depending on how long you've worked on the Project.

                      Last, there is a progam, XML Wrench, that can test XML files, which the Project file is. It can spot a lot of little problems, and help you fix them. It has a "test" mode and an "edit" mode. Often, the corruption is just a minor glitch in the header info.

                      Good luck,

                      Hunt
                      • 8. Re: PE2 "project appears to be damaged"
                        Level 1
                        The project from the corrupted date was in Auto Save, I got it, saved it under a new name, and it works fine. Thanks.
                        • 9. Re: PE2 "project appears to be damaged"
                          the_wine_snob Level 9
                          Ned,

                          "... and it works fine," are great words to hear!

                          Since you have already encountered a problem (these things seem to always happen, after they have happened the first time), I would recommend initiating one of two Save schemes:

                          1.) Open your re-named Project, and as you edit (maybe end of day, or after an intricate editing session) do Save_AS and increment your Project name, i.e. [Project Name]_01, 02, etc. What Save_As does is Saves a copy of your Project file to a new name, AND keeps this version in your editing window, i.e. you are working in a Project with the new name. Your old Project is no longer Open, and being edited. All changes from this point forward will be in the newly named Save_As Project, not your original Project. It will reamain exactly as you left it, when you did the Save_As.

                          2.) Save_As_a_Copy. This is similar, but with important differences. When you do this, I'd do the same incrementing of the filename. Now for the differences: you will be Saving your Project, as it exists at that moment with a new filename, [Filename] Copy_01, 02, etc. You can alter the filenaming convention, but I would recommend keeping the default word "Copy" in it. When Saved, you will STILL be working in your original Project and NOT in your Save_As_a_Copy. It will be locked in time to the point that you did the Save_As_a_Copy. Important distinctions.

                          I'd do one, or both, of these techniques, while you edit. I'd create folders especially for the Save output of each method, to keep things straight. The Project files are quite small, compared to the media used, so having incremented versions on your system will not take up THAT much space, and can really come in handy, if something goes pear-shaped. When you are finished, you can safely delete all of these Save_As/Save_As_a_Copy files. You will also have your AutoSave files as a third layer of defense. Just remember that these get overwritten in time. It's possible, when experiencing problems, to end up with corrupted AutoSaves, though not that likely. There is nothing wrong with making copies of these files, every now and then in another folder. This would be done via Windows Explorer.

                          Good luck,

                          Hunt
                          • 10. Re: PE2 "project appears to be damaged"
                            Opegasys

                            the_wine_snob wrote:

                             

                            Ned,

                            In P-Pro, one can Import a Project into another Project. This often straightens out some minor glitches. Do not recall if PE will do this, but would be worth a look. Since PE uses Get Media, rather than Import, there might be limitations.

                            It is usually worth a look in the Project's AutoSave folder. There should be up to 5 AutoSave files in it. Go to Detail View, and choose the last one created. Note: Adobe programs will overwrite existing AutoSave files, using the same file name. Hence, #5 might not be the newest, depending on how long you've worked on the Project.

                            Last, there is a progam, XML Wrench, that can test XML files, which the Project file is. It can spot a lot of little problems, and help you fix them. It has a "test" mode and an "edit" mode. Often, the corruption is just a minor glitch in the header info.

                            Good luck,

                            Hunt
                            A million thanx for your tip!!!

                            I´m using Premiere Pro CS4 and have been working on this huge project for more than 3 months now.

                            Today when I was doing some titleing (the project is soon finished) Premiere froze and when I restarted I got the message:

                            "The project appears to be damaged".

                            I tried to open a new project and import the real project into the new one without success,

                            I tried the autosaved copies (all 5 of them was corrupt!!)

                            So I started to realize that my project were screwed forever... And then I read your tip: Try XML Wrench...

                            I downloaded it, opened the projectfile in it and ran a "check well formed" on it.

                            The program directly found the error: One of my titles had a space in the name!

                            After I corrected the error in 3 or 4 places and saved the file I could open it again i Premiere Pro.

                            Thanks alot 8^D

                            • 11. Re: PE2 "project appears to be damaged"
                              the_wine_snob Level 9

                              That is great news. Even with one's direct redundancy of doing Save_As_a_Copy, and also having AutoSave set to ON with a workable frequency, things can go wonky with Project files. As you saw in XML Wrench, they are very intricate databases with links to everything.

                               

                              The ability to Import one Project into another (in PrPro), has saved many people. XML Wrench has saved many others.

                               

                              Thanks for reporting your success,

                               

                              Hunt

                              • 12. Re: PE2 "project appears to be damaged"
                                Andyman_200

                                If you are reading this page, there is a good chance you are freaking out. "Holy Crap--do I have to do all that work over again???"

                                 

                                I am just writing to say that after much freaking out on my part, the XML Wrench also worked for me. I was reluctant to try it--open the XML code and make changes to it? That sounds way above my computing capabilities. However, I decided to post here to tell other frightened people that using XML Wrench is very simple, in fact.

                                 

                                Here are the steps I followed (which I copied from another forum):

                                 

                                1. Do a google search for XML Wrench and download it. As I write this it's located at XMLWrench.com. It's free, and not a big, complex program.

                                 

                                2. Use it to open the corrupt file. When you go to "Open" in XMLWrench, it will start by looking for .xml files. Since your .prproj doesn't have the .xml (although it IS an xml file) you'll have to change the "open file type" drop down to "any file" in order for the .prproj to show up.

                                 

                                3. Simply go to the "Tools" menu in XML Wrench and perform a 'Check is well formed'.

                                 

                                4. It go down the code and stop once it finds the first error. Once you have fixed that error, you run "Check is Well Formed" again to find the next one (if any.)  Mine only had two errors (can you beleive the stress over two little errors!) but others said they were fixing errors for twenty minutes, so I don't know.

                                 

                                5. How to fix an error: Usually you will find "garbage data" in between some XML fields like this <NAME>&$d.~</NAME>. Just delete the weird stuff (&$d.~) in the middle, but leave the open and close tags there (<NAME></NAME>)

                                 

                                6. Once you've fixed every error, XMLWrench will tell you it couldn't find any more. ("Ok. File is well-formed.")

                                 

                                7. It is VERY important that once you fix all of the errors, perform a SAVE AS and name it "(project name).prproj". IF you do not name the extension '.prproj' then Premiere wont recognize it.

                                 

                                THANK YOU to the geniuses who figured this out!

                                 

                                And, if XML Wrench does not work for you, and your project is still damaged, I am terribly sorry and I sincerely hope you can find a solution to your problem! Best of luck!