Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Names.dat may be corrupt
- Thread starter TomKane
- Start date
- Thread starter
- #2
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.
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.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question