locked
Visual Sourcesafe 6.0 Analyze error RRS feed

  • Question

  • Hello, I run Visual Sourcesafe Analyze nightly on our database and recently started getting the error below:

    Analyze Visual SourceSafe Version 6.0c (Build 9350)
    Database analysis in progress @  10/24/12; 2:24p.
    Building the project list.
    Checking cross file relationships.
    Checking parent/child relationships.
    Removing unused items from the database.
    Started analyzing user management system.
    Successfully completed analyzing the user management system.
    Validating the Security System.
    File or project not found
    Analysis complete @ 10/24/12; 3:48p.
     Potentially serious errors or inconsistencies were found.

    I run it with the following options: analyze -c -d -f -v4 e:\VSS\Data

    Any ideas on how I can resolve this?  The posting on August 25, 2010 by JeanCao reported a similiar issue and Grant from Microsoft provided a tool called VSSMS which purged deleted files, projects and fixed the problem.  Is this tool available?  Any assistance you can provide is appreciated.

    Wednesday, October 31, 2012 8:48 PM

All replies

  • Unfortunately, VSS 6.0 is too old, and I also cannot find Grant from MS, there so many Grant from our list, and cannot know where we could get the VSSMS tool. But you coulr try to update the VSS6.0c to 6.0d or the latest version VSS2005 version.

    Bob Bao [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, November 1, 2012 6:18 AM
    Moderator
  • Thanks for the feedback Bob.  We've had bug issues with VSS 6.0d in the past so we stayed with 6.0c.  Do you know if Nancy Shao is still around?  She was the moderator on JeanCao's issue and may have kinowledge of the VSSMS tool.  Another question.  Is the VSS2005 fully integrated for Visual Studio 6?  We're in a legacy software development world here and upgrading is not an option at this time.
    Thursday, November 1, 2012 4:20 PM
  • VSS2005 works with VS 6.

    Upgrading to VSS 2005 will very likely solve this problem. We have solved this kind issues for many clients.

    Kevin Gao

    MCSD, MVDBA, MBA

    Friday, November 9, 2012 8:34 AM
  • We aren’t ready to upgrade from VSS 6.0 to VSS 2005 yet due to compatibility issues with our code and tools.  However, we found the VSS 2005 Analyze.exe utility provides a lot more detail on VSS errors than the VSS 6.0 Analyze.exe, so we decided to use the VSS 2005 Analyze.exe as a tool to identify the problems in our VSS 6.0 database and fix the problems by hand (based on the errors we saw with VSS 2005 Analyze).

    Here’s what we did to fix the problems with our VSS 6.0 database:

    Install VSS 2005 on a test machine - D:\VSS2005

    1. Copy latest daily VSS database backup to local drive on test machine -  D:\VSS
    2. Run full VSS2005 Analyze scan on database - D:\VSS2005\analyze –c –d –f –v4 d:\vss\data
    3. Run VSS 2005 SS command line utility to generate physical.txt file displaying VSS formatted files (eg. JEOEAAAA) and what’s in them.
      1. To do this, create an environment variable – add name SSDIR and value D:\VSS (path where the srcsafe.ini file is located.
      2. Run command - D:\VSS2005\ss physical –r $/ > physical.txt - to generate a list of all VSS files (recursive from database root) and pipe the results to a text file in the current directory.
    4. Compare physical.txt file with display window and analyze.log file results.  This allows you to reference exactly which formatted files had the problem in order to manually fix them. 

    We didn’t trust the VSS 2005 Analyze program to fix our master database, so we used the manual process mentioned above to make sure we had complete control over the repair process.  We did however have to repeat steps 2 – 5 a number of times before we had a clean database.

    Wednesday, December 12, 2012 9:48 PM