This project is read-only.

Add "SourceSafe needs Analyzed and Fixed" to homepage

Nov 7, 2011 at 7:07 PM
Edited Nov 8, 2011 at 2:56 PM

Could you add to the home page that Visual SourceSafe will need to be Analyzed and Fixed?  If the database is corrupt, your program fails.  Not because of VssMigrate.  But it might seem that way.

The command is:

"$ProgramFiles\Microsoft Visual SourceSafe\analyze.exe" -F -V3 -D -db -c -s "C:\Your-SourceSafe\data"

where C:\Your-SourceSafe\data\..\SourceSafe.ini exists.


This link says how to purge files that have been deleted, but not obliterated/purged.  If you don't purge them from the SourceSafe repository, VssMigrate will crash.
It is good to do this, even if the issue gets resolved per the suggestion in this issue (very helpful to me, as I applied it to the source-code, just in-case).

Nov 7, 2011 at 7:12 PM
Edited Nov 7, 2011 at 7:16 PM

Another suggestion (doesn't need to be home page):

If you can't repair the database because people are logged into it, have your NOC team, or yourself, copy it at night when you don't think anyone will be on it.
Then make the migration from the copy. I prefer the copy, as you can't do anything wrong or migrate mid-check-in.