8 Replies Latest reply on Dec 3, 2013 9:19 PM by garymanilow

    "The project appears to be damaged. It cannot be opened".

    garymanilow Level 1

      The title says it all. I was editing offline and everything was fine a few hours ago, then I opened the project offline again and got that message. I don't want to mess with it too much until I can find some support from Adobe.....   Seen this before?

        • 1. Re: "The project appears to be damaged. It cannot be opened".
          Steve Grisetti Adobe Community Professional

          What do you mean by "I was editing offline" and "I opened the project offline"?

           

          Which version of the program are you using and on what operating system?

           

          Are you  using Premiere Elements' File/Open to open a .prel file?

          • 2. Re: "The project appears to be damaged. It cannot be opened".
            garymanilow Level 1

            1. I was not connected to the web during the interval when the problem occured.

            2.Premiere elements 11. Windows 7.

            3. I open it both from Elements/open as well as opening the file directly from a folder.

            • 3. Re: "The project appears to be damaged. It cannot be opened".
              the_wine_snob Level 9

              Gary,

               

              Three things that I would try:

               

              1. Look in your AutoSave folder for that Project, and find the latest - try to Open that. Note: if the defaults were not changed, you will have 5 AutoSaves in that folder. As AutoSave files are FIFO (First In - First Out), I would look at that folder with Detail View, and check the Date/Time of each file - #3 might be newer, than #5. Try each AutoSave file in reverse order - newest first, and work backward, until one does Open correctly.
              2. As a PREL file is XML, one can use a free utility, XMLWrench, to test the PREL's header. When going to Open the PREL into XMLWrench, you will likely need to change the file extension from "XML" to "All Files," to see the PREL's.
              3. If your issue is due to a bad/corrupt Asset, one other test would be to use Windows Explorer, to "hide" the Assets. I would Move all to separate and different, newly created sub-folders, say "Video," "Still," "Audio," etc.. Then, try to Open that original PREL again. If it gets past the initial Open stage, you should get a dialog asking "Where is file ____ ?" Then, navigate to the sub-folder, where you Moved that Asset type, say "Video" sub-folder with your Video Assets. Locate that first "missing file," and PrE will attempt to relink to it, and then automatically attempt to relink to all other Video Assets in that sub-folder. This process will repeat for each Asset type, in those sub-folders. If the Open process hangs, or gives an error message, then you know which Asset type has a problem. One can then manually separate those Assets, as before, but into individual sub-folders, so that you can isolate on the one bad file - hopefully. Depending on the number of Assets in that Asset type, it can be a bit tedious, but if you can isolate a problem Asset, you can then investigate how to handle that.

               

              Good luck, and thanks for letting us know about the "offline editing." I had the same question as Steve G did.

               

              Hunt

              • 4. Re: "The project appears to be damaged. It cannot be opened".
                Steve Grisetti Adobe Community Professional

                Also, why tempt fate? Why not try opening a project from Premiere Elements' File/Open menu?

                 

                Just in case there's a problem with your file associations.

                • 5. Re: "The project appears to be damaged. It cannot be opened".
                  garymanilow Level 1

                  I got in touch with support and they accessed my machine and said it could not be opened in elements but could be opened in Pro. So I'm downloading a trial version of pro which he claimed I could open the project with. I'll be camping out here for the several hours it will take to download and see if he's correct.

                   

                  Bill, my auto save was corrupted at some point. I've had to do manual saves (or lose all work from the previous manual save) for several months. I'll look for auto-saves for this project but haven't seen any so far. I'll look at your "option 2" as well and maye dig at option 3 to see if I understand it.

                   

                  Fingers crossed. I'm at a few hours remaining of editing on a project I started in May.

                  • 6. Re: "The project appears to be damaged. It cannot be opened".
                    garymanilow Level 1

                    Update..........!

                     

                    My original post said that "the auto save was not working". This was true, in the sense that my main project file would not update unless I saved it on my own. However, after 2 days and many hours of dealing with adobe tech support, I thought I would have to start the entire project from scratch. While looking for a file, I saw the folder for the 5 most recent auto saved projects.

                     

                    Huge waste of time with their techs. They were in my computer the whole time and did not see the file.

                    • 7. Re: "The project appears to be damaged. It cannot be opened".
                      A.T. Romano Level 7

                      garymanilow

                       

                      Are you all resolved on a path to get your job done?

                       

                      I came across this Adobe document regarding troubleshooting damaged projects. You might be beyond it by now, but I will post the link just in case.

                      http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html

                       

                      ATR

                      • 8. Re: "The project appears to be damaged. It cannot be opened".
                        garymanilow Level 1

                        I found a back up copy of the project, so yes, it's resolved.