What does "Error 10" mean? "An error occurred while loading your project. 10"

Question

Does anyone know what "Error 10" means?  For the first time, I'm getting a message that says, "An error occurred while loading your project. 10".  I'm getting this message when I try to open a project that I created yesterday.
I'm using Adobe Premiere 6 on a Windows 7 machine.  I have over 20 gigs of open space on the drive with all the project and support files.  And this machine with 2 gigs of RAM never has a problem opening other similar Premeire project files with even more still images plugged in.
All of my Premiere project files have always opened with no problem.  A similar file that this project file was created from with all the same base elements still opens with no problem.
This file almost finishes the "Loading Project - checking files..." process, but then I get the error message.
I had also saved a duplicate backup file for the project in question and it will not open either, so I believe that rules out a corrupt file... it is only this one project that I created yesterday that will not open.  This project file is only about 5.7 megabytes in size.
This file has many still images plugged in to it, but all the same images are plugged in to another base file that still opens correctly.
I've also tried closing all other apps to save memory but I still get the error.   I've also tried opening this problem file from within the application and I still get the same error message.
I read some troubleshooting information on the Adobe website about files that give error messages that will not open and it recommended adjusting the size of the virtual memory paging file in the system settings to twice the amount of RAM that is installed instead of being on the automatic setting, so I followed the instruction verbatim and restarted my machine and I still get the error message.
I've also read other troubleshooting info on the Adobe site that recommends to "delete the application preferences file" and "recreate the plugin cache file", but I'm not sure if "Error 10" indicates that those things are the correct procedures to use.
I could re-create this project file, but it has many tricky cutting and motion setting edits that will be difficult to reproduce and it took me a full day to create this project file.
Also, yesterday before initially closing this file, I was able to successfully render a test version to an AVI file and that video file plays fine, but neither the original project file nor the duplicate will open... I'm always getting the "An error occurred while loading your project. 10"   after the file almost finishes the "Loading Project - checking files..." process... it almost finishes opening but then I get the error message.
Thanks for any input on this problem.  You can see the error message screenshot below.
digi

Answer 1

Thanks Bill... me too.
After writing to Dennis Radeke on an Adobe.com blog about this and getting his very limited response, I wrote to him quoting something I read on the wiki page that you sent me the link to...
Adobe blog:
http://http://blogs.adobe.com/genesisproject/2009/11/having_weird_behavior_with_an.html#co mment-2701
Wiki page link that you gave me:
http://premierepro.wikia.com/wiki/FAQ:How_do_I_recover_a_corrupt_project%3F
Here's what my response today was...
Thanks for your reply DR.
My old version of Premiere 6 works perfectly on Windows 7.  I’ve created over a thousand different Premiere project files on this 5 year-old PC that was updated to Windows 7 last year.
All of my other Premiere 6 files open and maintain their original editability and all the features in this ancient version of Premiere work very well.
I own and use mostly Mac machines but I have one 5 year-old PC with a 160 gig hard drive with Windows 7 that I run Premiere 6 on because it’s a thousand dollar program that I had from 10 years ago that I didn’t want to repurchase. Buying a newer PC 5 years ago was far less expensive than buying a new copy of Premiere.  Some people seem to think, “Wow, just buy a new version of the software for a thousand dollars and a new computer with a 5 Terabyte hard drive.”, but that isn’t always the reality of some peoples financial situation.
With 20 gigs of open HD space, all of my previous, even more complex Premiere 6 files still open and edit just fine.  It is only this one file that I created Thursday that won’t re-open after closing it for the first time.  Since the backup copy of that file won’t open either, and all the support files open, play and work in other previous project files, I’m thinking that there is some glitch that happened when saving this file that is corrupting it now, making it unable to be re-opened.
Based on prior advice on multiple topics about Premiere 6 from people on the Adobe forum who use only newer versions of Premiere, most information that applies to the brand new Premiere Pro CS5 still seems to apply to the old Premiere 6.
I found that holding down Shift-Option while opening Premiere 6 trashes the preferences file. This became my work around since I can’t locate the preferences file based on your path noted (in your blog) nor via the other prefs file path published on the Adobe website.
But unfortunately, trashing the prefs file, resetting the plugin cache file, increasing the virtual memory paging file size, importing the problem project file in to a new project, nor anything else is working to allow this file to open.
Now I’m looking in to XML:Wrench to see if that can find the corruption in this file, but I’ve had a malware warning from one download source and the xmlwrench.com website says their download is only a demo version, but no price is listed… this seems somewhat strange and possibly deceptive.
But I read something on an Premiere Pro wiki page , quoted below, at this URL, that seems to be pertinent, and though my version of Premiere may be ancient, it seems that, according to this user’s concerns, Adobe is still having problems with current versions of Adobe software creating corrupt files…
http://premierepro.wikia.com/wiki/FAQ:How_do_I_recover_a_corrupt_project%3F
QUOTE:
“Can someone please advise – why on EARTH we should have to download XML Wrench and manually fix a corrupt Adobe project??? This is something common to all the Adobe “Support” forums on issues like this, and the many others that plague Adobe’s product (and I’m not being a mindless troll – I’ve been forced to use it for years so I do know the usability and other issues it has): it seems that people are excited because they’ve found a “fix” (which is more like a work-around) – purely because they’re understandably ecstatic that all their hard work isn’t comPLETEly lost.
However, Adobe should be making sure their product isn’t so buggy! This issue should be fixed (as just one example). Adobe should be finding out what causes the corruption in the first place and fixing it. And whether it’s some other codec on the system that’s caused it is no excuse – their software should have better error management built into it. I’ve seen other issues where an Adobe support representative has happily replied: “oh, that’s a known issue since version [3 versions back] – don’t worry, most users are aware of the work around for it: just select and move all of the items in your timeline each time you open the project and you’ll be fine!”
I’m sorry to rant on – but can some other users please explain the above to me? (i.e. why aren’t more people annoyed about this and complaining to Adobe to fix these things).”
UNQUOTE
All of this coming from an experienced user of Adobe products complaining about needing XML:Wrench to fix corrupt Adobe files seems relevant.
In addition, why does no one, including the Adobe knowledge base, have any info about what “An error occurred while loading your project. 10″ means?… why isn’t there a database that identifies Adobe error numbers by the simple number itself?  The only info I was able to find identifying “Error 10″ on the Adobe site was a software installation error, not a project loading error.
Now I find myself chasing a clean download of XML:Wrench in order to hopefully fix this corrupt file.  Whether I’m using Premiere 6 on a 160 gig hard drive with 20 gigs of open space or Premiere Pro CS5 on a 5 Terabyte hard drive with 3 Terabytes of open space, the problems, according to other users, seem to be the same as ever with corrupt Adobe Premiere files, based on what I’ve been reading across the internet.