PRB: PVCS to SourceSafe Conversion Fails

 Last reviewed: October 25, 1996
Article ID: Q157533
The information in this article applies to:
  • Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows, versions 4.0, 4.0a
  • Microsoft Visual SourceSafe, 32-bit, for Windows, version 5.0

SYMPTOMS

When running PVCS_SS.EXE to convert a PVCS database to a SourceSafe database, the conversion does not complete. This process does not return any error messages.

RESOLUTION

Add these lines to AUTOEXEC.BAT: 

   set libpath = <path to the DLLs used by the GET program,
                 such as c:\pvcs\dll>

   set vcsid  = <userid>

   set vcscfg = <path to configuration file>

   set intrsolvdir = <path to dir where license admin facility is>
NOTE: When you execute PVCS_SS *.*, meaning convert *all* of the files, it may appear to hang as it apparently does a lot of initialization in PVCS.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Problem

  1. At a DOS prompt, switch to the directory containing the file PVCS_SS.EXE. This will vary depending on the version of SourceSafe and the kind of installation.

  2. Type the command:

    PVCS_SS *.* $/<newproject>

On screen and in the conversion log file, the following appears: 

   PVCS_SS. Copyright...
   7/25/95 12:42
There may be some other unusable information as well.

The PVCS data is converted to SourceSafe data.

KBCategory: kbprg kbprb
KBSubcategory: ssother
Additional reference words: 4.00 4.00a 5.00 kbdsi



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: October 25, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.