How to Upgrade SourceSafe Manually

 Last reviewed: December 19, 1995
Article ID: Q131451
The information in this article applies to:
  • Microsoft SourceSafe for Windows, versions 3.04, 3.1
  • Microsoft SourceSafe for Windows NT, versions 3.04, 3.1
  • Microsoft SourceSafe for MS-DOS, versions 3.04, 3.1
  • Microsoft SourceSafe for Macintosh, versions 3.04, 3.1

SUMMARY

If the SourceSafe upgrade installation fails it may be necessary for the user to manually convert the database.

MORE INFORMATION

The following steps are needed to complete the upgrade:

NOTE: For the following examples to work, SourceSafe must be in the \SS directory and the data in the \SS\DATA directory. If the user is upgrading to a version prior to version 3.1, make sure that all of the SourceSafe serial numbers are available prior to upgrading.

  1. Run the DDCONV.EXE utility located in the \SS\ADMIN directory with the following syntax:

    DDCONV -s \SS\DATA

** If installing version 3.04 or greater ignore step 2 **

  1. Run the following command for all of the serial number in the system: 

          SERIALIZ -s<serial number> \SS\DATA

  2. If upgrading from version 2.2:

    To upgrade the SYSTEM.INI to SRCSAFE.INI, run this command: 

          UPDINI -m\SS\DATA

    To upgrade each user's SS.INI file, run the following command for each user in the system: 

          UPDINI \SS\USERS\<user name>\SS.INI

Additional reference words: ss3 vbwin 3.04 3.10 SS SRCSAFE
KBCategory: kbsetup
KBSubcategory: SourceSafe

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: December 19, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.