PRB: Unable to Open Project Error When Running Analyze

 Last reviewed: May 27, 1997
Article ID: Q153502
The information in this article applies to:
  • Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows 95

SYMPTOMS

Running Analyze returns the following error message: 

   "Unable to open project <DOS path>\a\aaaaaaaa" Continue Y?

CAUSE

The analyze utility is unable to find the database.

RESOLUTION

Ensure that Analyze is pointing to the correct database location. It should include DATA. For example, if the database resides on a file server mapped to drive F: 

      Analyze -i- f:\VSS\data
The full syntax is:

ANALYZE [-B<directory>] [-C] [-F] [-I-] [-V] [-X] [-?] [-H] <Full Database Path>

This particular message is corrected in later revisions of Analyze.exe. However, later versions of Analyze (specifically 1309 or above) also fail if you don't include the data directory as part of the entire path to the Database. In that case, the following error appears: 

      "File '<Path Used>\version.dat' not found"
where the Version.dat file is located in the data directory. For more information about the newest analyze utility, please see the following article in the Microsoft Knowledge Base: 

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

STATUS

This behavior is by design.

Keywords : kbtshoot kbusage vss
Version : 4.0
Platform : 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: May 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.