PRB: Error "Names.dat may be corrupt" Appears

Last reviewed: April 18, 1997
Article ID: Q140593
The information in this article applies to:
  • Microsoft Visual SourceSafe, versions 4.0, 5.0

SYMPTOMS

The error "Names.dat maybe corrupt" occurs when starting Visual SourceSafe, when trying to gain access to a file or project, or when running ANALYZE on the Database.

CAUSE

The Names.dat file in the database contains information on the 8.3 names that correspond to files that have long file names in SourceSafe. When this error occurs, SourceSafe cannot find the correct information in the Names.dat file for the file or project that it is trying to retrieve information on.

RESOLUTION

If you know the name of the file or project where the error occurs, rename the file to an 8.3 name, and then name it back from the Visual SourceSafe Explorer or Command Line.

If the Visual SourceSafe database is on a Novell server, do both of the following:

  1. Make the names.dat sharable (use Novell's FLAG command, which is similar to DOS's ATTRIB command).

    -and-

  2. Change the Client on the Win95 computers to use the NetWare Client 32 client rather than the Microsoft Client for NetWare. The NetWare Client 32 client is a free download from Novell. Please see their site at http://support.novell.com for more information on that client.

The new Analyze.exe will rebuild the Names.dat file. Run Analyze with the -F switch to make changes to the database. Make sure no one attempts to gain access to SourceSafe's database while ANALYZE -F is running.

NOTE: When you are modifying the SourceSafe database, it is always a good idea to back up the Data directory and all subdirectories first should you need to recover.

Additionally, if the Visual SourceSafe database is on a Novell server, the error message will be returned if the Names.dat is not marked as sharable.

STATUS

Microsoft is researching this behavior and will post more information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For additional information on Analyze, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q139566
   TITLE     : SAMPLE: ANALYZE5.EXE Utility for Visual SourceSafe
 

	
	


Keywords : kb3rdparty kbusage SourceSafe vbwin
Version : 4.0 5.0
Platform : MS-DOS NT WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.