vss 2005 analyze - unknown error message

rosam

unread,

Nov 9, 2005, 3:46:45 PM11/9/05

to

When running analyze on my sourcesafe database using the following command:

"C:\Program Files\Microsoft Visual SourceSafe\analyze.exe" -F -V3 -D
"d:\srcsafe.net\data"

I get the following output:

Database analysis in progress @ 05-11-09;20:59.
The file T\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.
Analysis complete @ 05-11-09;21:05
Some errors or inconsistencies were found and fixed.

I am unable to find the file refered to in the error message (T\DATA\\).

The errror persists even if I run analyze several times.

Any suggestions on how to fix this problem?

--
/Thomas

Kevin Yu [MSFT]

unread,

Nov 9, 2005, 11:46:19 PM11/9/05

to

Hi Thomas,

It seems the file that VSS is referring to does not exist in the database.
That's why you cannot find the file and the error message appears. Since
the file is already missing, it's hard to recover this, unless you get the
file back, I think.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

rosam

unread,

Nov 10, 2005, 1:32:03 AM11/10/05

to

You say that it seems that the file does not exit in the database and that
might be true. I find it hard to belive that a file named "T\DATA\\" ever has
existed
There must be something wrong with the error message, no file can be named
"T\DATA\\". The other issue is how do I get rid of the problem (or the
message if there is no problem)?.
--
/Thomas

Dan Freeman

unread,

Nov 10, 2005, 7:36:09 PM11/10/05

to

Sometimes VSS sees ghosts and all you can do is shrug and say "OK, well,
that file doesn't exist."

I have 3-4 errors that show up every week and as long as they don't *change*
I ignore them.

Dan

rosam wrote:
> You say that it seems that the file does not exit in the database and
> that might be true. I find it hard to belive that a file named
> "T\DATA\\" ever has existed
> There must be something wrong with the error message, no file can be
> named "T\DATA\\". The other issue is how do I get rid of the problem
> (or the message if there is no problem)?.
>

Kevin Yu [MSFT]

unread,

Nov 11, 2005, 1:49:55 AM11/11/05

to

Hi Thomas,

It's hard to tell what is going on in the database without taking a look.
Is there any difficulty for you to build and run the project with this
error exists?

rosam

unread,

Nov 11, 2005, 2:47:03 AM11/11/05

to

Kevin,

The problem here is not preventing me from building. A lot of other problems
are but they are not related to sourcesafe. I'll leave the problem for a
while and hope that it goes away, if not I will post again for a solution.
--
/Thomas

Kevin Yu [MSFT]

unread,

Nov 11, 2005, 9:51:37 PM11/11/05

to

Hi Thomas,

Thanks for your understanding. Please come back to the thread if it doesn't
go away.

Alin Constantin [MSFT]

unread,

Nov 12, 2005, 5:14:32 AM11/12/05

to

Hi Thomas,

I suspect that in the "d:\srcsafe.net\data\T" folder you have a file or
subdirectory called "DATA".
If that's true, you can delete that file, as it's not part of the VSS
database.

I also think that VSS analyze would have fixed that problem if the -FP
parameter would have been passed to analyze.

--
Alin Constantin

This posting is provided "AS IS" with no warranties, and confers no rights.

"rosam" <ro...@community.nospam> wrote in message
news:8FBE717C-D94F-4D82...@microsoft.com...

rosam

unread,

Nov 15, 2005, 4:26:10 AM11/15/05

to

Alin,

Thanks for the suggestion. I checked and there is no folder named DATA in
the "d:\srcsafe.net\data\T" folder. I also tried running analyze with -FP but
the error still remains.

--
/Thomas

Alin Constantin [MSFT]

unread,

Nov 15, 2005, 5:06:54 AM11/15/05

to

Hi Thomas,

If -FP flag doesn't fix the error, I think the message may be possible to a
bug in analyze.
I've found a place in the code where we take a file_path string, extract the
last 8 characters of it, try to interpret them as a physical file (like
bcrfaaaa), and if we fail analyze displays that error message.
The string "T\DATA\\" contains exactly 8 characters and it loos like the
termination of a path like "D:\srcsafe.neT\DATA\\".
(I don't know what could cause analyze to interpret such path as a file path
though)

Can you try to rename the database folder from "D:\srcsafe.net" into
"D:\srcsafe.xxx" and rerun analyze on the database?
If I'm correct, it will display the error message for "X\DATA\\" this time -
in which case it means analyze has a bug and you should ignore the reported
error.

Thanks,

--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.

"rosam" <ro...@community.nospam> wrote in message

news:081C68FC-26F8-4B49...@microsoft.com...

rosam

unread,

Nov 15, 2005, 8:00:02 AM11/15/05

to

Alin,

You were right, I renamed it to D:\Srcsafe.XYZ and got the following output
from analyze:

Database analysis in progress @ 05-11-15;13:40.
The file Z\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.
Analysis complete @ 05-11-15;13:41

Some errors or inconsistencies were found and fixed.

I also also renamed it to a folder name witout a period (.) to check if the
period made sorucesafe treat it as a file name, but that made no difference.
The error message still contains the last character of the folder name
followed by "\DATA\\".

BitBasher

unread,

Nov 23, 2005, 11:20:45 AM11/23/05

to

In article <654DE87E-844E-4A82...@microsoft.com>,
ro...@community.nospam says...

>You were right, I renamed it to D:\Srcsafe.XYZ and got the following output
>from analyze:

AH-HA! I'm having this exact same problem, but I reported it in
microsoft.public.vstudio.sourcesafe.

Also, I've seen the exact same thing as rosam is seeing, that the garbage
error message is based on the command line path provided.

Also, -FP does NOT fix the problem.

Analyze needs a PATCH so that is displays the CORRECT filename that is "bad"
so we can track it down and deal with it. Right now, since analyze is
displaying a "bad" string, it's virtually impossible to track down the file it
is complaining about (I have 50,000+ files in my database).

Bit.

Alin Constantin [MSFT]

unread,

Dec 9, 2005, 5:30:35 PM12/9/05

to

Hi Thomas,

We have found the cause of this problem, and there is an easy workaround.

Analyze logs incorrectly errors like "The file T\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" for any
database that has a label applied to the root folder $/.

The bug is legacy from DataWiz code that was integrated into Analyze2005.
The code does a case-sensitive comparison to "AAAAAAAA", the physical file
for the root folder $/.
Since normally the root file name uses lowercase characters, the comparison
fails and we end up calling incorrectly a function that logs the false error
message.

A quick solution to the problem is to rename the physical file for the
database root to use capital leters ("rename <vss_database>\data\a\aaaaaaaa
AAAAAAAA") and analyze will stop reporting the false corruption message.

--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.

"rosam" <ro...@community.nospam> wrote in message
news:8FBE717C-D94F-4D82...@microsoft.com...