×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Names.dat may be corrupt

Names.dat may be corrupt

Names.dat may be corrupt

(OP)
Hi,

We are getting the following error when we go into sourcesafe:

\\vs1bkcfc1\bkccorpit\corpit\sourcesafe\data\names.dat may be corrupt

Has anyone ever come across this before?  Is a restore the only option?

Thanks,
Tom

RE: Names.dat may be corrupt

(OP)
We ran the analyze utility with the -f option which got rid of the problem stated above but ir also reported another error:

The file 's:\corpit\sourcesafe\data\w\whsbaaaa' appears to be corrupt.  Unable to read the format or header.

So we're looking at restoring the file - we gor this oput of the microsoft site:

The file "<Physical Log File Name including path>" appears to be corrupt. Unable to read the format or header.
Example:
The file "f:\vss\data\O\ORLAAAAA" appears to be corrupt. Unable to read the format or header.
Cause:
Files in Visual SourceSafe have format and header records to identify the file. One or both of these is corrupted. This error is very serious because it usually indicates that the rest of the Log file is damaged.

In many cases Analyze will report this error on files that are not needed by the database, often they have a size of 0 bytes. First try moving the files that report this error out of the \data\a-z directory, along with any files that have the same name with an extension, usually .a, .b or .old.

If rerunning analyze no longer reports this error, no further action is necessary.
Steps to Resolve:
·    The best solution is to retrieve the file from backup.
·    If no backups are available and the file is a project, delete the files from the DATA\?\ directory. Be sure to delete the file with the extension of .a or .b and the file with no extension. Then run Analyze -F <Path to Data:gt; to clean up the links. All files that were in that project are likely to be lost.
·    If it is a file, then make a copy of the data file (the one with the extension of .a or .b), and then delete the files from the DATA\?\ directory. Delete the file with the extension of .a or .b and the file with no extension, and then rename the .a or .b file to its real name. Finally, add the file back into Visual SourceSafe. You will have to Identify the file. See directions for identifying a file at the beginning of this article.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close