Microsoft KB Archive/151006

{| 4.00 5.00 | 4.00 5.00 WINDOWS  | WINDOWS NT kbusage kbprb The information in this article applies to:
 * width="100%"|


 * 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
While converting a database from SourceSafe 3.1 to Visual SourceSafe 4.0 or 5.0, the DDCONV utility reports an error and logs the error to the Ddcerr.log file. The file Ddcerr.log contains the error:

Physical file parent project  not found, skipping parent record

CAUSE
This error is caused by having two projects with the same name: one is the active project, and the other is a project that is deleted but not permanently destroyed.

RESOLUTION
Follow these steps to correct this error:


 * 1) Recover the SourceSafe 3.1 database from backup.
 * 2) Using the SourceSafe 3.1 interface, rename the project by adding an "_" to make the name unique.
 * 3) Run Ddconv.exe again on the data directory.
 * 4) Rename the project to its original name in Visual SourceSafe 4.0 or 5.0.

STATUS
This behavior is by design.

MORE INFORMATION
In SourceSafe 3.1, child files only refer to their parent projects by project name, which is not unique. In Visual SourceSafe 4.0 and 5.0, the child files refer to the physical file name, which is unique.

After converting from SourceSafe 3.x to Visual SourceSafe 4.0 or 5.0, the fileDdcerr.log contains information and errors about the conversion. This file is usually found in the data directory.
 * }

-

Last reviewed: February 27, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.