FIX: Initialization Var Shadow_SetTime Set to Invalid Value

 Last reviewed: August 25, 1997
Article ID: Q139672
The information in this article applies to:
  • 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

The error "Initialization variable Shadow_SetTime set to invalid value" occurs when a user checks a file in to Visual SourceSafe or adds a file to Visual SourceSafe.

CAUSE

The Visual SourceSafe Administrator gives administrators the ability to shadow projects. The shadow option has several flags that tell SourceSafe how to operate on the files. One of the options is the date/time flag known as the Shadow_SetTime .ini file variable. The valid options in the Administrator are Current, Modification, or Update. The valid .ini file settings are Current, Mod, and Update respectively. The Visual SourceSafe Administrator improperly wrote the modification setting as: 

   Shadow_SetTime = Modification

RESOLUTION

The administrator should manually modify the Srcsafe.ini file. Modify the Shadow_SetTime setting as follows: 

   Shadow_SetTime = Mod

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

This problem has been fixed in Visual SourceSafe 5.0. 

Keywords          : SourceSafe vbwin vss kbenv fixlist5.00 kbbuglist
Version           : 4.0 5.0
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

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

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