Q279192: FIX: Names.Dat Corruption Is Not Repaired by Analyze Utility

Article: Q279192
Product(s): Microsoft SourceSafe
Version(s): 6.0
Operating System(s): 
Keyword(s): kbSSafe600bug kbSSafe600fix kbAnalyze kbDSupport kbGrpDSSSafe kbVS600sp5fix kbSSafeAnal
Last Modified: 31-JUL-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Visual SourceSafe for Windows, version 6.0 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you run the Analyze utility for Visual SourceSafe 6.0, you receive the
following error message:

  The NameSet Information for [file name] is corrupt.

If you run the Analyze utility subsequently with the repair switch "-F," the
corruption is not repaired.

STATUS
======

Microsoft has confirmed this to be a bug in the Microsoft products listed at the
beginning of this article. This bug was corrected in the latest service pack for
Visual Studio 6.0.

For additional information about Visual Studio service packs, click the article
numbers below to view the articles in the Microsoft Knowledge Base:

  Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

  Q194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed

You can download the latest Visual Studio service pack from the following
Microsoft Web site:

  Visual Studio Product Updates
  (http://msdn.microsoft.com/vstudio/downloads/updates.asp)

REFERENCES
==========

For more information on the Analyze utility that is included with Visual
SourceSafe, please see the "Best Practices Guide" available on the following
Microsoft Web site at:

  http://msdn.microsoft.com/library/default.asp?URL=/library/techart/vssbest.htm

Additional query words:

======================================================================
Keywords          : kbSSafe600bug kbSSafe600fix kbAnalyze kbDSupport kbGrpDSSSafe kbVS600sp5fix kbSSafeAnalyze 
Technology        : kbSSafeSearch kbAudDeveloper kbSSafe600
Version           : :6.0
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================