PRB: "incompatible database" Error

Last reviewed: March 4, 1997
Article ID: Q123468

The information in this article applies to:

SourceSafe for MS-DOS, versions 3.0x
SourceSafe for Windows, versions 3.0x
SourceSafe for Macintosh, versions 3.0x
SourceSafe for Windows NT, versions 3.0x
SourceSafe for UNIX, versions 3.0x
Microsoft Visual SourceSafe for Windows, version 4.0
Microsoft Visual SourceSafe for Windows NT, version 4.0
Microsoft Visual SourceSafe for Macintosh, version 4.0

SYMPTOMS

The error "incompatible database format" can occur after updating from a 2.x version of SourceSafe with SourceSafe 3.1.

In Visual SourceSafe 4.0, the error has been changed to "incompatible database."

CAUSE

There are two potential causes for the "Incompatible Database" error.

Cause #1: Visual SourceSafe 4.0 Client Install over 3.1 Database

The first possible cause is an installation pattern specific to Visual SourceSafe 4.0. If you are upgrading from SourceSafe 3.1, and perform a Client Installation on that 3.1 database without first performing a Server installation, then you will receive "Incompatible Database" error. In this case, the solution is to perform the following steps:

Run the SETUP.EXE off the Visual SourceSafe 4.0 disks / cd-rom.\
Choose Add/Remove in the "Microsoft Visual SourceSafe 4.0 Setup" dialog.
Add the following components to make your client installation the equivalent of a server install:
```
    - Create Database
    - Help Files
    - Books OnLine
```
If you intend to integrate Visual C++ or Visual SourceSafe on the machine with Visual SourceSafe already installed, then also select:
```
    - Visual Basic and Visual C++ Registration
```
Otherwise, you would need to select this option. See the following article for details:
```
      ARTICLE ID: Q135332
      TITLE     : FAQ: Visual SourceSafe Installation and Setup Issues
```

Cause #2: Visual SourceSafe Install Not Completed

The SourceSafe install is not completed. The last thing the SourceSafe installation does is run a DDCONV command to make sure that the SourceSafe database is updated to the current version. If for some reason, the installation does not finish, when you try to start up SourceSafe, you will receive either an "Incompatible Database Format" or "Incompatible Database" error.

RESOLUTION

To work around this problem, execute the proper DDCONV.EXE. This program will make the necessary modifications to the data files. For example, use this command line:

      DDCONV <path to data_dir>

There are several different versions of DDCONV for different operating systems. With SourceSafe 3.x, if you are running under MS-DOS, Windows 3.1, or Windows for Workgroups, you can run DDCONV from the ADMIN directory. If you are running Windows NT or Windows 95, you can run DDCONV from the WINNT directory.

With Visual SourceSafe 4.0, if you are running under MS-DOS, run DDCONV from the MS-DOS directory. If you are running under Windows 3.1 or Windows for Workgroups, run DDCONV from the WIN directory. If you are running Windows NT or Windows 95, run DDCONV from the WIN32 directory.

MORE INFORMATION

NOTE: SourceSafe version 3.02 contains an invalid Ddconv.exe that will not update the database. To get a correct Ddconv.exe, update your product or download Ddcon.exe.

The following file is available for download from the Microsoft Software Library:

 ~ Ddcon.exe (size: 60760 bytes)

For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services

After you obtain Ddcon.exe, run it in an empty directory to get the correct version of Ddconv.exe.

Keywords : kbtool SourceSafe ss3 vbwin vss
Version : 3.0x 4.0
Platform : MACINTOSH MS-DOS NT UNIX WINDOWS
Issue type : kberrmsg
Resolution Type : kbfile

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 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.