FIX: Branched Files Restored to New Database Cause Corruption

 Last reviewed: December 1, 1997
Article ID: Q174874
The information in this article applies to:
  • Microsoft Visual SourceSafe, 32-bit, for Windows, version 5.0

SYMPTOMS

Using SSARC/SSRESTOR Utilities to archive and restore files to a new database can cause corruption to occur. The problem happens only when restoring files that were previously branched into a different database. Analyze will report no errors immediately after restoring the files to the new database. However, any action adding a log record (such as labeling, sharing, branching, checking in, etc.) to a problem file will cause corruption. When attempting to perform an action on an affected file, you may see "file may be corrupt" errors followed by an "error reading file" message.

Analyze can be used to fix the files after the corruption occurs, but the problem can't be detected or repaired before an action is performed.

RESOLUTION

You should use build 2222 of ssrestor.exe, available in Visual Studio Service Pack 3. If possible, using build 2222 of ssarc.exe is also recommended.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 3.

For more information, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

Keywords          : ssdb VS97FixlistSP3
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

================================================================================

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