PRB: "Incompatible Database Version" Error Running Analyze

 Last reviewed: March 10, 1997
Article ID: Q150646
The information in this article applies to:
  • Microsoft Visual SourceSafe for Windows, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows NT, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows 95, versions 4.0, 5.0

SYMPTOMS

When running Analyze Build 1309 or higher, you receive the error message: 

   Incompatible Database Version
This error usually happens when users upgrade from a 3.x version and have sufficient corruption in their 3.x database so DDCONV cannot convert one or more files. See DDCERR.LOG for clues to the identify of the file that is corrupted.

Analyze uses the VERSION.DAT file in the SourceSafe data directory to determine if the conversion and creation process was successful. The DDCONV.EXE file changes the contents of the VERSION.DAT file as one of the last operations before it completes. If there is a problem with the database conversion or some question as to the status of some of the files in the database, DDCONV does not change the contents of VERSION.DAT.

The Visual SourceSafe Explorer does not use VERSION.DAT. Rather, it relies on the contents of the UM.DAT file to determine the status of the database.

STATUS

This behavior is by design.

WORKAROUND

  • Try to correct errors reported by the 3.1 Version of Analyze. The 3.1 version should be run on the database before it is converted. For more information on utilities that can be run on the 3.1 database to correct problems, please see the following article in the Microsoft Knowledge Base:

    ARTICLE-ID: Q133054 

       TITLE     : Detecting and Fixing Database Corruption Errors in
               SourceSafe
  • Try to Purge/Destroy Permanently any files/projects that are not needed.
  • Remove bad files from SourceSafe. Purge the files. Upgrade. Add files back to the converted database. All of the above are done though SourceSafe operations, not directly to the database. All history is Lost on files that are added manually.
  • If all else fails, contact Microsoft Technical Support SourceSafe Support.

Keywords : SourceSafe kbusage
Version : 4.0 5.0
Platform : 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: March 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.