TheChaseMan's Frenetic SoapBox

Always looking for better ways to do things...

VSS Error: File Names.dat maybe corrupt

Uh oh! There's nothing worse than a problem with your source control database. Even though we all consistently back those up, right? Yeah, it's still scary. So, for anyone who runs into this problem, and you are thinking of using the Analyze6.exe Utility - don't bother. That is, don't bother for the following symptoms. For some reason I had 3 files that had a zero length name that I couldn't delete, rename, or anything else. This utility was supposed to fix everything by running "analyze -f x:\vss\data" from a command window. No dice. But, what DID work was using the admin utility to archive the files. Crazy, but true.
Digg!

posted on Tuesday, July 05, 2005 9:22 AM

Feedback

# re: VSS Error: File Names.dat maybe corrupt 7/27/2005 6:25 AM Depressed Developer

How do you get the admin utility to fix this problem?

# re: VSS Error: File Names.dat maybe corrupt 7/27/2005 9:11 AM Sean Chase

The admin utility lets you either delete or archive the files. That's all I did and it got rid of the problem. I'm pretty sure Visual Studio 2003 is what caused the problem to begin with because I moved files from one folder to another, got a warning about saving the file, selected overwrite, and then KABOOM! In that sense, VSS doesn't work and play well with VS. :-(

# re: VSS Error: File Names.dat maybe corrupt 3/30/2006 3:57 AM re: VSS Error: File Names.dat maybe corrupt

re: VSS Error: File Names.dat maybe corrupt

# re: VSS Error: File Names.dat maybe corrupt 3/30/2006 3:58 AM re: VSS Error: File Names.dat maybe corrupt

re: VSS Error: File Names.dat maybe corrupt