Welcome to the forum.
Is it safe to assume that you are created the Project on the PC, and are still using the PC?
Have you done any housekeeping, and perhaps deleting what appeared to be some empty folders in the Project's hierarchy? (That is what Jim is also asking). The folder structure is important, and must be maintained, or there will be issues.
Is your Project on an external HDD? If so, is the OS assigning the drive letter, or have you assigned the drive letter manually in the OS? Is that drive letter the same, as when the Project was created?
Good luck, and please let us know a bit more.
In both CS4 and CS5 at least, a missing folder gets a "Cannot open project; the folder for this project cannot be found" message. Who knows what message happens if only certain elements have been moved, etc.
Do you get an error number or any additional information in the "Invalid project file" message?
The error messages that you cite, are what I am used to, as well. However, as we all know, sometimes the error messags in Encore can leave a lot to be desired, and there have been instances where "wires" got crossed, and Encore received an error from the Sonic modules, or from the OS, but could not really act upon it - so it guessed at what could be the problem.
I have only seen the error message, that you mention once, when I Deleted some of the necessary folders by mistake. All it took was to create the necessary folders, though they were empty, as the originals had been, and all was good again. In all of my years with the program, that was but one of only two errors, that I have ever encountered in Encore, so I have to rely on reports from "the field," when it comes to errors in Encore.
The only "Invalid Project Flie" type error, that I can recall, was when users attempted to Open a Mac NCOR on a PC, or vice versa. Do not recall the exact syntax of those errors, as I have never seen them myself.
I used CS5.1 Encore. Did not move or delete anything!
Also, when saving a copy of ANY project, I save to a second location called "back up" and 90% of the time I get a pop up box "General Error" but NOT when I save to my usual location.
Using my C: drive.
I re-made my project (menus) and saved it again on my C: drive with all supporting files. It saves fine and I also save a 2nd copy in another folder (in C:) as 'back up', BUT when I save a second copy of the same project, sometimes the 'back up' gives me the General Error pop up box. When I re-save the project in the ususal C: location, it appears ok now, except when I save another back (I used dates for my files, ie "Project06162011.ncor" or "BackUp06192011" which is Project Name with the month/day/year so I can keep a continuing record of my progress).
Oh, yea, I'm using Window 7 Pro (fully updated) on a Dell Studio laptop. All works fine so far. I have an external Western Digital HD at 10,000 rpm on my eSATA port for video files.
In a month or so I'm looking at a Mac all-in-one 3.2GHz, 16 gig ram with SSD and HD, 27 inch!!!! I'm so done with Windows!
I wasn't clear re the answer to my question: Do you get an error number or any additional information in the "Invalid project file" message?
I understand about the general error also. But when you get the "Invalid Project File" message, anything else? You might check any error logs and the windows event log.
Your new project is okay, right?
You mentioned about saving your projects on the external hard drive. Some times the external hard drive might cause some problems with Encore's communication with the drives. This is because encore tries to acquire some hardware before opening the project and if it can not acquire the hardware, it throws out some error.
Updating the driver software might help.
NO error numbers. ONLY "Invalid Project File".
When I re-make all my menus (by first drag/drop all images/PSD files to a particular folder in C: drive) and save the project and save a second copy to a 'back up' folder on the C: drive, it NOW behaves.
Before, i was saving to my external Western Digital 10,000rpm drive eSATA. Never had a problem before. Other files open/closed well.
ONLY now having a "General Error" ONLY when I save a copy of current work into 'back up' folder. When I re-save in my usual C: drive folder, no problem. PS: Back up is ALSO on C: drive!!!
Weird. Any guesses?
You know what. Adobe. You need to fix this bug. If not fix it, you need away for customers and your engineers know what what was corrupted in the project file. You can't run a business with a tool that let's you do all these hours of work and then decide arbitrarily not to work and become unrecoverable. You should be sued for this kind of stuff. Leaving this kind a problemt to a users forum is criminal. Here is the bug I submitted. Adobe GET INVOLVED.
Concise problem statement:
Encore fails to open due to "Invalid Project File."
Steps to reproduce bug:
1.Create a encore project with menus an multiple timelines where assets are references to CS5 Premiere and After Effects projects. Encore and assets project files are located on an external HDD connected using USB 2.0. Encore is installed to an internal SATA C: volume.
2. At this point, I'm able to close and open the encore project.
3. Do a build that includes transcoding. Building to an DVD ISO image file.
4. Build completes, save Encore project and close it.
5. Shutdown computer.
6. Power on computer, try to open Encore project.
Open of Encore project fails: "Invalid Project FIle." Weeks of work is lost.
Open needs to succeed or Encore needs to indicates specifically what is invalid. And, there needs to be a way to recover the project. There are no logged events or error messages to indicate the root cause of the problem, that is, what makes the project file invalid. The Internet it full of Encore "Invalid Project File" pleas for help. Please fix this issue. It's a deal breaker.
BTW, Mr Hunt. Changing drive letters on external disks should never result in project open failure due to "Invalid Project File" and here's why. Project references to project data files should only use relative path. If the Encore doesn't do that, it's a code defect. This isn't a problem anyway, simple deductive reasoning indicates the problem is a corrupt project file - not something external to it. Assets referenced by a project file simply become offline when the project is opened. The project file still needs to open. This is an out and out a stupid Adobe Encore defect and they need to get involved and fix it.
My specifics: Window 7 Pro 64bit. Encore version: 18.104.22.1688. I use MacDrive 9.0 to access a formatted Mac disk as an external HDD (not Western Digital, I've long since given up on them) connected by USB 2.0. It's not MacDrive 9.0 since the problem occurred on MacDrive 8.0 as well. I might be related to USB connectivity. I'm checking that out now. The problem started to happen after I upgraded to CS5.
What tha? Today is the first time I've Heard Of, Seen, or Recieved this error... ever!
- This project started on my Mac but something is awry with my Adobe/Mac setup so I did a minimal Adobe installation to my Win7 64bit PC laptop. (Pr CC, Pr CS6, & En CS6)
I just finished Building & Transcoding my project in En CS6 on my laptop.
I closed En and went to lunch. When I tried opening my project an hour later, I recieved the error.
Trying to move project folders into a new En project structure prompted the same error.
Rebuild: Media on External Harddrive
1. New En projects started on Desktop (1 for DVD - 1 for Blu ray)
2. Import Ps Menu... restarted En... OK
3. Import Audios (.wav)... restarted En... OK
4. Import Videos (.m2v)... "Indexing"... "Pending"... restarted En... OK
5. Create New Timelines from Media... "Pending"... restarted En... OK
6. Add Text to Menu... restarted En... OK
7. Created Buttons from Text... restarted En... OK
8. Linked Buttons to Timelines... restarted En... OK
9. Routed DVD Operations... restarted En... OK
10. Building DVD... Fingers Crossed!
* I have lost way too many hours of work due to various Adobe related issues over the last couple of weeks.
DVD Authored Successful!
(only difference was that I did NOT store the project on the external HD with the media... external HD the problem?)
Now, on the the Blu ray.