PRB: SSARC/SSRESTOR Change 4.0 Database to 4.0a/5.0 Format

 Last reviewed: January 2, 1997
Article ID: Q161610
The information in this article applies to:
  • Microsoft Visual SourceSafe for Windows, versions 4.0, 4.0a, 5.0

SYMPTOMS

Visual SourceSafe version 5.0 includes two new utilities, SSARC.EXE and SSRESTOR.EXE. These utilities allow the Visual SourceSafe Administrator to archive and restore files and projects within Visual SourceSafe databases.

Visual SourceSafe version 4.0 shipped three different builds: 811 (version 4.0), 831 (version 4.0), and 1309 (version 4.0a). You can find out which build you are using by clicking About on the Help menu.

The actual format of the Visual SourceSafe database did not change between builds 811 and 831 (both are version 4.0) or build 1309 (version 4.0a) and Visual SourceSafe version 5.0. However, the format did change between 831 and 1309.

When you use SSARC.EXE and SSRESTOR.EXE on a version 4.0 database (builds 811 or 831), it is 'silently' upgraded to the new 4.0a/5.0 format. When this upgrade occurs, you cannot use the executables from version 4.0 (builds 811 and 831). Under this condition you may get the following error message: 

   Incompatible database version.

RESOLUTION

Upgrade to Visual SourceSafe version 4.0a or higher before using the SSARC.EXE and SSRESTOR.EXE. You can get version 4.0a by contacting Microsoft Technical Support.

STATUS

This behavior is by design.

KBCategory: kbusage kbprb
KBSubcategory: ssusage
Additional reference words: 4.00 4.00a 5.00 kbdss



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