Friday, October 13, 2006

SourceSafe 2005 issue fixed

More than 6 months ago, I have experienced an awkward problem with SourceSafe.

I periodically run the following script to launch the Analyze tool on SourceSafe databases:

Dim shell
Set shell = CreateObject("WScript.Shell")

Dim sVssAnalyzeCmd
Dim sVssAnalyzeExe
sVssAnalyzeExe = chr(34) & "C:\Program Files\Microsoft Visual SourceSafe\analyze.exe" & chr(34) & " -F -V3 -D "

'----------> First Project
sVssAnalyzeCmd = sVssAnalyzeExe & chr(34) & "d:\vss2005\project1\data" & chr(34)
shell.Run sVssAnalyzeCmd, 7, true

One day, Analyze was reporting the following error:

The file 0\DATA\\ is not a valid SourceSafe physical database file. It must be renamed to a file with an extension or moved to another directory outside the database.

I found a curious fix on the web: to work around this problem, rename the physical file for the database root. Use all uppercase letters in the new name.

I renamed d:\vss2005\project1\data\a\aaaaaaaa into d:\vss2005\project1\data\a\AAAAAAAA and it worked.

I am glad to realize that a fix has recently been made available by Microsoft at:

No comments: