BUG: SourceSafe Reports a Date/Time of 1/1/70

 Last reviewed: May 9, 1997
Article ID: Q130270
The information in this article applies to:
  • SourceSafe for Windows, versions 3.04, 3.1, 4.0, 4.0a, 5.0
  • SourceSafe for Windows NT, versions 3.04, 3.1, 4.0, 4.0a, 5.0

SYMPTOMS

SourceSafe reports a date/time of 1/1/70 on all files within a project.

CAUSE

This is caused by a corrupt STATUS.DAT file.

RESOLUTION

The STATUS.DAT file can be repaired in two ways. Download the latest versions of Analyze and DDCONV. For information on downloading these file, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q139566
   TITLE     : ANALYZE5.EXE Utility for Visual SourceSafe

  • Run DDCONV -S <path to data directory>.

  • Delete the STATUS.DAT file and run ANALYZE <path to data directory> -f.

    Note that if you have SourceSafe version 4.0 (build 811 or 831), you should obtain version 4.0a (build 1309) from Microsoft Technical Support before repairing STATUS.DAT .

    STATUS

    Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

    • Additional query words: REBUILD
    Keywords : kbnetwork kbusage SourceSafe vbwin kbbuglist
    Version : 3.04 3.1 4.0 4.0a 5.0
    Platform : NT WINDOWS

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