>>>>I have installed VSS 6.0 When I try to run it, it tells me that the common database is corrupted with no way of fixing it, either by ignoring the message or otherwise. I can't find this as a reported bug. Anybody else experience this? If so, how did you fix it?
>>>>
>>>
>>>Have you tried selecting the Analyze & Fix VSS DB Start menu option under the Visual SourceSafe entry in your start menu? This launches VSS's Analuze.EXE with the command line parameters -f -c -d -v1 against the default VSS database specified on the command line (on my system, with VSS 6 installed on my D: drive on my NT Server, the command line reads:
>>>
>>>

"D:\Program Files\Microsoft Visual Studio\Common\VSS\win32\ANALYZE.EXE" -f -c -d -v1 "D:\Program Files\Microsoft Visual Studio\Common\VSS\data"

>>
>>
>>When I run this against the installed files, I get a message that 'Version.dat' not found. The only .dat file in the folder is um.dat. I put that at the end of the program statement and I get a message that it can't read the file, that maybe it is corrupt. I looked on the Visual Studio install disks and that is the only .dat file out there. Kind of a dead end at this point. Thanks for your input.
>
>It sounds like you're trying to run VSS 6 against an unconverted (or unsuccessfully converted) VSS5 database. If you still have a copy of the VSS 5 database administrator, trying running that against your Source Safe database; if it runs, then you need to convert the old VSS database to VSS 6 before using it with VSS 6.


Negative. I did not have VSS before purchasing Visual Studio 6. However, something interesting is that the UM.DAT file shipped with VSS has a date of 5/21/98 while all other files on the disk have later dates. I don't have VSS 5. Guess I'll have to call MS. There are no threads on their tech support site concerning this. Thanks.